| newbee eclipse j2ee module development [message #86519] |
Tue, 01 July 2003 12:07  |
Eclipse User |
|
|
|
Originally posted by: user.domain.invalid
I am several years into developing J2EE applications with Ant, CVS, and
vi and only a few days into Eclipse. I'm working my way through some of
the newgroup postings/manuals but could use some religion on how some of
this is suppose to work.
My _existing_ Ant-based system is a multi-headed source tree with each
head being targeted at a component archive (EJB, WAR, .jar, etc.). They
are nested within their scoping unit (EAR). I have three levels of
build.xml files; root, unit/EAR, and component. Ignoring Ant for the
moment, I want to be able to setup Eclipse to understand my source tree
and leave the complexity of the project construction to Ant.
How, in general are Eclipse projects managed when the products go into
several different archives?
It almost looks like an EAR with 2 EJB archives and a WAR would be 3-4
Eclipse projects (one for the three components and possibly another for
the EAR itself).
Is there a (free) plugin that I've missed?
thanks!
|
|
|
| Re: newbee eclipse j2ee module development [message #87005 is a reply to message #86519] |
Tue, 01 July 2003 22:40  |
| Eclipse User |
|
|
|
Originally posted by: cagatayk.stop.acm.org
user@domain.invalid wrote:
> I am several years into developing J2EE applications with Ant, CVS, and
> vi and only a few days into Eclipse. I'm working my way through some of
> the newgroup postings/manuals but could use some religion on how some of
> this is suppose to work.
>
> My _existing_ Ant-based system is a multi-headed source tree with each
> head being targeted at a component archive (EJB, WAR, .jar, etc.). They
> are nested within their scoping unit (EAR). I have three levels of
> build.xml files; root, unit/EAR, and component. Ignoring Ant for the
> moment, I want to be able to setup Eclipse to understand my source tree
> and leave the complexity of the project construction to Ant.
>
> How, in general are Eclipse projects managed when the products go into
> several different archives?
>
> It almost looks like an EAR with 2 EJB archives and a WAR would be 3-4
> Eclipse projects (one for the three components and possibly another for
> the EAR itself).
Not necessarily. You can set up your project source folders to point to
each source tree and define individual output directories for each
source folder. To make accessing your web resources more palatable you
can define a few top level linked folders to context root and web-inf
directories; they will show up with a special "chained" icon in the
Resource Navigator.
You would need to have more than one project if you have to set the
classpath of some of the archives/components differently, though.
>
> Is there a (free) plugin that I've missed?
>
> thanks!
>
--
CK.
|
|
|
Powered by
FUDForum. Page generated in 0.04489 seconds
Home