Re: .m2 folder creation
Am Mon, 21 Apr 2014 18:52:44 -0700 (PDT) schrieb Mayank mayankanan...@gmail.com: I have started using by unzipping its binary.zip and setting the environment variables and got the mvn -version executed successfully but after that none of the command worked, probably because of setting.xml (not sure, please clarify). You need to tell us what command you tried, what error message or result you got and what you did expected. Then I got another idea and integrated the maven plugin in Eclipse Kepler and got that successful too. Then I tried to create jsf archetype project in eclipse, but I did not get the correct structure and facet option (though I also tried to change the builder and nature in .project file). Again, some more details would be nice. Do you have unblocked internet access? Now I am confused, I want to use mvn plugin for eclipse and confusion is does successfully integrating the maven plugin with eclipse is enough or does env variable creation and unzipped maven folder are mandatory ? The m2e plugin in eclipse brings its own maven version, you dont need to (but can) install an external version. And since I noticed about .m2 folder after two different tries so I am not sure which one actually created it ? All maven commands which need the local repository will create the .m2 dir if it was not present before. Greetings Bernd - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: .m2 folder creation
Hi, There are two ways to generate maven project structure: First way: Download the maven package, unzip it and set the maven path up to bin enviornmnet variable. Now once you are done with this you can generate the maven project structure through command prompt using below command: mvn archetype:generate -DgroupId=com.dns-DartifactId=hibernatemappingexample -DarchetypeArtifactId=maven-archetype-quickstart -DinteractiveMode=false Second way: Install m2e plugin in eclipse to enable support of maven in eclipse. To make a maven project structure: File-project-maven project- select the archetype you want, then provide the group id and artifact id. By default .m2 directory (contains all jar dependency) is created inside C:\Users\reena.upadhyay location. You can change its location in conf/settings.xml I hope this answers your question :) On Tue, Apr 22, 2014 at 7:22 AM, Mayank mayankanan...@gmail.com wrote: Hi, I am new to Maven, so need some help !! I have started using by unzipping its binary.zip and setting the environment variables and got the mvn -version executed successfully but after that none of the command worked, probably because of setting.xml (not sure, please clarify). Then I got another idea and integrated the maven plugin in Eclipse Kepler and got that successful too. Then I tried to create jsf archetype project in eclipse, but I did not get the correct structure and facet option (though I also tried to change the builder and nature in .project file). Now I am confused, I want to use mvn plugin for eclipse and confusion is does successfully integrating the maven plugin with eclipse is enough or does env variable creation and unzipped maven folder are mandatory ? And since I noticed about .m2 folder after two different tries so I am not sure which one actually created it ? Kindly help urgently!! -- View this message in context: http://maven.40175.n5.nabble.com/m2-folder-creation-tp5791740.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Generating war and Jar from same codebase
#2 is the Maven way in a structural sense, although you shouldn't put all dependencies in the parent but where they are used. So the jar project will get most of the deps and the war project will have a dependency to the jar artifact (and possibly some other web related deps). Also, as the jar project already produces a jar artifact as the main artifact, you only need to add the m-assembly-p to produce the secondary fat jar artifact. /Anders On Tue, Apr 22, 2014 at 2:18 AM, Narayanan K knarayana...@gmail.com wrote: Hi We have a default pom file with packaging war for our codebase. From the same code base we also want to generate a normal jar and a fat jar with dependencies. Currently solution that has been implemented is another pom-jar.xml file that has the packaging as jar and maven-assembly-plugin to generate the jar with dependencies. We use mvn install -f pom-jar.xml. But we are in a situation where if any new dependency is added to pom.xml, we need to add to pom-jar.xml as well as it is the same codebase. To avoid this we thought of couple of solutions - 1. Add maven-jar-plugin and maven-assembly-plugin to the default pom with packaging war - so it generates a war file, a normal jar file and fat jar out of the same pom. So we can do away with the pom-jar.xml. Not sure if this is a good solution. We tried this, but this is working well only in maven 3.0.4. The assembly plugin is not working well with Maven 2 (which is in our build environment) while generating the fat jar. 2. Have a parent pom and put all the dependencies and plugins in that and have 2 child poms in the same codebase with different names inherit from parent pom, one that has packaging of war that generates war file and the other child pom has packaging jar with maven assembly plugin to generate both normal and fat jar. And all new dependencies need to be added only to parent pom. This solution will make us have 3 pom files in codebase, doesnt look very elegant, but will solve our dependency management issues between the 2 packaging. Are these good solutions? Is there any other good solution available for this scenario ? Regards Narayanan - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Generating war and Jar from same codebase
I believe the Tomcat Plugin offers a way to create a fat jar with tomcat + your deps. http://tomcat.apache.org/maven-plugin-2.2/executable-war-jar.html Wouldn't it help perhaps? -- -- Aldrin Leal, ald...@leal.eng.br Master your EC2-fu! Get the latest ekaterminal public beta http://www.ingenieux.com.br/products/ekaterminal/ On Mon, Apr 21, 2014 at 9:18 PM, Narayanan K knarayana...@gmail.com wrote: Hi We have a default pom file with packaging war for our codebase. From the same code base we also want to generate a normal jar and a fat jar with dependencies. Currently solution that has been implemented is another pom-jar.xml file that has the packaging as jar and maven-assembly-plugin to generate the jar with dependencies. We use mvn install -f pom-jar.xml. But we are in a situation where if any new dependency is added to pom.xml, we need to add to pom-jar.xml as well as it is the same codebase. To avoid this we thought of couple of solutions - 1. Add maven-jar-plugin and maven-assembly-plugin to the default pom with packaging war - so it generates a war file, a normal jar file and fat jar out of the same pom. So we can do away with the pom-jar.xml. Not sure if this is a good solution. We tried this, but this is working well only in maven 3.0.4. The assembly plugin is not working well with Maven 2 (which is in our build environment) while generating the fat jar. 2. Have a parent pom and put all the dependencies and plugins in that and have 2 child poms in the same codebase with different names inherit from parent pom, one that has packaging of war that generates war file and the other child pom has packaging jar with maven assembly plugin to generate both normal and fat jar. And all new dependencies need to be added only to parent pom. This solution will make us have 3 pom files in codebase, doesnt look very elegant, but will solve our dependency management issues between the 2 packaging. Are these good solutions? Is there any other good solution available for this scenario ? Regards Narayanan - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Generating war and Jar from same codebase
On 22 April 2014 01:18, Narayanan K knarayana...@gmail.com wrote: Hi We have a default pom file with packaging war for our codebase. From the same code base we also want to generate a normal jar and a fat jar with dependencies. Currently solution that has been implemented is another pom-jar.xml file that has the packaging as jar and maven-assembly-plugin to generate the jar with dependencies. We use mvn install -f pom-jar.xml. But we are in a situation where if any new dependency is added to pom.xml, we need to add to pom-jar.xml as well as it is the same codebase. To avoid this we thought of couple of solutions - 1. Add maven-jar-plugin and maven-assembly-plugin to the default pom with packaging war - so it generates a war file, a normal jar file and fat jar out of the same pom. So we can do away with the pom-jar.xml. Not sure if this is a good solution. We tried this, but this is working well only in maven 3.0.4. The assembly plugin is not working well with Maven 2 (which is in our build environment) while generating the fat jar. 2. Have a parent pom and put all the dependencies and plugins in that and have 2 child poms in the same codebase with different names inherit from parent pom, one that has packaging of war that generates war file and the other child pom has packaging jar with maven assembly plugin to generate both normal and fat jar. And all new dependencies need to be added only to parent pom. This solution will make us have 3 pom files in codebase, doesnt look very elegant, actually depends on your point of view. To me this is the more elegant solution as you clearly see the relationship between inputs (pom.xml) and outputs (artifacts, e.g. jars wars, etc) but will solve our dependency management issues between the 2 packaging. Are these good solutions? Is there any other good solution available for this scenario ? Regards Narayanan - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
can't download jar is my server blacklisted
Hi Is my new vps blocked from the maven repo i have tried different mirrors same problem 94.247.169.236 server: ping repo.maven.apache.org (185.31.17.192) wget http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-resources-plugin/2.6/maven-resources-plugin-2.6.jar 2014-04-22 11:24:37 ERROR 404: Not Found. Amazon ec2: ping repo.maven.apache.org (185.31.17.192) wget http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-resources-plugin/2.6/maven-resources-plugin-2.6.jar 2014-04-22 07:18:01 (1.79 MB/s) - ‘maven-resources-plugin-2.6.jar.1’ saved [29519/29519]
Re: .m2 folder creation
Try using the Eclipse STS from Spring. It is Eclipse with all the bits and pieces that you need to do Maven and most Java development. This will save a ton of time every time you need to set up a new workstation or upgrade an existing one. You can use the Eclipse preference screens to manage and understand where Maven is located and which .m2 folder is the real one. It comes with tools to start a new Maven project with the right structure and initial pom files. Ron On 21/04/2014 9:52 PM, Mayank wrote: Hi, I am new to Maven, so need some help !! I have started using by unzipping its binary.zip and setting the environment variables and got the mvn -version executed successfully but after that none of the command worked, probably because of setting.xml (not sure, please clarify). Then I got another idea and integrated the maven plugin in Eclipse Kepler and got that successful too. Then I tried to create jsf archetype project in eclipse, but I did not get the correct structure and facet option (though I also tried to change the builder and nature in .project file). Now I am confused, I want to use mvn plugin for eclipse and confusion is does successfully integrating the maven plugin with eclipse is enough or does env variable creation and unzipped maven folder are mandatory ? And since I noticed about .m2 folder after two different tries so I am not sure which one actually created it ? Kindly help urgently!! -- View this message in context: http://maven.40175.n5.nabble.com/m2-folder-creation-tp5791740.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: can't download jar is my server blacklisted
I am seeing the same error. I also encounter similar issue, could you check if you see the same thing and add your into the mentioned Jira http://maven.40175.n5.nabble.com/Strange-maven-central-response-do-you-see-the-same-thing-td5791549.html Thanks -Dan On Tue, Apr 22, 2014 at 1:39 AM, Lars Carlsson lars.carls...@hiq.se wrote: Hi Is my new vps blocked from the maven repo i have tried different mirrors same problem 94.247.169.236 server: ping repo.maven.apache.org (185.31.17.192) wget http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-resources-plugin/2.6/maven-resources-plugin-2.6.jar 2014-04-22 11:24:37 ERROR 404: Not Found. Amazon ec2: ping repo.maven.apache.org (185.31.17.192) wget http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-resources-plugin/2.6/maven-resources-plugin-2.6.jar 2014-04-22 07:18:01 (1.79 MB/s) - ‘maven-resources-plugin-2.6.jar.1’ saved [29519/29519]
Re: Perforce Maven Integration ??
Hi Brian, since you already upload p4java 2013.1, could you upload the latest 2013.2? [1] Very much appreciated -D [1] http://ftp.perforce.com/perforce/r13.2/bin.java/ On Wed, Apr 16, 2014 at 2:25 PM, Brian Jackson br...@jaxzin.com wrote: On Tue, Apr 15, 2014 at 10:33 PM, Dan Tran dant...@gmail.com wrote: Hello, I am currently not able to get Perforce with SSL connection working. My guess here is both currently built-in perforce provider at maven scm, and the one from Perforce ( p4maven) are not support this new feature yet which is available around 2012. ( also the last p4maven release is around 2011 ) Yeah, Perforce (the company) doesn't support the publishing of p4maven to Central. I had to do it myself using the Sonatype OSSH Repository. is Perforce well supported and used with Maven? Well-supported is debatable since its subjective. Perforce, like many commercial product, often get the same level of open source support when open source alternatives exist (git, svn). are there any Maven shops with Perforce which actively using maven release plugin? Yes, we've been using it for many years to cut releases at ESPN through our CI server. Unfortunately we don't use SSL so I can't help you with your specific issue. Thanks -Dan
Re: Perforce Maven Integration ??
and It solves my issue [1] Thanks -D [1] http://forums.perforce.com/index.php?/topic/3222-p4maven-supports-ssl/ On Tue, Apr 15, 2014 at 7:33 PM, Dan Tran dant...@gmail.com wrote: Hello, I am currently not able to get Perforce with SSL connection working. My guess here is both currently built-in perforce provider at maven scm, and the one from Perforce ( p4maven) are not support this new feature yet which is available around 2012. ( also the last p4maven release is around 2011 ) is Perforce well supported and used with Maven? are there any Maven shops with Perforce which actively using maven release plugin? Thanks -Dan
Re: Generating war and Jar from same codebase
Thanks all for replying. So having a parent pom and inheriting common dependencies to the 2 child poms is the best solution. My new maven project structure will be : . | -- pom.xml (parent pom) | -- pom-war.xml (inherits from parent, generates a war) | -- pom-jar.xml (inherits from parent, generates a jar) There are no modules in the project. All poms are going to be in the root path of the project. 1. Any examples on how to write the parent pom referencing the same codebase for the child poms. Will there be a module tag for parent pom. I understand that the packaging for parent pom will be pom. 2. The child poms will have relativePath in parent tag as ./pom.xml. Please correct me if this is wrong. Thanks Narayanan Narayanan On Tue, Apr 22, 2014 at 12:38 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: On 22 April 2014 01:18, Narayanan K knarayana...@gmail.com wrote: Hi We have a default pom file with packaging war for our codebase. From the same code base we also want to generate a normal jar and a fat jar with dependencies. Currently solution that has been implemented is another pom-jar.xml file that has the packaging as jar and maven-assembly-plugin to generate the jar with dependencies. We use mvn install -f pom-jar.xml. But we are in a situation where if any new dependency is added to pom.xml, we need to add to pom-jar.xml as well as it is the same codebase. To avoid this we thought of couple of solutions - 1. Add maven-jar-plugin and maven-assembly-plugin to the default pom with packaging war - so it generates a war file, a normal jar file and fat jar out of the same pom. So we can do away with the pom-jar.xml. Not sure if this is a good solution. We tried this, but this is working well only in maven 3.0.4. The assembly plugin is not working well with Maven 2 (which is in our build environment) while generating the fat jar. 2. Have a parent pom and put all the dependencies and plugins in that and have 2 child poms in the same codebase with different names inherit from parent pom, one that has packaging of war that generates war file and the other child pom has packaging jar with maven assembly plugin to generate both normal and fat jar. And all new dependencies need to be added only to parent pom. This solution will make us have 3 pom files in codebase, doesnt look very elegant, actually depends on your point of view. To me this is the more elegant solution as you clearly see the relationship between inputs (pom.xml) and outputs (artifacts, e.g. jars wars, etc) but will solve our dependency management issues between the 2 packaging. Are these good solutions? Is there any other good solution available for this scenario ? Regards Narayanan - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Generating war and Jar from same codebase
Code is in jar project. Jar produces x.jar, No code in Parent No code in war. War depends on jar project output x.jar. It includes web resources but no code. Produces x.war. Ron On 22/04/2014 1:15 PM, Narayanan K wrote: Thanks all for replying. So having a parent pom and inheriting common dependencies to the 2 child poms is the best solution. My new maven project structure will be : . | -- pom.xml (parent pom) | -- pom-war.xml (inherits from parent, generates a war) | -- pom-jar.xml (inherits from parent, generates a jar) There are no modules in the project. All poms are going to be in the root path of the project. 1. Any examples on how to write the parent pom referencing the same codebase for the child poms. Will there be a module tag for parent pom. I understand that the packaging for parent pom will be pom. 2. The child poms will have relativePath in parent tag as ./pom.xml. Please correct me if this is wrong. Thanks Narayanan Narayanan On Tue, Apr 22, 2014 at 12:38 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: On 22 April 2014 01:18, Narayanan K knarayana...@gmail.com wrote: Hi We have a default pom file with packaging war for our codebase. From the same code base we also want to generate a normal jar and a fat jar with dependencies. Currently solution that has been implemented is another pom-jar.xml file that has the packaging as jar and maven-assembly-plugin to generate the jar with dependencies. We use mvn install -f pom-jar.xml. But we are in a situation where if any new dependency is added to pom.xml, we need to add to pom-jar.xml as well as it is the same codebase. To avoid this we thought of couple of solutions - 1. Add maven-jar-plugin and maven-assembly-plugin to the default pom with packaging war - so it generates a war file, a normal jar file and fat jar out of the same pom. So we can do away with the pom-jar.xml. Not sure if this is a good solution. We tried this, but this is working well only in maven 3.0.4. The assembly plugin is not working well with Maven 2 (which is in our build environment) while generating the fat jar. 2. Have a parent pom and put all the dependencies and plugins in that and have 2 child poms in the same codebase with different names inherit from parent pom, one that has packaging of war that generates war file and the other child pom has packaging jar with maven assembly plugin to generate both normal and fat jar. And all new dependencies need to be added only to parent pom. This solution will make us have 3 pom files in codebase, doesnt look very elegant, actually depends on your point of view. To me this is the more elegant solution as you clearly see the relationship between inputs (pom.xml) and outputs (artifacts, e.g. jars wars, etc) but will solve our dependency management issues between the 2 packaging. Are these good solutions? Is there any other good solution available for this scenario ? Regards Narayanan - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: DependencyTreeBuilder vs. DependencyGraphBuilder
Hi, Interesting problem, I've just faced, using aether and maven 3.1, I developed a plugin for creating a special kind of 'war' file for a plugin infrastructure. I was using aether directly, I faced the problem aether was changed, so just looking into maven dependency plugin, and looking at some advice mentioned in the network I moved from using aether directly to use maven-dependency-tree library, which isolates me of the problem of what Aether provider is used. Because of the nature of the plugin, I need to use DependencyTree and not DependencyGraph (need the repeated/confict info). So wondering, should I go back to using Aether directly (because of DependencyTree) deprecation, or some replacement for it will be available ? thanks in advance tonio On Wed, Apr 2, 2014 at 10:34 AM, Stefan Ferstl st.fer...@gmail.com wrote: I haven't had any problems so far. I was just confused by DependencyTreeBuilder's Javadoc. It says that (at least I understood it that way) the dependency graph might differ from the dependency resolution in Maven 3. The same Javadoc references an Issue (MSHARED-167) that was solved two years ago. So I was not sure if differences can still occur or not. According to Hervé's reply, differences can still occur. Cheers, Stefan On Wed, Apr 2, 2014 at 2:49 AM, Martin Gainty mgai...@hotmail.com wrote: Stefan A year ago..Herve says r1469697 maven-dependency-tree is fixed for M3 Is this not the case? Martin Date: Tue, 1 Apr 2014 08:29:20 +0200 Subject: DependencyTreeBuilder vs. DependencyGraphBuilder From: st.fer...@gmail.com To: users@maven.apache.org I'm using the org.apache.maven.shared:dependency-tree library to gather dependency information on my projects. In order to get additional information about version conflicts, I prefer to use DependencyTreeBuilder instead of DependencyGraphBuilder. However, the Javadoc of DependencyTreeBuilder says: Notice that it doesn't fail with Maven 3, but when Maven 2 and Maven 3 don't calculate the same transitive dependency result, the tree calculated with this component is consistent with Maven 2 even if run with Maven 3 (see MSHARED-167) The issue MSHARED-167 [1] was closed in June 2012. So may DependencyTreeBuilder still produce different results than DependencyGraphBuilder or is this not an issue anymore? Cheers, Stefan [1] https://jira.codehaus.org/browse/MSHARED-167 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Generating war and Jar from same codebase
My new maven project structure will be : . | -- pom.xml (parent pom) | -- pom-war.xml (inherits from parent, generates a war) | -- pom-jar.xml (inherits from parent, generates a jar) There are no modules in the project. All poms are going to be in the root path of the project. Wrong! You should create two modules; one for the jar project and one for the war project. Follow the Maven standards and you can use any of the many examples of this on the Internet. I believe we haven't pushed the mantra for some time now, so here it comes: Don't fight Maven! /Anders 1. Any examples on how to write the parent pom referencing the same codebase for the child poms. Will there be a module tag for parent pom. I understand that the packaging for parent pom will be pom. 2. The child poms will have relativePath in parent tag as ./pom.xml. Please correct me if this is wrong. Thanks Narayanan Narayanan On Tue, Apr 22, 2014 at 12:38 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: On 22 April 2014 01:18, Narayanan K knarayana...@gmail.com wrote: Hi We have a default pom file with packaging war for our codebase. From the same code base we also want to generate a normal jar and a fat jar with dependencies. Currently solution that has been implemented is another pom-jar.xml file that has the packaging as jar and maven-assembly-plugin to generate the jar with dependencies. We use mvn install -f pom-jar.xml. But we are in a situation where if any new dependency is added to pom.xml, we need to add to pom-jar.xml as well as it is the same codebase. To avoid this we thought of couple of solutions - 1. Add maven-jar-plugin and maven-assembly-plugin to the default pom with packaging war - so it generates a war file, a normal jar file and fat jar out of the same pom. So we can do away with the pom-jar.xml. Not sure if this is a good solution. We tried this, but this is working well only in maven 3.0.4. The assembly plugin is not working well with Maven 2 (which is in our build environment) while generating the fat jar. 2. Have a parent pom and put all the dependencies and plugins in that and have 2 child poms in the same codebase with different names inherit from parent pom, one that has packaging of war that generates war file and the other child pom has packaging jar with maven assembly plugin to generate both normal and fat jar. And all new dependencies need to be added only to parent pom. This solution will make us have 3 pom files in codebase, doesnt look very elegant, actually depends on your point of view. To me this is the more elegant solution as you clearly see the relationship between inputs (pom.xml) and outputs (artifacts, e.g. jars wars, etc) but will solve our dependency management issues between the 2 packaging. Are these good solutions? Is there any other good solution available for this scenario ? Regards Narayanan - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANNOUNCE] Release Mojo's JDepend Maven Plugin version 2.0
Hi, The Mojo team is pleased to announce the release of the JDepend Maven Plugin version 2.0. This plugin produces a nicely formatted metrics report based on your project. http://mojo.codehaus.org/jdepend-maven-plugin/ To get this update, simply specify the version in your project's plugin configuration: plugin groupIdorg.codehaus.mojo/groupId artifactIdjdepend-maven-plugin/artifactId version2.0/version /plugin Release Notes: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=13231version=20128 Bug [MJDEPEND-8] - Add missing scm entry in pom Improvement [MJDEPEND-6] - Stabilize Plugin IT's by using a setup project [MJDEPEND-9] - Improve Usage page [MJDEPEND-10] - State that plugin uses the JDepend library and include link [MJDEPEND-11] - Change the license text. New Feature [MJDEPEND-1] - Add a -no-fork goal Enjoy, The Mojo team. Karl-Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANNOUNCE] Release Mojo's Exec Maven Plugin version 1.3
Hi, The Mojo team is pleased to announce the release of the Exec Maven Plugin version 1.3. The plugin provides 2 goals to help execute system and Java programs. http://mojo.codehaus.org/exec-maven-plugin/ To get this update, simply specify the version in your project's plugin configuration: plugin groupIdorg.codehaus.mojo/groupId artifactIdexec-maven-plugin/artifactId version1.3/version /plugin Release Notes: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11240version=17822 Bug [MEXEC-86] - outputFile support for capturing exec not functional [MEXEC-104] - Cannot pass empty argument to exec goal. [MEXEC-105] - %classpath is fragile when used with commandlineArgs [MEXEC-108] - NPE at EnvironmentUtils.toStrings() Improvements: [MEXEC-66] - ability to add custom classpath together with %classpath placeholder [MEXEC-73] - add configuration for adding additional directories to project classpath [MEXEC-93] - Exec plugin not marked as @threadSafe [MEXEC-107] - Drop @execute phase=validate from ExecJavaMojo [MEXEC-119] - At position of argument to Misconfigured argument, value is null message [MEXEC-122] - Run integration test only by using the profile run-its [MEXEC-123] - use java 5 plexus annotations [MEXEC-125] - Upgrade Plugin Required Maven Version to 2.2.1 [MEXEC-129] - provided scope for maven-plugin-annotation [MEXEC-130] - @threadSafe [MEXEC-131] - commons-exec upgrade to 1.2 [MEXEC-133] - Upgrade to mojo-parent v:33 Task [MEXEC-101] - Migrate plugin to JDK5 Wish [MEXEC-126] - Bring back Maven 2.0.11 Compatibility Enjoy, The Mojo team. Karl-Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Generating war and Jar from same codebase
Have a look at this option: http://maven.apache.org/plugins/maven-war-plugin/war-mojo.html#archiveClasses On 23 April 2014 03:15, Narayanan K knarayana...@gmail.com wrote: Thanks all for replying. So having a parent pom and inheriting common dependencies to the 2 child poms is the best solution. My new maven project structure will be : . | -- pom.xml (parent pom) | -- pom-war.xml (inherits from parent, generates a war) | -- pom-jar.xml (inherits from parent, generates a jar) There are no modules in the project. All poms are going to be in the root path of the project. 1. Any examples on how to write the parent pom referencing the same codebase for the child poms. Will there be a module tag for parent pom. I understand that the packaging for parent pom will be pom. 2. The child poms will have relativePath in parent tag as ./pom.xml. Please correct me if this is wrong. Thanks Narayanan Narayanan On Tue, Apr 22, 2014 at 12:38 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: On 22 April 2014 01:18, Narayanan K knarayana...@gmail.com wrote: Hi We have a default pom file with packaging war for our codebase. From the same code base we also want to generate a normal jar and a fat jar with dependencies. Currently solution that has been implemented is another pom-jar.xml file that has the packaging as jar and maven-assembly-plugin to generate the jar with dependencies. We use mvn install -f pom-jar.xml. But we are in a situation where if any new dependency is added to pom.xml, we need to add to pom-jar.xml as well as it is the same codebase. To avoid this we thought of couple of solutions - 1. Add maven-jar-plugin and maven-assembly-plugin to the default pom with packaging war - so it generates a war file, a normal jar file and fat jar out of the same pom. So we can do away with the pom-jar.xml. Not sure if this is a good solution. We tried this, but this is working well only in maven 3.0.4. The assembly plugin is not working well with Maven 2 (which is in our build environment) while generating the fat jar. 2. Have a parent pom and put all the dependencies and plugins in that and have 2 child poms in the same codebase with different names inherit from parent pom, one that has packaging of war that generates war file and the other child pom has packaging jar with maven assembly plugin to generate both normal and fat jar. And all new dependencies need to be added only to parent pom. This solution will make us have 3 pom files in codebase, doesnt look very elegant, actually depends on your point of view. To me this is the more elegant solution as you clearly see the relationship between inputs (pom.xml) and outputs (artifacts, e.g. jars wars, etc) but will solve our dependency management issues between the 2 packaging. Are these good solutions? Is there any other good solution available for this scenario ? Regards Narayanan - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
BUILD FAILED - apache-maven-3.2.1
Dear Maven developers,
I am trying to install apache-maven-3.2.1
http://ftp.unicamp.br/pub/apache/maven/maven-3/3.2.1/source/apache-maven-3.2.1-src.tar.gz
with the following variables
export M2_HOME=/opt/apache-maven-3-2-1-SNAPSHOT
PATH=$M2_HOME/bin:$PATH
under linux and I am getting the error below. Could you please help me
installing Maven?
Regards,
Ewerton
--
ewerton@deb6:/opt/apache-maven-3.2.1$ ant
Buildfile: /opt/apache-maven-3.2.1/build.xml
clean-bootstrap:
initTaskDefs:
[echo] Building Apache Maven ...
isMavenHomeSet:
init:
[echo] maven.home = /opt/apache-maven-3-2-1-SNAPSHOT
[echo] maven.repo.local = /home/ewerton/.m2/repository
[echo] distributionId = apache-maven
[echo] distributionName = Apache Maven
[echo] distributionDirectory = apache-maven
prompt-maven-home-exists:
[input] WARNING:
[input] The specified target directory
[input] /opt/apache-maven-3-2-1-SNAPSHOT
[input] already exists. It will be deleted and overwritten by the build.
[input] Do you want to continue? (yes, [no])
yes
pull:
[copy] Copying 1 file to /opt/apache-maven-3.2.1
[delete] Deleting: /opt/apache-maven-3.2.1/dependencies.xml
generate-sources:
[mkdir] Created dir: /opt/apache-maven-3.2.1/bootstrap/target
[mkdir] Created dir:
/opt/apache-maven-3.2.1/bootstrap/target/generated-sources
[modello] Generating sources for maven-model/src/main/mdo/maven.mdo
[modello] Generating sources for
maven-plugin-api/src/main/mdo/lifecycle.mdo
[modello] Generating sources for
maven-model-builder/src/main/mdo/profiles.mdo
[modello] Generating sources for maven-settings/src/main/mdo/settings.mdo
[modello] Generating sources for maven-core/src/main/mdo/toolchains.mdo
[modello] Generating sources for
maven-repository-metadata/src/main/mdo/metadata.mdo
[modello] Generating sources for maven-compat/src/main/mdo/profiles.mdo
[modello] Generating sources for maven-compat/src/main/mdo/paramdoc.mdo
compile-boot:
[mkdir] Created dir: /opt/apache-maven-3.2.1/bootstrap/target/classes
[javac] Compiling 742 source files to
/opt/apache-maven-3.2.1/bootstrap/target/classes
[javac] failed to read ecj.jar (reconfigure with --with-ecj-jar):
/usr/share/java/eclipse-ecj.jar
[javac] failed to load org.eclipse.jdt.internal.compiler.batch.Main
from ecj.jar: /usr/share/java/eclipse-ecj.jar
[javac] java.lang.ClassNotFoundException:
org.eclipse.jdt.internal.compiler.batch.Main not found in
java.net.URLClassLoader{urls=[file:/usr/share/java/eclipse-ecj.jar],
parent=gnu.gcj.runtime.SystemClassLoader{urls=[file:/usr/share/ant/lib/ant-launcher.jar,file:/usr/share/java/xmlParserAPIs.jar,file:/usr/share/java/xercesImpl.jar],
parent=gnu.gcj.runtime.ExtensionClassLoader{urls=[], parent=null}}}
[javac]at java.net.URLClassLoader.findClass(libgcj.so.10)
[javac]at java.lang.ClassLoader.loadClass(libgcj.so.10)
[javac]at java.lang.ClassLoader.loadClass(libgcj.so.10)
[javac]at com.sun.tools.javac.Main.clinit(Main.java:91)
[javac]at java.lang.Class.initializeClass(libgcj.so.10)
[javac]at java.lang.Class.forName(libgcj.so.10)
[javac]at java.lang.Class.forName(libgcj.so.10)
[javac]at
org.apache.tools.ant.taskdefs.compilers.CompilerAdapterFactory.doesModernCompilerExist(CompilerAdapterFactory.java:165)
[javac]at
org.apache.tools.ant.taskdefs.compilers.CompilerAdapterFactory.getCompiler(CompilerAdapterFactory.java:124)
[javac]at
org.apache.tools.ant.taskdefs.Javac.compile(Javac.java:1088)
[javac]at
org.apache.tools.ant.taskdefs.Javac.execute(Javac.java:906)
[javac]at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
[javac]at java.lang.reflect.Method.invoke(libgcj.so.10)
[javac]at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
[javac]at org.apache.tools.ant.Task.perform(Task.java:348)
[javac]at org.apache.tools.ant.Target.execute(Target.java:390)
[javac]at org.apache.tools.ant.Target.performTasks(Target.java:411)
[javac]at
org.apache.tools.ant.Project.executeSortedTargets(Project.java:1360)
[javac]at
org.apache.tools.ant.Project.executeTarget(Project.java:1329)
[javac]at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
[javac]at
org.apache.tools.ant.Project.executeTargets(Project.java:1212)
[javac]at org.apache.tools.ant.Main.runBuild(Main.java:801)
[javac]at org.apache.tools.ant.Main.startAnt(Main.java:218)
[javac]at
org.apache.tools.ant.launch.Launcher.run(Launcher.java:280)
[javac]at
org.apache.tools.ant.launch.Launcher.main(Launcher.java:109)
BUILD FAILED
/opt/apache-maven-3.2.1/build.xml:226: java.lang.ExceptionInInitializerError
at java.lang.Class.initializeClass(libgcj.so.10)
at java.lang.Class.forName(libgcj.so.10)
at
Re: Error of after running 'mvn package' command
I faced exact same issue , replying to this mail chain so that other can benefit. It looks like Hudson project is moved to eclipse.org hence in plugin pom.xml we need to changed parent declaration as below parent groupIdorg.eclipse.hudson.plugins/groupId artifactIdhudson-plugin-parent/artifactId version3.0.0/version /parent BTW in your machine if you first build the project for Jenkins and then Hudson you won't encounter this issue. This happens only when you are building Hudson plugin freshly where Jenkins dependent jars does not exist. -- View this message in context: http://maven.40175.n5.nabble.com/Error-of-after-running-mvn-package-command-tp5762649p5791803.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: BUILD FAILED - apache-maven-3.2.1
I am trying to install apache-maven-3.2.1 http://ftp.unicamp.br/pub/apache/maven/maven-3/3.2.1/source/apache-maven-3.2.1-src.tar.gz No, you are trying to BUILD Maven 3.2.1. If you simply want to install it, grab the binaries. Who's JDK/JVM are you using and what version is it? Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Trouble downloading a dependency
Output from Maven... Downloading: http://repo1.maven.org/maven2/org/jboss/spec/javax/ejb/jboss-ejb-api_3.2_spec/1.0.0.Final/jboss-ejb-api_3.2_spec-1.0.0.Final.pom ...and then this error: connect: Address is invalid on local machine, or port is not valid on remote machine I don't understand the error. If I paste the URL into my browser, the POM exists. I even turned off my antivirus/firewall to make sure nothing was blocking Java -- and still the same result. Any clues what could be causing this? -- Cheers, Paul
Re: Generating war and Jar from same codebase
Hi Anders The codebase is the same. So having 2 separate directories (for modules) and pom in each of them is not required right ? I can have modules in parent pom to specify the 2 child poms that are present in the same project level. Tried below and seems it is working. parent pom will have : modules modulepom-war.xml/module modulepom-jar.xml/module modules In both child poms, parent relativePath./pom-parent.xml/relativePath /parent Currently including the jar artifact dependency in war project cannot be done due to some restrictions in our development. Narayanan On Tue, Apr 22, 2014 at 11:37 AM, Anders Hammar and...@hammar.net wrote: My new maven project structure will be : . | -- pom.xml (parent pom) | -- pom-war.xml (inherits from parent, generates a war) | -- pom-jar.xml (inherits from parent, generates a jar) There are no modules in the project. All poms are going to be in the root path of the project. Wrong! You should create two modules; one for the jar project and one for the war project. Follow the Maven standards and you can use any of the many examples of this on the Internet. I believe we haven't pushed the mantra for some time now, so here it comes: Don't fight Maven! /Anders 1. Any examples on how to write the parent pom referencing the same codebase for the child poms. Will there be a module tag for parent pom. I understand that the packaging for parent pom will be pom. 2. The child poms will have relativePath in parent tag as ./pom.xml. Please correct me if this is wrong. Thanks Narayanan Narayanan On Tue, Apr 22, 2014 at 12:38 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: On 22 April 2014 01:18, Narayanan K knarayana...@gmail.com wrote: Hi We have a default pom file with packaging war for our codebase. From the same code base we also want to generate a normal jar and a fat jar with dependencies. Currently solution that has been implemented is another pom-jar.xml file that has the packaging as jar and maven-assembly-plugin to generate the jar with dependencies. We use mvn install -f pom-jar.xml. But we are in a situation where if any new dependency is added to pom.xml, we need to add to pom-jar.xml as well as it is the same codebase. To avoid this we thought of couple of solutions - 1. Add maven-jar-plugin and maven-assembly-plugin to the default pom with packaging war - so it generates a war file, a normal jar file and fat jar out of the same pom. So we can do away with the pom-jar.xml. Not sure if this is a good solution. We tried this, but this is working well only in maven 3.0.4. The assembly plugin is not working well with Maven 2 (which is in our build environment) while generating the fat jar. 2. Have a parent pom and put all the dependencies and plugins in that and have 2 child poms in the same codebase with different names inherit from parent pom, one that has packaging of war that generates war file and the other child pom has packaging jar with maven assembly plugin to generate both normal and fat jar. And all new dependencies need to be added only to parent pom. This solution will make us have 3 pom files in codebase, doesnt look very elegant, actually depends on your point of view. To me this is the more elegant solution as you clearly see the relationship between inputs (pom.xml) and outputs (artifacts, e.g. jars wars, etc) but will solve our dependency management issues between the 2 packaging. Are these good solutions? Is there any other good solution available for this scenario ? Regards Narayanan - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Generating war and Jar from same codebase
If you are going to get serious about development, you should install a Maven repo. We use the Community version of Nexus and it works very well. What are the restrictions on your development? Almost every other company that uses Maven works as Anders suggests. Ron On 23/04/2014 12:15 AM, Narayanan K wrote: Hi Anders The codebase is the same. So having 2 separate directories (for modules) and pom in each of them is not required right ? I can have modules in parent pom to specify the 2 child poms that are present in the same project level. Tried below and seems it is working. parent pom will have : modules modulepom-war.xml/module modulepom-jar.xml/module modules In both child poms, parent relativePath./pom-parent.xml/relativePath /parent Currently including the jar artifact dependency in war project cannot be done due to some restrictions in our development. Narayanan On Tue, Apr 22, 2014 at 11:37 AM, Anders Hammar and...@hammar.net wrote: My new maven project structure will be : . | -- pom.xml (parent pom) | -- pom-war.xml (inherits from parent, generates a war) | -- pom-jar.xml (inherits from parent, generates a jar) There are no modules in the project. All poms are going to be in the root path of the project. Wrong! You should create two modules; one for the jar project and one for the war project. Follow the Maven standards and you can use any of the many examples of this on the Internet. I believe we haven't pushed the mantra for some time now, so here it comes: Don't fight Maven! /Anders 1. Any examples on how to write the parent pom referencing the same codebase for the child poms. Will there be a module tag for parent pom. I understand that the packaging for parent pom will be pom. 2. The child poms will have relativePath in parent tag as ./pom.xml. Please correct me if this is wrong. Thanks Narayanan Narayanan On Tue, Apr 22, 2014 at 12:38 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: On 22 April 2014 01:18, Narayanan K knarayana...@gmail.com wrote: Hi We have a default pom file with packaging war for our codebase. From the same code base we also want to generate a normal jar and a fat jar with dependencies. Currently solution that has been implemented is another pom-jar.xml file that has the packaging as jar and maven-assembly-plugin to generate the jar with dependencies. We use mvn install -f pom-jar.xml. But we are in a situation where if any new dependency is added to pom.xml, we need to add to pom-jar.xml as well as it is the same codebase. To avoid this we thought of couple of solutions - 1. Add maven-jar-plugin and maven-assembly-plugin to the default pom with packaging war - so it generates a war file, a normal jar file and fat jar out of the same pom. So we can do away with the pom-jar.xml. Not sure if this is a good solution. We tried this, but this is working well only in maven 3.0.4. The assembly plugin is not working well with Maven 2 (which is in our build environment) while generating the fat jar. 2. Have a parent pom and put all the dependencies and plugins in that and have 2 child poms in the same codebase with different names inherit from parent pom, one that has packaging of war that generates war file and the other child pom has packaging jar with maven assembly plugin to generate both normal and fat jar. And all new dependencies need to be added only to parent pom. This solution will make us have 3 pom files in codebase, doesnt look very elegant, actually depends on your point of view. To me this is the more elegant solution as you clearly see the relationship between inputs (pom.xml) and outputs (artifacts, e.g. jars wars, etc) but will solve our dependency management issues between the 2 packaging. Are these good solutions? Is there any other good solution available for this scenario ? Regards Narayanan -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Generating war and Jar from same codebase
On 23 April 2014 13:45, Narayanan K knarayana...@gmail.com wrote: Hi Anders The codebase is the same. So having 2 separate directories (for modules) and pom in each of them is not required right ? I can have modules in parent pom to specify the 2 child poms that are present in the same project level. Tried below and seems it is working. parent pom will have : modules modulepom-war.xml/module modulepom-jar.xml/module modules Please have a look at the freely available books at http://maven.apache.org/articles.html Spending a few hours reading about how things should be done and the concepts behind them will be your best use of time. This will help boost your knowledge and help you to articulate your questions to get the best answers in the future.
Re: Trouble downloading a dependency
Web proxy not configured for Maven? /Anders (mobile) Den 23 apr 2014 05:10 skrev Paul Benedict pbened...@apache.org: Output from Maven... Downloading: http://repo1.maven.org/maven2/org/jboss/spec/javax/ejb/jboss-ejb-api_3.2_spec/1.0.0.Final/jboss-ejb-api_3.2_spec-1.0.0.Final.pom ...and then this error: connect: Address is invalid on local machine, or port is not valid on remote machine I don't understand the error. If I paste the URL into my browser, the POM exists. I even turned off my antivirus/firewall to make sure nothing was blocking Java -- and still the same result. Any clues what could be causing this? -- Cheers, Paul
