mvn install creates a jar file of the code in your current project. The
pom is copied for information. It is not necessary to run thee project.
The dependencies are not copied by mvn install. They are copied by mvn
dependency:copy-dependencies
So to run your main class use:
java -cp target/dependencies/*;target/yourproject.jar YourMain
Christian
Am 08.10.2011 16:09, schrieb newbiee:
Thank you all for the feeback.
Here is the result of executing
1. MVN INSTALL and
2. mvn dependency:copy-dependencies
1. mvn install: it created a jar file which contains the following:
i. log4j.properties
ii. META-INF folder which contains MANIFEST.MF and a package. The package
contains pom.properties and pom.xml
ii. Another folder contains the class files
I don't see the dependencies in the jar file.
2. mvn dependency:copy-dependencies: it created a folder "dependency" which
contains all the camel jar files.
please let me know why mvn install did copy all the dependencies in JAR file
and instead it contains POM file.
--
View this message in context:
http://camel.465427.n5.nabble.com/running-a-CAMEL-exmple-tp4881222p4882849.html
Sent from the Camel - Users mailing list archive at Nabble.com.
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
