cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler" <cziege...@s-und-n.de>
Subject RE: eclipse classpath
Date Tue, 15 Jul 2003 06:36:00 GMT
Using eclipse is really very simple, you only have to invoke ant once.
Just add a launch configuration to your project that directly starts
jetty and uses the build/webapp directory for the webapp.

Now build Cocoon once using ant, this creates the webapp directory,
copies the samples etc; invoke the eclipse-project and eclipse-webapp
targets. This updates your eclipse project, removes all jars from
WEB-INF/lib and restores the cocoon.roles.
>From now on you can directly compile, edit and debug in eclipse and
simply launch the jetty launch target from within eclipse.
You only have to invoke ant if you change something in the configuration
or the samples but not for java code.
PS: I tried to created the launch configuration via ant but failed :(

Carsten

> -----Original Message-----
> From: Geoff Howard [mailto:cocoon@leverageweb.com]
> Sent: Tuesday, July 15, 2003 4:23 AM
> To: dev@cocoon.apache.org
> Subject: Re: eclipse classpath
>
>
> Joerg Heinicke wrote:
> > Why exactly? I only found out - when setting output path to
> > WEB-INF/classes - that Eclipse kicked the complete content and replaces
> > the xpatch'ed cocoon.roles.
>
> Maybe that is the smarter way to go.  I've been wanting to set the
> output path to the same as the build before prepare-webapp (i.e.,
> build/cocoon-2.1rc1dev/classes, build/cocoon-2.1rc1dev/scratchpad/dest,
> and so on for each source path) so I could let eclipse do the compiling
> (since it usually already has anyway) but still use the regular build.
> I don't know that eclipse's compiling is orders of magnitude better, but
> it does it incrementally.
>
> But compiling/copying straight to WEB-INF would save even more time in
> some situations.  Well, I'll start experimenting and see what I learn.
> Anything to improve:
> BUILD SUCCESSFUL
> Total time: 14 minutes 29 seconds
>
> > I don't have another problem with Eclipse.
>
> Me either (except the debugger and flowscript possibly)
>
> By the way, are you running ant from inside eclipse, or do you use
> build.sh?  I gave up on the first and haven't tried lately.
>
> > Carsten added a target 'eclipse-prepare-webapp' to circumvent this
> > problem and restore the xpatch'ed cocoon.roles.
>
> I'll see what he's doing there - maybe it'll give some ideas.
>
> Thanks,
> Geoff
>
> >
> > Geoff Howard wrote:
> >
> >> I just noticed that eclipse now has support for different destination
> >> folders for each source folder, something that was needed before one
> >> could have eclipse compile into the same build dir that cocoon does.
> >> Is there value in setting this up? (it's just a matter of adding an
> >> output attribute on the classpathentry element in .classpath.
> >>
> >> I'd be particularly interested to hear from anyone who's tried it and
> >> found problems or benefits.  I'd imagine that the cocoon build would
> >> go faster, and possibly build clean would be less often necessary.
> >>
> >> Geoff
> >
> >
> >
> >
> >
>
>


Mime
View raw message