commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Strachan" <james_strac...@yahoo.co.uk>
Subject Re: [jelly] howto setup eclipse for jelly development?
Date Wed, 05 Mar 2003 08:23:20 GMT
 From: "Wannheden, Knut" <knut.wannheden@paranor.ch>
> Hi,
>
> I was wondering if someone could provide some easy instructions on how to
> best set up Eclipse for development on the Jelly project.
>
> I suppose the first step is to check out Jelly as a Java project from CVS.
> This part is quite easy.
>
> The next step is probably to setup the project classpath using the Maven
> definitions, which is very well explained in
>
http://radio.weblogs.com/0112098/stories/2003/02/12/usingEclipseAndMaven.htm
> l.
>
> Now comes the harder part: Now that Jelly has been modularized into the
core
> and the individual tag libraries (all as individual Maven projects) I
don't
> know how to best map these to Eclipse projects.  Should I create a single
> Java project for everything?  Or should I create individual projects for
the
> tag libraries?  For the former to work, I assume I will have to setup the
> classpath and sourcepath manually, which isn't very elegant.  And for the
> latter to work I assume I will somehow have to use a different root
> directory for the Jelly core project as projects can't be nested in
Eclipse.
> Also I guess I'd have to setup the project dependencies manually.
>
> Hopefully there's a much easier solution altogether! :-)

What I've been doing locally is to add all the source directories for each
library I'm working on to the project along with manually adding any extra
jar dependencies. So I have a single project with all the source code for
Jelly in there, divided into java & test directories for each library. Then
I get the benefit of eclipse compile checking if I change something in
Jelly's core etc.

It'd be nice to patch the eclipse plugin for Maven to do this automatically.
The same thing could be used to generate the eclipse project for Maven
itself; it has a similar issue of lots of sub-projects (plugins) that it'd
be nice to include in the same large project.

James
-------
http://radio.weblogs.com/0112098/

__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com

Mime
View raw message