Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Language IDEs » ServerTools (WTP) » Project Layout
Project Layout [message #54793] Sun, 28 November 2004 20:50 Go to next message
Christopher M. Judd is currently offline Christopher M. JuddFriend
Messages: 39
Registered: July 2009
Member
I just finished reading the Wiki Project Layout page
( http://wiki.objectweb.org/eclipse-webtools/Wiki.jsp?page=Pro jectLayout).
Based on my experience and the community input, I wonder if there is too
much focus on projects. It appears the direction may be to create separate
Web, EJB, Enterprise, application client and library projects much like WSAD
does. I think this is the wrong approach and something I found unintuitive
when moving from JBuilder and ANT to Eclipse and WSAD. I think there should
be a single Java project in which you can add configurations to it. So a
single Java project could contain the Web, EJB and Enterprise configurations
and artifacts. Configurations could be added and configured either using the
project properties (project icon could change if configurations are added)
or like JBuilder does by adding nodes to the project tree.
Re: Project Layout [message #54929 is a reply to message #54793] Tue, 30 November 2004 14:42 Go to previous message
Michael D. Elder is currently offline Michael D. ElderFriend
Messages: 62
Registered: July 2009
Member
Hi Christopher,

The design of the J2EE project-interaction architecture is under
discussion for the first Web Tools release. Some information on our current
state can be found at
http://dev.eclipse.org/viewcvs/index.cgi/jst/components/serv er/development/miscdocuments/?cvsroot=WebTools_Project .
We are currently collecting and integrating comments from other WTP
contributors. A refresh of the document should be available within the week.

At a high level, we will encourage the use of a single project per
module because of the advantages that it provides. The single project
metaphor makes it easier to understand the dependencies between modules and
to validate those dependencies in a development environment, which can catch
potential problems before they are deployed into a runtime environment.
However, we are building in flexibility for users who still have a need for
a multiple-modules-per-project metaphor due to preference or legacy systems.


Thank you for your participation.

Kind Regards,

Michael D. Elder


"Christopher M. Judd" <eclipse@juddsolutions.com> wrote in message
news:coddn9$o34$1@www.eclipse.org...
> I just finished reading the Wiki Project Layout page
> ( http://wiki.objectweb.org/eclipse-webtools/Wiki.jsp?page=Pro jectLayout).
> Based on my experience and the community input, I wonder if there is too
> much focus on projects. It appears the direction may be to create separate
> Web, EJB, Enterprise, application client and library projects much like
WSAD
> does. I think this is the wrong approach and something I found unintuitive
> when moving from JBuilder and ANT to Eclipse and WSAD. I think there
should
> be a single Java project in which you can add configurations to it. So a
> single Java project could contain the Web, EJB and Enterprise
configurations
> and artifacts. Configurations could be added and configured either using
the
> project properties (project icon could change if configurations are added)
> or like JBuilder does by adding nodes to the project tree.
>
>
Previous Topic:org.eclipse.wst.webbrowser
Next Topic:Grouping create wizards
Goto Forum:
  


Current Time: Sat Sep 28 17:53:00 GMT 2024

Powered by FUDForum. Page generated in 0.03535 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top