Hi
Yes it does take time to do a clean rebuild ;) And you need to
increase the memory settings on Maven to let it be able to compile it
all.
The snapshorts is deployed on a public maven server
http://activemq.apache.org/camel/download.html
Apache snapshots
http://people.apache.org/repo/m2-snapshot-repository
http://people.apache.org/repo/m2-snapshot-repository/org/apache/camel/apache-camel/
So you can add the apache m2 snapshot in your pom.xml and you are off
to go.
<repository>
<id>apache.snapshots</id>
<name>Apache Development Snapshot Repository</name>
<url>http://people.apache.org/repo/m2-snapshot-repository</url>
<releases>
<enabled>false</enabled>
</releases>
<snapshots>
<enabled>true</enabled>
</snapshots>
</repository>
Med venlig hilsen
Claus Ibsen
......................................
Silverbullet
Skovsgårdsvænget 21
8362 Hørning
Tlf. +45 2962 7576
Web: www.silverbullet.dk
-----Original Message-----
From: Christian Schneider [mailto:[EMAIL PROTECTED] Sent: 6.
juli 2008 12:22
To: [email protected]
Subject: Re: Can not compile examples from 1.4 snapshot
I just tried to compile the snapshot from source. The first thing I
must say ... it takes ages. So this is sure no way to get people to
test the snapshots.
The other thing is that I am getting an out of memory error at the
camel cxf example while compiling.
I think it would be better if you could deploy the snapshot to a
maven repository. So people could use the binary download wwithout
compiling all themselves.
In any case there should be a description somewhere that the examples
from the binary distro will only run if you first compile from
source. For me this was not clear at the start.
Greetings
Christian
-----
[INFO] Compiling 27 source files to
C:\java\apache-camel-1.4-SNAPSHOT\src\examples\camel-example-cxf\target\classes
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Compilation failure
Failure executing javac, but could not parse the error:
The system is out of resources.
Consult the following stack trace for details.
java.lang.OutOfMemoryError: Java heap space
at
com.sun.tools.javac.zip.ZipFileIndex$ZipDirectory.findCENRecord(ZipFileIndex.java:698)
at
com.sun.tools.javac.zip.ZipFileIndex$ZipDirectory.<init>(ZipFileIndex.java:665)
at
com.sun.tools.javac.zip.ZipFileIndex.checkIndex(ZipFileIndex.java:260)
at
com.sun.tools.javac.zip.ZipFileIndex.<init>(ZipFileIndex.java:209)
at
com.sun.tools.javac.zip.ZipFileIndex.getZipFileIndex(ZipFileIndex.java:115)
at
com.sun.tools.javac.util.DefaultFileManager.openArchive(DefaultFileManager.java:645)
at
com.sun.tools.javac.util.DefaultFileManager.listDirectory(DefaultFileManager.java:325)
at
com.sun.tools.javac.util.DefaultFileManager.list(DefaultFileManager.java:872)
at
com.sun.tools.javac.jvm.ClassReader.fillIn(ClassReader.java:2077)
at
com.sun.tools.javac.jvm.ClassReader.complete(ClassReader.java:1781)
at com.sun.tools.javac.code.Symbol.complete(Symbol.java:386)
at com.sun.tools.javac.comp.Enter.visitTopLevel(Enter.java:272)
at
com.sun.tools.javac.tree.JCTree$JCCompilationUnit.accept(JCTree.java:446)
at com.sun.tools.javac.comp.Enter.classEnter(Enter.java:236)
at com.sun.tools.javac.comp.Enter.classEnter(Enter.java:250)
at com.sun.tools.javac.comp.Enter.complete(Enter.java:444)
at com.sun.tools.javac.comp.Enter.main(Enter.java:429)
at
com.sun.tools.javac.main.JavaCompiler.enterTrees(JavaCompiler.java:819)
at
com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:727)
at com.sun.tools.javac.main.Main.compile(Main.java:353)
at com.sun.tools.javac.main.Main.compile(Main.java:279)
at com.sun.tools.javac.main.Main.compile(Main.java:270)
at com.sun.tools.javac.Main.compile(Main.java:87)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.codehaus.plexus.compiler.javac.JavacCompiler.compileInProcess(JavacCompiler.java:420)
at
org.codehaus.plexus.compiler.javac.JavacCompiler.compile(JavacCompiler.java:141)
at
org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:493)
at
org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:114)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
Willem Jiang schrieb:
Hi ,
If you are running the example for source code, you'd better run
"mvn install -Dtest=false" from the root directory to install the
snapshot artifacts in your local maven repository first.
Willem
Christian Schneider wrote:
I have tried to run the examples from the 1.4 snapshot. Like
described in
http://activemq.apache.org/camel/running-examples.html
mvn exec:java
I get the following error:
Cannot find parent: org.apache.camel:camel-parent for project:
null:examples:pom:null for project null:examples:
It seems the examples need a parent pom that is not existing in the
distribution. So probably this can be fixed by adding the parent
pom to the distribution. Though I think the concept of a parent pom
for examples is a bad thing in general.
As people often want to start their own project with the example
code I think each example should be able to exist on it´s own and
so it should not need a parent pom.
Is this a good idea?
Greeting
Christian
