[
https://issues.apache.org/jira/browse/CAMEL-3799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022133#comment-13022133
]
Babak Vahdat commented on CAMEL-3799:
-------------------------------------
Claus,
I'm really sorry for the irritation I caused, as my answer to you on the user
forum was just too speedy! Unfortunately I've got still exactly the same issue
having the following setup:
D:\Data\eclipse-ws\camel-trunk>mvn --version
Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)
Maven home: P:\My Documents\dev\env\apache-maven-3.0.3\bin\..
Java version: 1.6.0_24, vendor: Sun Microsystems Inc.
Java home: C:\Program Files\Java\jdk1.6.0_24\jre
Default locale: de_CH, platform encoding: Cp1252
OS name: "windows xp", version: "5.1", arch: "x86", family: "windows"
So I tell you how I try to build and maybe you can tell me where I'm going
wrong. I've checked out the camel trunk under "D:\Data\eclipse-ws\camel-trunk"
and go through the following steps on this directory:
D:\Data\eclipse-ws\camel-trunk>mvn clean // just to make it sure that I've got
no "dead body" hidden somewhere under the "target" directories
That goes well. Then as it's described @ http://camel.apache.org/building.html
I do
set MAVEN_OPTS=-Xmx512m -XX:MaxPermSize=512m
That goes also well. Please note that I set the maximal heap size to just 512
and not 1024, as otherwise maven will fail to start (will not be able to
allocate that much heap space on my machine). Then I do:
D:\Data\eclipse-ws\camel-trunk>mvn install -Pfastinstall
That goes smooth as well, but with that I just skipped the execution of the
unit tests, so afterwards I simply do
D:\Data\eclipse-ws\camel-trunk>mvn test
That still fails as I've already reported here:
http://camel.465427.n5.nabble.com/Camel-release-2-8-tt4305340.html#a4305861#none
When I also try to do:
D:\Data\eclipse-ws\camel-trunk>mvn eclipse:clean eclipse:eclipse
It also fails with the effect I have already reported here:
https://issues.apache.org/jira/browse/CAMEL-3837
So I simply wonder how it's possible that all the steps above work on your
box!!!
Again please accept my apologies for my speedy reply on the user forum...
> maven eclipse goal failure
> --------------------------
>
> Key: CAMEL-3799
> URL: https://issues.apache.org/jira/browse/CAMEL-3799
> Project: Camel
> Issue Type: Bug
> Components: tooling
> Affects Versions: 2.7.0
> Reporter: Hadrian Zbarcea
> Priority: Minor
>
> The error is:
> {code}
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Request to merge when 'filtering' is not identical. Original=resource
> src/main/resources: output=target/classes, include=[], exclude=[**/*.java],
> test=false, filtering=false, merging with=resource src/main/resources:
> output=target/classes, include=[**/archetype-metadata.xml],
> exclude=[**/*.java], test=false, filtering=true
> {code}
> and it seems to be resolved in the upcoming maven-eclipse-plugin:2.9.0 (see
> [MECLIPSE-576|http://jira.codehaus.org/browse/MECLIPSE-576]). An update to
> the new release of the plugin, once available, should resolve this.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
