You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-user@portals.apache.org by Martin Maidhof <ma...@wemove.com> on 2003/04/30 11:10:31 UTC
Re: development structure for eclipse ? How to structure jetspeed for development ?
Hi Tam,
i work with a combination of eclipse and ant and the following eclipse plugins:
http://www.sysdeo.com/eclipse/tomcatPlugin.html
http://www.gebit.de/download/planty/planty.html
In principal, i have my own develop directory, the jetspeed distribution directory
and a directory where i merge both to a webapp (merge directory). My develop
directory has the same structure as jetspeed, but contains only my changed/new files.
The merging is done by ant, compiling can be done by ant and eclipse. The single
steps are as follows:
ant:
- clean merge directory
- copy all jetspeed stuff i need to the merge directory (libs, props etc.)
- copy all static stuff from my develop directory to the merge directory (images,
templates etc.)
- compile my stuff to the merge directory (torque om, actions ...)
- merge my props in my develop directory with the props in the merge directory (see tutorial)
voila, the merge directory now contains my webapp ready to run or deploy (hopefully) ...
eclipse:
- i have a separate project for the jetspeed distribution to compile, all needed internal libs
in this project are exported (turbine, velocity ...)
- i have a separate project for my "develop directory", this project references the
jetspeed project from above as "reqired project" (and thus get's the needed libs
via the jetspeed project), i compile my stuff to the same directory as ant, so i can
develop with eclipse
- the tomcat plugin configures tomcat to run my webapp under the merge directory directly
as context
Usually i develop as follows:
- run ant to create the newest app under the merge directory
- develop with eclipse, which compiles my changes to the merge directory (if i change static
files i have to copy them to the merge dir, if i change props i have to remerge the new
props to the merge directory)
- run tomcat via the plugin, so i can directly test my webapp in the merge directory
(because of "hot deployment" you mostly don't have to restart tomcat if you recompile stuff)
Hope this helps, please send all replies also to the jetspeed user list :)
regards,
Martin
................................
martin maidhof
martin@wemove.com | fon: +49-(0)69-759003-14
w e m o v e d i g i t a l s o l u t i o n s ... http://www.wemove.com
----- Original Message -----
From: "Tâm Huynh" <ta...@juggler.net>
To: "Martin Maidhof" <ma...@wemove.com>
Sent: Tuesday, April 29, 2003 10:02 PM
Subject: Re: development structure for eclipse ? How to structure jetspeed for development ?
> Hi Martin,
>
> I just read you post in the mailing list archive. I'm
> just starting to work with Jetspeed and wondering how
> I should organize my code, too. Using Eclipse would
> be nice. Can you shortly tell me how you did it in the end?
>
> Cheers,
> Tâm
>
>
> On Fri, Feb 07, 2003 at 02:01:48PM +0100, Martin Maidhof wrote:
> > Hi,
> >
> > is there any experience in developing with jetspeed in an eclipse
> > environment ? Or better, what's the preferred development structure
> > (directories, files, build targets etc.) for separating the individual
> > changes from the default jetspeed distribution (for "fast" upgrade to new
> > jetspeed versions ...)
> >
> > I know the tutorial uses property merging etc. but it "only" merges into
> > the default war file. How to extensively modify the war file (meaning
> > the underlying sources, images etc.) WITHOUT loosing track of my own changes ?
> >
> > I'm thinking of a separate directory which encapsulates all modifications
> > and add ons (like in the tutorial) and a general directory with the "default"
> > jetspeed distribution, where you can delete stuff you don't need (images etc.).
> > Both should be merged to a common webapp directory, which is the final webapp.
> > Does this make sense ? Or will soon the personal directory look like the
> > default jetspeed one with lot's of merging trouble ?
> >
> > A complete webapp dir under the development root would also be fine for
> > server side debugging. E.g. with the Eclipse Tomcat Launcher plugin you can
> > easily debug a webapp within eclipse but it has to be part of the project
> > (underneath the development root)
> > -> http://www.sysdeo.com/eclipse/tomcatPlugin.html
> >
> > Or just use the default structure and my.properties and mix all together
> > (e.g. modified java sources) as suggested in the Configuration Guide
> > http://jakarta.apache.org/jetspeed/site/config_guide.html
> > ?
> >
> > Any advice appreciated !
> >
> > Martin
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
Re: development structure for eclipse ? How to structure jetspeed for development ?
Posted by Tâm Huynh <ta...@nterra.com>.
Hi Martin,
thanks a lot for the detailed description!
Tâm
On Wed, Apr 30, 2003 at 11:10:31AM +0200, Martin Maidhof wrote:
> Hi Tam,
>
> i work with a combination of eclipse and ant and the following
> eclipse plugins:
> [...]
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org