Eclipse Community Forums: ServerTools (WTP)

Home » Language IDEs » ServerTools (WTP) » WTP project structure

Tue, 18 October 2005 03:23

Eclipse User

Hi all,
i think now wtp is matured enough to be worth considering it for our
development cycle and i'd wish to give it a try, but i'm a bit scared
about what this could cause to our projects structure and way of working.

One of our must is to completely divide the source of a project from
anything needed for or produced during build or for runtime (dependency
jars), i clearly stated this in my requirement
http://dev.eclipse.org/newslists/news.eclipse.webtools/msg00 811.html

Now peeking around in docs and this newsgroup it looks instead that i need
to insert runtime artifact in the source tree, for instance i read that
dependency jars mus be in WEB-INF/lib that i assume is the one in the
source tree.

This is a no no for our group, i cannot count the many times i had to
clean unwanted jars or compiled classes wrongly imported in our cvs
repository.

Normally our project structure is composed of three main directories:
src (java, junit tests, etc)
web (jsp, html, etc)
build

Within the build dir there are the ant build files, the dependendency jars
for build, compile and runtime (i'm now experimenting with ivy dependency
management) and any build artifact (wars assembled from compiled src, web
stuff and runtime dependency libs)

I'd be glad if someone could help me understanding if wtp can adapt to our
way of working, ie if it can satisfy the following conditions:

1- the deployable content must be assembled in a specified location with
pieces coming from various places
2- that assembled content must be deployable to some server (jboss in our
case, i already built a working 4.0.3 serverdef for our environment)
3- that assembled content must have the source associated with it (java,
jsp) and must be debuggable (java, jsp) in the server
4- i must not need spreading build and runtime artifacts in the cvs source
tree

Thanks for your attention, Gabriele

Re: WTP project structure [message #144279 is a reply to message #144267]

Tue, 18 October 2005 03:50

Eclipse User

Originally posted by: Rafal.Krzewski.caltha.pl

Gabriele Garuglieri wrote:

> Now peeking around in docs and this newsgroup it looks instead that i
> need to insert runtime artifact in the source tree, for instance i read
> that dependency jars mus be in WEB-INF/lib that i assume is the one in
> the source tree.
>
> This is a no no for our group, i cannot count the many times i had to
> clean unwanted jars or compiled classes wrongly imported in our cvs
> repository.

Keeping dependency jars in projects CVS is the root of all evil...
Fortunately WPT does not impose that at all.

See https://bugs.eclipse.org/bugs/show_bug.cgi?id=87474 for details.

Regarding your other concern with polluting CVS with build artifacts -
the assembly of the deployable artifact used to happen in a .deployables
directory within the project (as of WTP 0.7), but it was invisible to
the team provider (or at least developers intention was to be so - I
recall problems reported with that). I heard that the assembly location
or technique was to be changed in the future, but it seems that
developers are well aware of this concern.

R.

Re: WTP project structure [message #144376 is a reply to message #144279]

Wed, 19 October 2005 01:38

Eclipse User

"Rafal Krzewski" <Rafal.Krzewski@caltha.pl> wrote in message
news:dj29fe$1l6$1@news.eclipse.org...
> Gabriele Garuglieri wrote:
>
>> Now peeking around in docs and this newsgroup it looks instead that i
>> need to insert runtime artifact in the source tree, for instance i read
>> that dependency jars mus be in WEB-INF/lib that i assume is the one in
>> the source tree.
>>
>> This is a no no for our group, i cannot count the many times i had to
>> clean unwanted jars or compiled classes wrongly imported in our cvs
>> repository.
>
> Keeping dependency jars in projects CVS is the root of all evil...
> Fortunately WPT does not impose that at all.
>
> See https://bugs.eclipse.org/bugs/show_bug.cgi?id=87474 for details.
>
> Regarding your other concern with polluting CVS with build artifacts - the
> assembly of the deployable artifact used to happen in a .deployables
> directory within the project (as of WTP 0.7), but it was invisible to the
> team provider (or at least developers intention was to be so - I recall
> problems reported with that). I heard that the assembly location or
> technique was to be changed in the future, but it seems that developers
> are well aware of this concern.
>
> R.

I could not work out if classes from other projects under eclipse can be
contributed automatically. Any ideas?

Matty.

Re: WTP project structure [message #144410 is a reply to message #144376]

Wed, 19 October 2005 06:12

Eclipse User

Originally posted by: patrick.roumanoff.gmail.com

Matthew Cooper wrote:
>
>
> I could not work out if classes from other projects under eclipse can be
> contributed automatically. Any ideas?

Yes they can, there is even a ui for that.

for WTP-1.0M8
in project properties (of a web app) go to J2EE Module dependencies->
Web Libraries
you should see the list of potential dependent project, and you can also
add external jars, or variable dependencies (a la Maven)

the build process will then jar you dependent project and put it in the
WEB-INF/lib folder of the webapp assembly.

hope this helps

Patrick

Re: WTP project structure [message #144853 is a reply to message #144267]

Fri, 21 October 2005 14:25

Eclipse User

Originally posted by: rsanheim.REMOVE.gmail.com

Gabriele Garuglieri wrote:
......

> Normally our project structure is composed of three main directories:
> src (java, junit tests, etc)
> web (jsp, html, etc)
> build

Regarding this, please go vote and follow this bug - its coming along in
the latest integration builds - you can now set the web and source
folders for a new project, but I don't think you can easily change an
existing structure.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=102981

- Rob
-------------------------
http://www.robsanheim.com

Re: WTP project structure [message #145028 is a reply to message #144267]

Mon, 24 October 2005 16:00

Eclipse User

Glad to know that progress is being made on this and that we will will see in the WTP1.0 final release in December..

Previous Topic:	javadocs available anywhere?
Next Topic:	Java Web Service Client

Goto Forum:

-=] Back to Top [=-

Current Time: Fri Apr 18 13:28:08 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter