Jorg Heymans wrote:
up until here everything went fine AFAICS. We should exclude svn files
from cocoon-core-2.2-SNAPSHOT.jar though.
Oh, you're right - this must be a bug in the resource plugin from m2 :(
Now you can startup Jetty. Set the JETTY_WEBAPP environment variable to
On Tuesday 30 August 2005 17:59, Carsten Ziegeler wrote:
First you have to install m2 latest from SVN, the alpha-3 does NOT work
for us!
H You realize that you now forces some people to stop building Cocoon
HEAD, due to overly high requirements of getting Maven2 installed. Many
people
Niclas Hedhman wrote:
On Tuesday 30 August 2005 17:59, Carsten Ziegeler wrote:
First you have to install m2 latest from SVN, the alpha-3 does NOT work
for us!
H You realize that you now forces some people to stop building Cocoon
HEAD, due to overly high requirements of getting
Niclas Hedhman wrote:
On Tuesday 30 August 2005 17:59, Carsten Ziegeler wrote:
First you have to install m2 latest from SVN, the alpha-3 does NOT work
for us!
H You realize that you now forces some people to stop building Cocoon
HEAD, due to overly high requirements of
Niclas Hedhman wrote:
I hope considerations are made that a Maven 2.0 Final is released prior to
making any breaking of the current Ant build. Hopefully that will be in a
couple of weeks. Worst-case scenario, remember Maven 1.
using maven1 at this point, if that's what you mean by
On Wednesday 31 August 2005 15:17, Carsten Ziegeler wrote:
Niclas Hedhman wrote:
On Tuesday 30 August 2005 17:59, Carsten Ziegeler wrote:
First you have to install m2 latest from SVN, the alpha-3 does NOT work
for us!
H You realize that you now forces some people to stop building
On Wednesday 31 August 2005 16:16, Jorg Heymans wrote:
Niclas Hedhman wrote:
I hope considerations are made that a Maven 2.0 Final is released prior
to making any breaking of the current Ant build. Hopefully that will be
in a couple of weeks. Worst-case scenario, remember Maven 1.
using
Jorg Heymans wrote:
...
Invoking build compile before executing the maven targets made it work.
I also found out that it is sufficient (at this stage) to run the
package target to get the basic webapp working. So my steps, from a
fresh trunk checkout, were :
- build maven and install maven
Daniel Fagerstrom wrote:
Some libraries seemed to be downloaded two times during Cocoon compile,
rhino e.g., any explanation? There where also plenty of ignored checksum
errors.
There is (obviously) a bug in the checksum testing of m2 - I'll look
into that in the next days.
The svn
Carsten Ziegeler wrote:
There is (obviously) a bug in the checksum testing of m2 - I'll look
into that in the next days.
yup, it's a known issue :
http://article.gmane.org/gmane.comp.jakarta.turbine.maven.user/25998
Jorg
Niclas Hedhman wrote:
I didn't mean going with Maven 1 first, but just hang in there with Ant and
await a final release.
We are doing this with 2.1.x.
For 2.2, I think we should not be afraid of innovate and remember: the
maven people are friends (just like the ant people were) and they
Ok, let's start with a simple description on how to get m2 build running
for Cocoon trunk. Actually, it's not that easy :)
First you have to install m2 latest from SVN, the alpha-3 does NOT work
for us! You'll find a description on how to do this here:
Carsten Ziegeler wrote:
Ok, let's start with a simple description on how to get m2 build running
for Cocoon trunk. Actually, it's not that easy :)
First you have to install m2 latest from SVN, the alpha-3 does NOT work
for us! You'll find a description on how to do this here:
13 matches
Mail list logo
