Return-Path: Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list commons-user@jakarta.apache.org Received: (qmail 88873 invoked from network); 4 Mar 2003 08:27:28 -0000 Received: from mail.paranor.ch (HELO nts?par1.paranor.ch) (195.65.4.180) by daedalus.apache.org with SMTP; 4 Mar 2003 08:27:28 -0000 Received: by nts_par1.paranor.ch with Internet Mail Service (5.5.2448.0) id ; Tue, 4 Mar 2003 09:27:39 +0100 Message-ID: <36E996B162DAD111B6AF0000F879AD1A76C153@nts_par1.paranor.ch> From: "Wannheden, Knut" To: "Jakarta-Commons-User (E-mail)" Subject: [jelly] howto setup eclipse for jelly development? Date: Tue, 4 Mar 2003 09:27:35 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2E227.EA9BAFCE" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N ------_=_NextPart_001_01C2E227.EA9BAFCE Content-Type: text/plain; charset="iso-8859-1" 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! :-) Cheers, -- knut ------_=_NextPart_001_01C2E227.EA9BAFCE--