-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 16 Jan 2006, Gianugo Rabellino wrote:
Date: Mon, 16 Jan 2006 00:05:39 +0100
From: Gianugo Rabellino <[EMAIL PROTECTED]>
Reply-To: dev@cocoon.apache.org
To: dev@cocoon.apache.org
Subject: Re: Jetty and Eclipse
On 1/15/06, Daniel Fage
Gianugo Rabellino wrote:
>
> Guys, sorry for the wasted electrons but I just feel the compelling
> need to thank you so much for this most promising work. You made me
> open my eyes on how Maven 2 could help us getting a solid build system
> which is a huge first step towards semplification: I'm
Gianugo Rabellino wrote:
On 1/15/06, Daniel Fagerstrom <[EMAIL PROTECTED]> wrote:
Jorg Heymans skrev:
Jorg Heymans wrote:
Anyhow, there seems to be something not quite right yet with our eclipse
setup. If you run eclipse:eclipse from the top level pom in
whiteboard/cocoon-flat
On 1/15/06, Daniel Fagerstrom <[EMAIL PROTECTED]> wrote:
> Jorg Heymans skrev:
> > Jorg Heymans wrote:
> >
> >>Anyhow, there seems to be something not quite right yet with our eclipse
> >>setup. If you run eclipse:eclipse from the top level pom in
> >>whiteboard/cocoon-flat-layout, you'll see that
Daniel Fagerstrom wrote:
> Absolutely! When you work at several blocks at once it is important. And
> it also give you connection to the latest source, when you get to e.g.
> core during debuging.
Cool!
I've updated the docs [1] to reflect this.
Jorg
[1] http://cocoon.zones.apache.org/dais
Jorg Heymans skrev:
Jorg Heymans wrote:
Anyhow, there seems to be something not quite right yet with our eclipse
setup. If you run eclipse:eclipse from the top level pom in
whiteboard/cocoon-flat-layout, you'll see that the plugin generates
eclipse project dependencies between the different mod
Jorg Heymans wrote:
>
> Anyhow, there seems to be something not quite right yet with our eclipse
> setup. If you run eclipse:eclipse from the top level pom in
> whiteboard/cocoon-flat-layout, you'll see that the plugin generates
> eclipse project dependencies between the different modules (very
>
Daniel Fagerstrom wrote:
> I'm certain that the hot deploy feature is usefull, see [2]. My problem
> was that I wanted to debug the cocoon-blocks-fw-sample, and here the
> code that I actually want to debug is in the project
> cocoon-blocks-fw-impl that is added as a jar to the webapp in
> cocoon-
I'm certain that the hot deploy feature is usefull, see [2]. My problem
was that I wanted to debug the cocoon-blocks-fw-sample, and here the
code that I actually want to debug is in the project
cocoon-blocks-fw-impl that is added as a jar to the webapp in
cocoon-blocks-fw-sample, when I run mvn
Daniel Fagerstrom wrote:
> Even if the Jetty6 plugin for Maven is an important step, the jar
> copying in mvn war:inplace, doesn't give the right snappy feeling for
> Cocoon core development.
Is its hot-deploy feature useable at all ? It's described on their
website [1].
HTH
Jorg
[1] http://j
Even if the Jetty6 plugin for Maven is an important step, the jar
copying in mvn war:inplace, doesn't give the right snappy feeling for
Cocoon core development. I wanted to start the Webserver in Eclipse
instead, and found a Jetty plugin http://jettylauncher.sourceforge.net/.
Besides installin
11 matches
Mail list logo
