How to perform ordered tasks in Maven2 build
Hi, I am trying to migrate a Java application built by Ant to Maven2. among other the build perform the following operations: 1) Running a javadoc doclet to find annotated Java files to be externalize later as web services 2) compile a small part of the code for step 3 3) run Axis java2wsdl on the compiled code from step 2 4) produce java code with wsdl2java on the wsdl files from step 3 5) compile the entire code when trying to mavenize the process I can accomplish each task at a time but fail to achieve them all in that order. to demonstrate my pom and not load you with details I'll show the following snippet: build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId version2.6.1/version executions execution idaggregate/id phasegenerate-sources/phase goals goalaggregate/goal /goals configuration.../configuration /execution /executions /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId version2.1/version executions execution idcompileWSfiles/id goals goalcompile/goal /goals phasegenerate-sources/phase configuration includes !-- include 3 source files -- /includes /configuration /execution /executions /plugin plugin groupIdorg.codehaus.mojo/groupId artifactIdaxistools-maven-plugin/artifactId version1.3/version dependencies dependency groupIdaxis/groupId artifactIdaxis/artifactId version1.3/version /dependency /dependencies executions execution idjava2wsdl/id phasegenerate-sources/phase goals goaljava2wsdl/goal /goals configuration.../configuration /execution execution idwsdl2java/id phasegenerate-sources/phase goals goalwsdl2java/goal /goals configuration.../configuration /execution /executions /plugin /plugins I pinned all of the build executions on the generate-sources phase and as far as I know they should run in the order they are defined in the pom. The main problem is that I have no control on the order of things and it is obviously important here as every step output is the next step input. any suggestions? Thanks, Ronen. This e-mail message may contain confidential, commercial or privileged information that constitutes proprietary information of Comverse Technology or its subsidiaries. If you are not the intended recipient of this message, you are hereby notified that any review, use or distribution of this information is absolutely prohibited and we request that you delete all copies and contact us by e-mailing to: secur...@comverse.com. Thank You.
RE: auto code format eclipse .settings
I don't really agree here. I think it's pretty much on a project level. I have different projects in my workspace that has different formatting requirements. And in my project, we have the exported xml-file version controlled. I defenetly think it would be great if the maven-eclipse-plugin could automatically set (if it can't already). Like it can with checkstyle. To me, that's what the maven-eclipse-plugin is about, configuring eclipse in every way needed for the project. Is that an incorrect assumption? /Ludwig -Original Message- From: Barrie Treloar [mailto:baerr...@gmail.com] Sent: den 18 mars 2010 00:36 To: Maven Users List Subject: Re: auto code format eclipse .settings Code formatting tends to be a workspace level thing rather than a per project setting. So you are probably better off doing this manually, since its a once off task. As others have pointed out, if it is a per-project file (e.g. like a checkstyle configuration file) then you can use the configuration additionalConfig file section to specify the files contents. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to perform ordered tasks in Maven2 build
On 18 March 2010 07:11, Perez Ronen ronen.pe...@comverse.com wrote: Hi, I am trying to migrate a Java application built by Ant to Maven2. among other the build perform the following operations: 1) Running a javadoc doclet to find annotated Java files to be externalize later as web services 2) compile a small part of the code for step 3 3) run Axis java2wsdl on the compiled code from step 2 4) produce java code with wsdl2java on the wsdl files from step 3 5) compile the entire code Steps 2-3/4 sound like they should be in a separate module. If you move them to a separate module (or two) you can leave things like the compiler plugin bound to the compile phase. By trying to keep things as a single module you are fighting Maven and that is not the Maven Way... you will have a much easier time if you give in and put them in a separate module. -Stephen when trying to mavenize the process I can accomplish each task at a time but fail to achieve them all in that order. to demonstrate my pom and not load you with details I'll show the following snippet: build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId version2.6.1/version executions execution idaggregate/id phasegenerate-sources/phase goals goalaggregate/goal /goals configuration.../configuration /execution /executions /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId version2.1/version executions execution idcompileWSfiles/id goals goalcompile/goal /goals phasegenerate-sources/phase configuration includes !-- include 3 source files -- /includes /configuration /execution /executions /plugin plugin groupIdorg.codehaus.mojo/groupId artifactIdaxistools-maven-plugin/artifactId version1.3/version dependencies dependency groupIdaxis/groupId artifactIdaxis/artifactId version1.3/version /dependency /dependencies executions execution idjava2wsdl/id phasegenerate-sources/phase goals goaljava2wsdl/goal /goals configuration.../configuration /execution execution idwsdl2java/id phasegenerate-sources/phase goals goalwsdl2java/goal /goals configuration.../configuration /execution /executions /plugin /plugins I pinned all of the build executions on the generate-sources phase and as far as I know they should run in the order they are defined in the pom. The main problem is that I have no control on the order of things and it is obviously important here as every step output is the next step input. any suggestions? Thanks, Ronen. This e-mail message may contain confidential, commercial or privileged information that constitutes proprietary information of Comverse Technology or its subsidiaries. If you are not the intended recipient of this message, you are hereby notified that any review, use or distribution of this information is absolutely prohibited and we request that you delete all copies and contact us by e-mailing to: secur...@comverse.com. Thank You.
Re: auto code format eclipse .settings
feel free to submit patches. I have seen this request to configure code-style per project before, but it kind a die out -D On Thu, Mar 18, 2010 at 12:29 AM, Ludwig Magnusson lud...@itcatapult.com wrote: I don't really agree here. I think it's pretty much on a project level. I have different projects in my workspace that has different formatting requirements. And in my project, we have the exported xml-file version controlled. I defenetly think it would be great if the maven-eclipse-plugin could automatically set (if it can't already). Like it can with checkstyle. To me, that's what the maven-eclipse-plugin is about, configuring eclipse in every way needed for the project. Is that an incorrect assumption? /Ludwig -Original Message- From: Barrie Treloar [mailto:baerr...@gmail.com] Sent: den 18 mars 2010 00:36 To: Maven Users List Subject: Re: auto code format eclipse .settings Code formatting tends to be a workspace level thing rather than a per project setting. So you are probably better off doing this manually, since its a once off task. As others have pointed out, if it is a per-project file (e.g. like a checkstyle configuration file) then you can use the configuration additionalConfig file section to specify the files contents. - 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
how to use maven-scm-plugin to checkout a CVS tag
Hi every one,
I have a need to checkout a CVS tag at build time, and have no idea
how to configure the tag. Any advice is greatly appreciated
here is my configuration
configuration
connectionUrl${cvsroot}:mymodule/connectionUrl
/configuration
Thanks
-Dan
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
RE: auto code format eclipse .settings
I can create a JIRA-task and look into if I can solve it. Perhaps I will do it within the next month then. But it would also be nice to get confirmation that it canät be done using the available configuration possibilities today. /Ludwig -Original Message- From: Dan Tran [mailto:dant...@gmail.com] Sent: den 18 mars 2010 08:57 To: Maven Users List Subject: Re: auto code format eclipse .settings feel free to submit patches. I have seen this request to configure code-style per project before, but it kind a die out -D On Thu, Mar 18, 2010 at 12:29 AM, Ludwig Magnusson lud...@itcatapult.com wrote: I don't really agree here. I think it's pretty much on a project level. I have different projects in my workspace that has different formatting requirements. And in my project, we have the exported xml-file version controlled. I defenetly think it would be great if the maven-eclipse-plugin could automatically set (if it can't already). Like it can with checkstyle. To me, that's what the maven-eclipse-plugin is about, configuring eclipse in every way needed for the project. Is that an incorrect assumption? /Ludwig -Original Message- From: Barrie Treloar [mailto:baerr...@gmail.com] Sent: den 18 mars 2010 00:36 To: Maven Users List Subject: Re: auto code format eclipse .settings Code formatting tends to be a workspace level thing rather than a per project setting. So you are probably better off doing this manually, since its a once off task. As others have pointed out, if it is a per-project file (e.g. like a checkstyle configuration file) then you can use the configuration additionalConfig file section to specify the files contents. - 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: auto code format eclipse .settings
Thank you, Patrick, I try this. Thank you for all, who has taken a part in this discussion. Best Regards, Sipungora Patrick Turcotte-4 wrote: Maybe this could help. If you make the modification through Eclipse interface, and check how the files were modified in .settings, you could probably set the plugin so it uses additionalConfig as below: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-eclipse-plugin/artifactId version2.7/version configuration additionalConfig file name.settings/org.eclipse.core.resources.prefs/name content ![CDATA[eclipse.preferences.version=1 encoding/project=ISO-8859-1]] /content /file /additionalConfig /configuration /plugin Patrick On 10-03-17 04:13 PM, Ludwig Magnusson wrote: Perhaps the code formatter? It's possible to export/import a projects code formatting in eclipse to/from an xml file. But I don't know if maven can use it to configure the code formatting of a project. /Ludwig -Original Message- From: Sipungora [mailto:kostya...@yahoo.de] Sent: den 17 mars 2010 21:03 To: users@maven.apache.org Subject: Re: auto code format eclipse .settings Hi Wayne, probably I don't correct understand your questions.:-( I read the documentation on the http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html site and there is the clause eclipse:eclipse Generates the following eclipse configuration files: ... .setting/org.eclipse.jdt.core.prefs with project specific compiler settings... there. But I didn't find how I can configure my pom to write e.g. formatting settings in this file in .setting directory. Wayne Fay wrote: how can I change .settings files with Maven2? maven-eclipse-plugin allows to set the workspace, but I want to set auto code format settings. Is it possible with maven? :confused::confused::confused: What in the maven-eclipse-plugin documentation makes you believe this is functionality that m-e-p will provide/support? Or is it merely an assumption on your part? What is confusing you? Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Patrick Turcotte Développeur/Architecte Java patrick.turco...@revolutionlinux.com (819) 780-8955, poste 1129 Sans frais 1-800-996-8955, poste 1129 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://old.nabble.com/auto-code-format-eclipse-.settings-tp27933567p27942678.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: how to use maven-scm-plugin to checkout a CVS tag
never mind,
The secret is in scmVersionType adn scmVervsion configuration
On Thu, Mar 18, 2010 at 1:02 AM, Dan Tran dant...@gmail.com wrote:
Hi every one,
I have a need to checkout a CVS tag at build time, and have no idea
how to configure the tag. Any advice is greatly appreciated
here is my configuration
configuration
connectionUrl${cvsroot}:mymodule/connectionUrl
/configuration
Thanks
-Dan
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: [ANNOUNCEMENT] - Maven License Verifier Plugin 0.2-SNAPSHOT
Hi Laurent, after investigating the problem i found the cause for this...sorry..;-( I hope to get a new update on the weekend... Thanks for testing MLV... Kind regards Karl Heinz Marbaise -- View this message in context: http://old.nabble.com/-ANNOUNCEMENTMaven-License-Verifier-Plugin-0.2-SNAPSHOT-tp27658754p27942753.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: [ANN] Riding Ruby on Rails3 with Maven3
Hi Kistrian, cool.. one question: Is Maven 3 required or would it work with Maven 2.2.1 as well ? Or didn't you test it ? Kind regards Karl Heinz Marbaise -- View this message in context: http://old.nabble.com/-ANN--Riding-Ruby-on-Rails3-with-Maven3-tp27941758p27942775.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
How to Invoke different goals of 1 plugin
Hi, We would like to invoke different goals on 1 plugin. From reading the documentation, it seems that the best way to achieve this is to setup a profile and specify the same plugin but with a different goal. Here is the 1st time that the plugin is defined in the pom.xml. Take note of the goal in this scenario 'check' (This should execute by default) build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-pmd-plugin/artifactId version2.4/version executions execution phasegenerate-sources/phase goals goalcheck/goal /goals /execution /executions /plugin /plugins /build And now for the profile, the goal in this case is 'pmd' : profiles profile idsonar/id build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-pmd-plugin/artifactId version2.4/version executions execution phasegenerate-sources/phase goals goalpmd/goal /goals /execution /executions /plugin /plugins /build /profile /profiles (Side note : We have to execute it during the generate-sources phase as we have other plugins that alters the source and any other phase is too late for this plugin in our environment) However, this approach seems to ONLY be valid for the top level. Once it decends into the child projects, then it seems to merge the goals, 'check' first 'pmd' thereafter (which doesn't seem to work correctly - see http://jira.codehaus.org/browse/MNG-4022). The documentation does mention that stuff will be merged but it fails to mention a.) is it possible to get around it? and b.) if it is possible, how would one go about it. We had a look into execution id's as well, but it seems that they are only bound to a lifecycle and cannot be used in our scenario. Any help would be much appreciated, -- izak -- View this message in context: http://n2.nabble.com/How-to-Invoke-different-goals-of-1-plugin-tp4755892p4755892.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: How to Invoke different goals of 1 plugin
give each execution a different id and if you don;t want something inherited by child projects, set inheritedfalse On 18 March 2010 11:38, izak.wessels izak.wess...@gmail.com wrote: Hi, We would like to invoke different goals on 1 plugin. From reading the documentation, it seems that the best way to achieve this is to setup a profile and specify the same plugin but with a different goal. Here is the 1st time that the plugin is defined in the pom.xml. Take note of the goal in this scenario 'check' (This should execute by default) build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-pmd-plugin/artifactId version2.4/version executions execution phasegenerate-sources/phase goals goalcheck/goal /goals /execution /executions /plugin /plugins /build And now for the profile, the goal in this case is 'pmd' : profiles profile idsonar/id build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-pmd-plugin/artifactId version2.4/version executions execution phasegenerate-sources/phase goals goalpmd/goal /goals /execution /executions /plugin /plugins /build /profile /profiles (Side note : We have to execute it during the generate-sources phase as we have other plugins that alters the source and any other phase is too late for this plugin in our environment) However, this approach seems to ONLY be valid for the top level. Once it decends into the child projects, then it seems to merge the goals, 'check' first 'pmd' thereafter (which doesn't seem to work correctly - see http://jira.codehaus.org/browse/MNG-4022). The documentation does mention that stuff will be merged but it fails to mention a.) is it possible to get around it? and b.) if it is possible, how would one go about it. We had a look into execution id's as well, but it seems that they are only bound to a lifecycle and cannot be used in our scenario. Any help would be much appreciated, -- izak -- View this message in context: http://n2.nabble.com/How-to-Invoke-different-goals-of-1-plugin-tp4755892p4755892.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: How to Invoke different goals of 1 plugin
stephenconnolly wrote: give each execution a different id and if you don;t want something inherited by child projects, set inheritedfalse Yup, we tried that. Example : build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-pmd-plugin/artifactId version2.4/version executions execution idpmd-default/id phasegenerate-sources/phase goals goalcheck/goal /goals /execution execution idpmd-sonar/id phasegenerate-sources/phase goals goalpmd/goal /goals /execution /executions /plugin /plugins /build 2 issues with that approach: 1. How do we tell maven which execution we want to run? 2. From what we understand you cannot just say inheritedfalse/inherited in the child pom.xml, you would have to do something like, plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-pmd-plugin/artifactId inheritedfalse/inherited /plugin However, we still want our plugin to run in our child projects, just run against a different goal based on question 1 -- View this message in context: http://n2.nabble.com/How-to-Invoke-different-goals-of-1-plugin-tp4755892p4755993.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: How to Invoke different goals of 1 plugin
build
plugins
plugin
artifactIdmaven-antrun-plugin/artifactId
version1.1/version
executions
execution
idechodir/id
goals
goalrun/goal
/goals
phaseverify/phase
*inheritedfalse/inherited* !-- this is the
inherited you want --
configuration
tasks
echoBuild Dir: ${project.build.directory}/echo
/tasks
/configuration
/execution
/executions
/plugin
/plugins
/build
On 18 March 2010 11:59, izak.wessels izak.wess...@gmail.com wrote:
stephenconnolly wrote:
give each execution a different id
and if you don;t want something inherited by child projects, set
inheritedfalse
Yup, we tried that.
Example :
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-pmd-plugin/artifactId
version2.4/version
executions
execution
idpmd-default/id
phasegenerate-sources/phase
goals
goalcheck/goal
/goals
/execution
execution
idpmd-sonar/id
phasegenerate-sources/phase
goals
goalpmd/goal
/goals
/execution
/executions
/plugin
/plugins
/build
2 issues with that approach:
1. How do we tell maven which execution we want to run?
You don't
It will run all the executions that are bound to the lifecycle automatically
If you want something different, use ANT, or hack away using profiles and
activation rules and then spend ages explainging to people why even though
you have used a build tool which has a standard lifecycle, you are ignoring
that and ending up back in the what ant task do I run to do ___ mire
2. From what we understand you cannot just say inheritedfalse/inherited
in the child pom.xml, you would have to do something like,
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-pmd-plugin/artifactId
inheritedfalse/inherited
/plugin
However, we still want our plugin to run in our child projects, just run
against a different goal based on question 1
--
View this message in context:
http://n2.nabble.com/How-to-Invoke-different-goals-of-1-plugin-tp4755892p4755993.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: How to perform ordered tasks in Maven2 build
Have different executions in different phases to ensure the order. In the same phase you cannot gaurantee any order AFAIK. Subir -Original Message- From: Perez Ronen [mailto:ronen.pe...@comverse.com] Sent: Thursday, March 18, 2010 12:42 PM To: Maven Users List Subject: How to perform ordered tasks in Maven2 build Hi, I am trying to migrate a Java application built by Ant to Maven2. among other the build perform the following operations: 1) Running a javadoc doclet to find annotated Java files to be externalize later as web services 2) compile a small part of the code for step 3 3) run Axis java2wsdl on the compiled code from step 2 4) produce java code with wsdl2java on the wsdl files from step 3 5) compile the entire code when trying to mavenize the process I can accomplish each task at a time but fail to achieve them all in that order. to demonstrate my pom and not load you with details I'll show the following snippet: build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId version2.6.1/version executions execution idaggregate/id phasegenerate-sources/phase goals goalaggregate/goal /goals configuration.../configuration /execution /executions /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId version2.1/version executions execution idcompileWSfiles/id goals goalcompile/goal /goals phasegenerate-sources/phase configuration includes !-- include 3 source files -- /includes /configuration /execution /executions /plugin plugin groupIdorg.codehaus.mojo/groupId artifactIdaxistools-maven-plugin/artifactId version1.3/version dependencies dependency groupIdaxis/groupId artifactIdaxis/artifactId version1.3/version /dependency /dependencies executions execution idjava2wsdl/id phasegenerate-sources/phase goals goaljava2wsdl/goal /goals configuration.../configuration /execution execution idwsdl2java/id phasegenerate-sources/phase goals goalwsdl2java/goal /goals configuration.../configuration /execution /executions /plugin /plugins I pinned all of the build executions on the generate-sources phase and as far as I know they should run in the order they are defined in the pom. The main problem is that I have no control on the order of things and it is obviously important here as every step output is the next step input. any suggestions? Thanks, Ronen. This e-mail message may contain confidential, commercial or privileged information that constitutes proprietary information of Comverse Technology or its subsidiaries. If you are not the intended recipient of this message, you are hereby notified that any review, use or distribution of this information is absolutely prohibited and we request that you delete all copies and contact us by e-mailing to: secur...@comverse.com. Thank You. Please do not print this email unless it is absolutely necessary. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to Invoke different goals of 1 plugin
We still want the plugin to be inherited by the child projects.
But thanks for the clarification on the syntax.
-Original Message-
From: stephenconnolly [via maven users]
ml-node+4756077-278159017-469...@n2.nabble.com
Date: Thu, 18 Mar 2010 04:16:17
To: izak.wesselsizak.wess...@gmail.com
Subject: Re: How to Invoke different goals of 1 plugin
build
plugins
plugin
artifactIdmaven-antrun-plugin/artifactId
version1.1/version
executions
execution
idechodir/id
goals
goalrun/goal
/goals
phaseverify/phase
*inheritedfalse/inherited* !-- this is the
inherited you want --
configuration
tasks
echoBuild Dir: ${project.build.directory}/echo
/tasks
/configuration
/execution
/executions
/plugin
/plugins
/build
On 18 March 2010 11:59, izak.wessels izak.wess...@gmail.com wrote:
stephenconnolly wrote:
give each execution a different id
and if you don;t want something inherited by child projects, set
inheritedfalse
Yup, we tried that.
Example :
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-pmd-plugin/artifactId
version2.4/version
executions
execution
idpmd-default/id
phasegenerate-sources/phase
goals
goalcheck/goal
/goals
/execution
execution
idpmd-sonar/id
phasegenerate-sources/phase
goals
goalpmd/goal
/goals
/execution
/executions
/plugin
/plugins
/build
2 issues with that approach:
1. How do we tell maven which execution we want to run?
You don't
It will run all the executions that are bound to the lifecycle automatically
If you want something different, use ANT, or hack away using profiles and
activation rules and then spend ages explainging to people why even though
you have used a build tool which has a standard lifecycle, you are ignoring
that and ending up back in the what ant task do I run to do ___ mire
2. From what we understand you cannot just say inheritedfalse/inherited
in the child pom.xml, you would have to do something like,
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-pmd-plugin/artifactId
inheritedfalse/inherited
/plugin
However, we still want our plugin to run in our child projects, just run
against a different goal based on question 1
--
View this message in context:
http://n2.nabble.com/How-to-Invoke-different-goals-of-1-plugin-tp4755892p4755993.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
__
View message @
http://n2.nabble.com/How-to-Invoke-different-goals-of-1-plugin-tp4755892p4756077.html
To unsubscribe from Re: How to Invoke different goals of 1 plugin, click (link
removed) =
--
View this message in context:
http://n2.nabble.com/How-to-Invoke-different-goals-of-1-plugin-tp4755892p4756104.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
Must timestamped snapshot deps be called out by full snapshot?
The instructions at: http://code.google.com/p/java-twitter/ call for one to declare their repo, and then just cite the g/a/v with version 0.9-SNAPSHOT. When I call it out in a pom, I get [INFO] Unable to find resource 'net.unto.twitter:java-twitter:jar:0.9-SNAPSHOT' in repository java-twitter-repository (http://java-twitter.googlecode.com/svn/repository/) [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) net.unto.twitter:java-twitter:jar:0.9-SNAPSHOT I note that the version is in fact, timestamped. Are the instructions wrong, or is my configuration broken ? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: How to perform ordered tasks in Maven2 build
From Maven documentation: http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html It says: a build phase can also have zero or more goals bound to it. If a build phase has no goals bound to it, that build phase will not execute. But if it has one or more goals bound to it, it will execute all those goals (Note: In Maven 2.0.5 and above, multiple goals bound to a phase are executed in the same order as they are declared in the POM, however multiple instances of the same plugin are not supported. Multiple instances of the same plugin are grouped to execute together and ordered in Maven 2.0.11 and above). Ronen -Original Message- From: subir.sasiku...@wipro.com [mailto:subir.sasiku...@wipro.com] Sent: ה 18 מרץ 2010 14:18 To: users@maven.apache.org Subject: RE: How to perform ordered tasks in Maven2 build Have different executions in different phases to ensure the order. In the same phase you cannot gaurantee any order AFAIK. Subir -Original Message- From: Perez Ronen [mailto:ronen.pe...@comverse.com] Sent: Thursday, March 18, 2010 12:42 PM To: Maven Users List Subject: How to perform ordered tasks in Maven2 build Hi, I am trying to migrate a Java application built by Ant to Maven2. among other the build perform the following operations: 1) Running a javadoc doclet to find annotated Java files to be externalize later as web services 2) compile a small part of the code for step 3 3) run Axis java2wsdl on the compiled code from step 2 4) produce java code with wsdl2java on the wsdl files from step 3 5) compile the entire code when trying to mavenize the process I can accomplish each task at a time but fail to achieve them all in that order. to demonstrate my pom and not load you with details I'll show the following snippet: build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId version2.6.1/version executions execution idaggregate/id phasegenerate-sources/phase goals goalaggregate/goal /goals configuration.../configuration /execution /executions /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId version2.1/version executions execution idcompileWSfiles/id goals goalcompile/goal /goals phasegenerate-sources/phase configuration includes !-- include 3 source files -- /includes /configuration /execution /executions /plugin plugin groupIdorg.codehaus.mojo/groupId artifactIdaxistools-maven-plugin/artifactId version1.3/version dependencies dependency groupIdaxis/groupId artifactIdaxis/artifactId version1.3/version /dependency /dependencies executions execution idjava2wsdl/id phasegenerate-sources/phase goals goaljava2wsdl/goal /goals configuration.../configuration /execution execution idwsdl2java/id phasegenerate-sources/phase goals goalwsdl2java/goal /goals configuration.../configuration /execution /executions /plugin /plugins I pinned all of the build executions on the generate-sources phase and as far as I know they should run in the order they are defined in the pom. The main problem is that I have no control on the order of things and it is obviously important here as every step output is the next step input. any suggestions? Thanks, Ronen. This e-mail message may contain confidential, commercial or privileged information that constitutes proprietary information of Comverse Technology or its subsidiaries. If you are not the intended recipient of this message, you are hereby notified that any review, use or distribution of this information is absolutely prohibited and we request that you delete all copies and contact us by e-mailing to: secur...@comverse.com. Thank You. Please do not print this email unless it is absolutely necessary. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and
Insert currentDate with archetype templates
Hello maven-archetype-plugin users, I am looking to insert a current datetime stamp into file generated by my own archetype. I found an old ticket http://jira.codehaus.org/browse/ARCHETYPE-63 said it's been implemented since alpha-1, but $currentDate still doesn't work on my alpha-4 version. Any idea how I can do this? If there is a list of dynamic properties available, can these be documented somewhere? Thanks, /Zemian Deng - Zemian Deng -- View this message in context: http://old.nabble.com/Insert-currentDate-with-archetype-templates-tp27945081p27945081.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: auto code format eclipse .settings
I've solved it. This is my parent model: http://old.nabble.com/file/p27945404/pom.xml pom.xml Warning: It doesn't work so. It must be extended. It should only show the principle. Settings for .settings files were made with eclipse first and then they was saved in foo-core.xml and in foo-ui.xml Best Regards, Sipungora Sipungora wrote: Hi, how can I change .settings files with Maven2? maven-eclipse-plugin allows to set the workspace, but I want to set auto code format settings. Is it possible with maven? :confused::confused::confused: Thanks in advance. -- View this message in context: http://old.nabble.com/auto-code-format-eclipse-.settings-tp27933567p27945404.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: Dealing with artifacts that have been moved - What to do?
Another section for the Best Practices Guide Sonotype has an article that almost describes how to do this. It is pretty good but lacks a bit about how (and why) to create a pom for the jars you need to upload. Ron Wayne Fay wrote: pThe document has moveda href=http://download.java.net/maven/1/javax.jms/jars/jms-1.1.jar;here/a./p You should not be using the java.net repos for a number of reasons, including this problem related to HTML 301s being saved as jars etc. You should download and manually install these artifacts into Nexus so they can be properly distributed within your team. We are using Sonatype Nexus and I am wondering if this as simple as adding Nexus has its own user list for questions such as these. Wayne - 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: How to perform ordered tasks in Maven2 build
Another Best Practice example about how to structure a project into Maven projects with libraries and dependencies to avoid the Big Bang theory of deployment. Ron Perez Ronen wrote: Hi, I am trying to migrate a Java application built by Ant to Maven2. among other the build perform the following operations: 1) Running a javadoc doclet to find annotated Java files to be externalize later as web services 2) compile a small part of the code for step 3 3) run Axis java2wsdl on the compiled code from step 2 4) produce java code with wsdl2java on the wsdl files from step 3 5) compile the entire code when trying to mavenize the process I can accomplish each task at a time but fail to achieve them all in that order. to demonstrate my pom and not load you with details I'll show the following snippet: build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId version2.6.1/version executions execution idaggregate/id phasegenerate-sources/phase goals goalaggregate/goal /goals configuration.../configuration /execution /executions /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId version2.1/version executions execution idcompileWSfiles/id goals goalcompile/goal /goals phasegenerate-sources/phase configuration includes !-- include 3 source files -- /includes /configuration /execution /executions /plugin plugin groupIdorg.codehaus.mojo/groupId artifactIdaxistools-maven-plugin/artifactId version1.3/version dependencies dependency groupIdaxis/groupId artifactIdaxis/artifactId version1.3/version /dependency /dependencies executions execution idjava2wsdl/id phasegenerate-sources/phase goals goaljava2wsdl/goal /goals configuration.../configuration /execution execution idwsdl2java/id phasegenerate-sources/phase goals goalwsdl2java/goal /goals configuration.../configuration /execution /executions /plugin /plugins I pinned all of the build executions on the generate-sources phase and as far as I know they should run in the order they are defined in the pom. The main problem is that I have no control on the order of things and it is obviously important here as every step output is the next step input. any suggestions? Thanks, Ronen. This e-mail message may contain confidential, commercial or privileged information that constitutes proprietary information of Comverse Technology or its subsidiaries. If you are not the intended recipient of this message, you are hereby notified that any review, use or distribution of this information is absolutely prohibited and we request that you delete all copies and contact us by e-mailing to: secur...@comverse.com. Thank You. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Must timestamped snapshot deps be called out by full snapshot?
Perhaps a silly question but did you add their repository to your list of repositories. Perhaps I am mistaken but it looks like there is a extra 0.9-SNAPSHOT in the real path and their instructions are not correct. I did not test this but you might want to try it http://java-twitter.googlecode.com/svn/repository/net/unto/twitter/java-twitter/0.9-SNAPSHOT/ has the jars in it. Ron Benson Margulies wrote: The instructions at: http://code.google.com/p/java-twitter/ call for one to declare their repo, and then just cite the g/a/v with version 0.9-SNAPSHOT. When I call it out in a pom, I get [INFO] Unable to find resource 'net.unto.twitter:java-twitter:jar:0.9-SNAPSHOT' in repository java-twitter-repository (http://java-twitter.googlecode.com/svn/repository/) [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) net.unto.twitter:java-twitter:jar:0.9-SNAPSHOT I note that the version is in fact, timestamped. Are the instructions wrong, or is my configuration broken ? - 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: [ANN] Riding Ruby on Rails3 with Maven3
On Thu, Mar 18, 2010 at 1:56 PM, Karl Heinz Marbaise k...@soebes.de wrote: Hi Kistrian, cool.. one question: Is Maven 3 required or would it work with Maven 2.2.1 as well ? Or didn't you test it ? it really needs maven 3 due to the way all the rubygems get downloaded as gem artifacts which uses a custom repository layout which works only in maven3 via plugin extension. regards Kristian Kind regards Karl Heinz Marbaise -- View this message in context: http://old.nabble.com/-ANN--Riding-Ruby-on-Rails3-with-Maven3-tp27941758p27942775.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 -- Kristian Meier + Saumya Sharma + Sanuka Meier Vadakkethu House, Edayanmula West PO - 689532, Pathanamthitta District, Kerala, INDIA tel: +91 468 2319577 protect your privacy while searching the net: www.ixquick.com _=_ q(-_-)p '_) (_` /__/ \ _(_ / )_ (__\_\_|_/__) - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [ANN] Riding Ruby on Rails3 with Maven3
Hi Kristian, First thanks for the answer But i know of the nar plugins which are used for C++/C compilings etc. and dependency download (nar-files) etc. and they are working for MVN 2.2.1 as well... http://duns.github.com/maven-nar-plugin/ Kind regards Karl Heinz Marbaise -- View this message in context: http://old.nabble.com/-ANN--Riding-Ruby-on-Rails3-with-Maven3-tp27941758p27945765.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: How to perform ordered tasks in Maven2 build
Guys, I am trying to push Maven in my organization, so I am facing the reality of existing mega projects with mega chaos and the resistance of some zealous ant users. Do you have an operative suggestions? -Original Message- From: Ron Wheeler [mailto:rwhee...@artifact-software.com] Sent: ה 18 מרץ 2010 14:45 To: Maven Users List Subject: Re: How to perform ordered tasks in Maven2 build Another Best Practice example about how to structure a project into Maven projects with libraries and dependencies to avoid the Big Bang theory of deployment. Ron Perez Ronen wrote: Hi, I am trying to migrate a Java application built by Ant to Maven2. among other the build perform the following operations: 1) Running a javadoc doclet to find annotated Java files to be externalize later as web services 2) compile a small part of the code for step 3 3) run Axis java2wsdl on the compiled code from step 2 4) produce java code with wsdl2java on the wsdl files from step 3 5) compile the entire code when trying to mavenize the process I can accomplish each task at a time but fail to achieve them all in that order. to demonstrate my pom and not load you with details I'll show the following snippet: build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId version2.6.1/version executions execution idaggregate/id phasegenerate-sources/phase goals goalaggregate/goal /goals configuration.../configuration /execution /executions /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId version2.1/version executions execution idcompileWSfiles/id goals goalcompile/goal /goals phasegenerate-sources/phase configuration includes !-- include 3 source files -- /includes /configuration /execution /executions /plugin plugin groupIdorg.codehaus.mojo/groupId artifactIdaxistools-maven-plugin/artifactId version1.3/version dependencies dependency groupIdaxis/groupId artifactIdaxis/artifactId version1.3/version /dependency /dependencies executions execution idjava2wsdl/id phasegenerate-sources/phase goals goaljava2wsdl/goal /goals configuration.../configuration /execution execution idwsdl2java/id phasegenerate-sources/phase goals goalwsdl2java/goal /goals configuration.../configuration /execution /executions /plugin /plugins I pinned all of the build executions on the generate-sources phase and as far as I know they should run in the order they are defined in the pom. The main problem is that I have no control on the order of things and it is obviously important here as every step output is the next step input. any suggestions? Thanks, Ronen. This e-mail message may contain confidential, commercial or privileged information that constitutes proprietary information of Comverse Technology or its subsidiaries. If you are not the intended recipient of this message, you are hereby notified that any review, use or distribution of this information is absolutely prohibited and we request that you delete all copies and contact us by e-mailing to: secur...@comverse.com. Thank You. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org “This e-mail message may contain confidential, commercial or privileged information that constitutes proprietary information of Comverse Technology or its subsidiaries. If you are not the intended recipient of this message, you are hereby notified that any review, use or distribution of this information is absolutely prohibited and we request that you delete all copies and contact us by e-mailing to: secur...@comverse.com. Thank You.” - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: How to perform ordered tasks in Maven2 build
You can set up maven in paralell, non-disruptively. Once you have that, get site reports working and then ask the Ant guys to produce a bill-of-materials! === Curtis Yanko UHGIT Computer Services - ADIS Continuous Integration Service https://ulink.uhc.com/groups/cis w860.702.9059 m860.881.2050 -Original Message- From: Perez Ronen [mailto:ronen.pe...@comverse.com] Sent: Thursday, March 18, 2010 9:56 AM To: 'Maven Users List' Subject: RE: How to perform ordered tasks in Maven2 build Guys, I am trying to push Maven in my organization, so I am facing the reality of existing mega projects with mega chaos and the resistance of some zealous ant users. Do you have an operative suggestions? -Original Message- From: Ron Wheeler [mailto:rwhee...@artifact-software.com] Sent: ה 18 מרץ 2010 14:45 To: Maven Users List Subject: Re: How to perform ordered tasks in Maven2 build Another Best Practice example about how to structure a project into Maven projects with libraries and dependencies to avoid the Big Bang theory of deployment. Ron Perez Ronen wrote: Hi, I am trying to migrate a Java application built by Ant to Maven2. among other the build perform the following operations: 1) Running a javadoc doclet to find annotated Java files to be externalize later as web services 2) compile a small part of the code for step 3 3) run Axis java2wsdl on the compiled code from step 2 4) produce java code with wsdl2java on the wsdl files from step 3 5) compile the entire code when trying to mavenize the process I can accomplish each task at a time but fail to achieve them all in that order. to demonstrate my pom and not load you with details I'll show the following snippet: build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId version2.6.1/version executions execution idaggregate/id phasegenerate-sources/phase goals goalaggregate/goal /goals configuration.../configuration /execution /executions /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId version2.1/version executions execution idcompileWSfiles/id goals goalcompile/goal /goals phasegenerate-sources/phase configuration includes !-- include 3 source files -- /includes /configuration /execution /executions /plugin plugin groupIdorg.codehaus.mojo/groupId artifactIdaxistools-maven-plugin/artifactId version1.3/version dependencies dependency groupIdaxis/groupId artifactIdaxis/artifactId version1.3/version /dependency /dependencies executions execution idjava2wsdl/id phasegenerate-sources/phase goals goaljava2wsdl/goal /goals configuration.../configuration /execution execution idwsdl2java/id phasegenerate-sources/phase goals goalwsdl2java/goal /goals configuration.../configuration /execution /executions /plugin /plugins I pinned all of the build executions on the generate-sources phase and as far as I know they should run in the order they are defined in the pom. The main problem is that I have no control on the order of things and it is obviously important here as every step output is the next step input. any suggestions? Thanks, Ronen. This e-mail message may contain confidential, commercial or privileged information that constitutes proprietary information of Comverse Technology or its subsidiaries. If you are not the intended recipient of this message, you are hereby notified that any review, use or distribution of this information is absolutely prohibited and we request that you delete all copies and contact us by e-mailing to: secur...@comverse.com. Thank You. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org “This e-mail message may contain confidential, commercial or privileged information that constitutes proprietary information of Comverse Technology or its subsidiaries. If you are not the intended recipient of this message, you
Re: Must timestamped snapshot deps be called out by full snapshot?
I did add the repo. On Thu, Mar 18, 2010 at 9:27 AM, Ron Wheeler rwhee...@artifact-software.com wrote: Perhaps a silly question but did you add their repository to your list of repositories. Perhaps I am mistaken but it looks like there is a extra 0.9-SNAPSHOT in the real path and their instructions are not correct. I did not test this but you might want to try it http://java-twitter.googlecode.com/svn/repository/net/unto/twitter/java-twitter/0.9-SNAPSHOT/ has the jars in it. Ron Benson Margulies wrote: The instructions at: http://code.google.com/p/java-twitter/ call for one to declare their repo, and then just cite the g/a/v with version 0.9-SNAPSHOT. When I call it out in a pom, I get [INFO] Unable to find resource 'net.unto.twitter:java-twitter:jar:0.9-SNAPSHOT' in repository java-twitter-repository (http://java-twitter.googlecode.com/svn/repository/) [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) net.unto.twitter:java-twitter:jar:0.9-SNAPSHOT I note that the version is in fact, timestamped. Are the instructions wrong, or is my configuration broken ? - 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: Getting the path to an individual dependency for use with the antrun plugin
Did you make any progress? I'm trying to do this same. ~ David Allan Ditzel wrote: Hi, We have the need to run some ant tasks within our maven project, but we need to get a fully qualified path to the artifact to pass in to some ant tasks. The only thing I've found so far is the following property name=mvn.dependency.jar refid=maven.dependency.my.group.id:my.artifact.id:classifier:jar.path/ But the above doesn't work. Would anyone know how to do this? Thanks, Allan -- View this message in context: http://old.nabble.com/Getting-the-path-to-an-individual-dependency-for-use-with-the-antrun--plugin-tp22265813p27947478.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
Does site set a property that it is running?
Is there a property set by the site plugin when the site goal runs (as the release plugin sets the performRelease property)? If there is, where/how could I have found the answer? I looked in site plugin doc, lifecycle pages, googled, http://docs.codehaus.org/display/MAVENUSER/MavenPropertiesGuide, etc. but no luck. (the ultimate goal is to have a profile active when site gen runs) - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to perform ordered tasks in Maven2 build
Perez Ronen wrote: Guys, I am trying to push Maven in my organization, so I am facing the reality of existing mega projects with mega chaos and the resistance of some zealous ant users. Do you have an operative suggestions? Unfortunately there is not a best practices guide. I can give you a few pointers based on my experience running a small development group and listening to the traffic here. 1) Post some more details about the type of project you are building and a bit about the size and make up of your team. Any information that you can give about your workflow and QC policies will help. 2) Try not to fight Maven or bend it to your will. Maven embodies some unspoken set of best practices that are well supported and will make your life better if you conform to its will. OTOH, there seem to be a million plug-ins that encourages peole to do some odd things by making it possible and even easy. 3) Do you have a repository set up? I am a bit fan of Nexus but there are others that are frequently used. I wish that I had done that 2+ years ago. It adds a level of transapency and convenience to Maven that really helps. I just have the free one but if you have a bigger team with more complexity in your structure and workflow, you may get a lot of benefit out of their professional version. 4) You should take a look at the build structure to see how the project's dependencies are woven together. See how well the libraries are organized so that libraries can be constructed and tested without testing the whole mess. Ant is a great tool but Maven makes your life easier once you get your shit together. There are some really smart people in the forum and you can probably get some good advice and use cases to help move the ant-lovers to become maven fanatics. If you follow my #1 piece of advice I am sure you will get some help. Ron Ron -Original Message- From: Ron Wheeler [mailto:rwhee...@artifact-software.com] Sent: ה 18 מרץ 2010 14:45 To: Maven Users List Subject: Re: How to perform ordered tasks in Maven2 build Another Best Practice example about how to structure a project into Maven projects with libraries and dependencies to avoid the Big Bang theory of deployment. Ron Perez Ronen wrote: Hi, I am trying to migrate a Java application built by Ant to Maven2. among other the build perform the following operations: 1) Running a javadoc doclet to find annotated Java files to be externalize later as web services 2) compile a small part of the code for step 3 3) run Axis java2wsdl on the compiled code from step 2 4) produce java code with wsdl2java on the wsdl files from step 3 5) compile the entire code when trying to mavenize the process I can accomplish each task at a time but fail to achieve them all in that order. to demonstrate my pom and not load you with details I'll show the following snippet: build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId version2.6.1/version executions execution idaggregate/id phasegenerate-sources/phase goals goalaggregate/goal /goals configuration.../configuration /execution /executions /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId version2.1/version executions execution idcompileWSfiles/id goals goalcompile/goal /goals phasegenerate-sources/phase configuration includes !-- include 3 source files -- /includes /configuration /execution /executions /plugin plugin groupIdorg.codehaus.mojo/groupId artifactIdaxistools-maven-plugin/artifactId version1.3/version dependencies dependency groupIdaxis/groupId artifactIdaxis/artifactId version1.3/version /dependency /dependencies executions execution idjava2wsdl/id phasegenerate-sources/phase goals goaljava2wsdl/goal /goals configuration.../configuration /execution execution idwsdl2java/id phasegenerate-sources/phase goals goalwsdl2java/goal /goals configuration.../configuration /execution /executions /plugin /plugins I pinned all of the build executions on the generate-sources phase and as far as I know they should run in the order they are defined in the pom. The main problem is
Re: Dealing with artifacts that have been moved - What to do?
Another section for the Best Practices Guide There are multiple books written about Maven (many as free PDFs) in addition to the Maven website, various plugin documentation, Maven User Wiki, and many other resources. At least one third of the questions on this list are straight out of the existing documentation. Some other good percentage is answered in the Maven books that a relatively small portion of the total Maven user population ever reads due to the length. I'm not saying this Best Practices Guide is not a good idea. I just don't think it would necessarily be as useful (especially in reducing traffic on this list) as you might think. PS- Who is producing and assuming ongoing responsibility for this BPG? Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to perform ordered tasks in Maven2 build
Guys, I am trying to push Maven in my organization, so I am facing the reality of existing mega projects with mega chaos and the resistance of some zealous ant users. Do you have an operative suggestions? It sounds like you would benefit from a mandate from someone higher up that will gently require people to adopt Maven over some period of time. In an org full of zealous ant users, you're fighting an uphill battle without some support. At the least, you need to be able to re-organize the projects to get them to conform to Maven's standards for where source files should be and to split things up into modules where it makes sense etc. Without a mandate or some power in general over the projects, this will probably be yet another failed migration effort. I am less of a fan of the parallel non-disruptive approach suggested by Curtis because it is much harder to accomplish due to the excessive configuration that is required, unless you can do all your work in one big branch in SVN and then check it all in at once after it is working. But that is going to be very disruptive, too. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Must timestamped snapshot deps be called out by full snapshot?
The instructions at: http://code.google.com/p/java-twitter/ call for one to declare their repo, and then just cite the g/a/v with version 0.9-SNAPSHOT. Perhaps a silly question but did you ask on their user list first? This may be a known error in their documentation that they can help you resolve. If not, they should know about the problem so they can work to resolve it. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Dealing with artifacts that have been moved - What to do?
Wayne Fay wrote: Another section for the Best Practices Guide There are multiple books written about Maven (many as free PDFs) in addition to the Maven website, various plugin documentation, Maven User Wiki, and many other resources. There is no shortage of documentation but it is not focused on integrating maven into common development environments. At least one third of the questions on this list are straight out of the existing documentation. Some other good percentage is answered in the Maven books that a relatively small portion of the total Maven user population ever reads due to the length. That is where a Best Practice would be good. - short, - targeted to each situation - tells you where to get the technical details - unambiguous - no you might do this or mayby that just if your situation is this and you want the best development environment do exactly this. I'm not saying this Best Practices Guide is not a good idea. I just don't think it would necessarily be as useful (especially in reducing traffic on this list) as you might think. PS- Who is producing and assuming ongoing responsibility for this BPG? The community. Wayne - 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: How to perform ordered tasks in Maven2 build
Wayne Fay wrote: Guys, I am trying to push Maven in my organization, so I am facing the reality of existing mega projects with mega chaos and the resistance of some zealous ant users. Do you have an operative suggestions? It sounds like you would benefit from a mandate from someone higher up that will gently require people to adopt Maven over some period of time. In an org full of zealous ant users, you're fighting an uphill battle without some support. At the least, you need to be able to re-organize the projects to get them to conform to Maven's standards for where source files should be and to split things up into modules where it makes sense etc. Without a mandate or some power in general over the projects, this will probably be yet another failed migration effort. I am less of a fan of the parallel non-disruptive approach suggested by Curtis because it is much harder to accomplish due to the excessive configuration that is required, unless you can do all your work in one big branch in SVN and then check it all in at once after it is working. But that is going to be very disruptive, too. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org Can you provide examples of large organizations that made the move from Ant to Maven and were happy with the process and felt that the benefits outweighed the initial costs. Ron Ron - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Must timestamped snapshot deps be called out by full snapshot?
Guilty as charged. I have this sense that I've gotten into trouble with snapshot timestamps before, so I lept here. On Thu, Mar 18, 2010 at 1:22 PM, Wayne Fay wayne...@gmail.com wrote: The instructions at: http://code.google.com/p/java-twitter/ call for one to declare their repo, and then just cite the g/a/v with version 0.9-SNAPSHOT. Perhaps a silly question but did you ask on their user list first? This may be a known error in their documentation that they can help you resolve. If not, they should know about the problem so they can work to resolve it. Wayne - 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: Dealing with artifacts that have been moved - What to do?
PS- Who is producing and assuming ongoing responsibility for this BPG? The community. It won't get done. Someone needs to come forward and lead the charge. All these suggestions going to the mailing list I am sure a lot of readers are enjoyoing but I doubt anyone is actually capturing the suggestions and putting them in a formal document available on the web. Its a good idea. It will just need some commitment. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to perform ordered tasks in Maven2 build
Can you provide examples of large organizations that made the move from Ant to Maven and were happy with the process and felt that the benefits outweighed the initial costs. I can only speak for the companies that I work for, and Maven has only been adopted in pockets, not broadly due to the way my company is organized -- development is not under one division/person. And we are not primarily a development shop. I would expect that Sonatype could talk more broadly about Maven's adoption at E*Trade, eBay, Overstock, Intuit, Qualcomm, etc. My personal opinion (and it is shared by many of the active people on this list) is that jumping in with your first Maven project as a big Ant migration is the worst possible way to get started with Maven and is nearly guaranteed to fail. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Dealing with artifacts that have been moved - What to do?
- unambiguous - no you might do this or mayby that just if your situation is this and you want the best development environment do exactly this. But notice some recent questions on the list... - how to compile from multiple source directories - migrating a large ant build to maven without any power to reorg the files/projects - etc It seems pretty rare that someone is looking for what you are proposing to create... PS- Who is producing and assuming ongoing responsibility for this BPG? The community. Sounds like the Maven User Wiki is a fine place to start. I started the document [1] for the community to add/edit as it deems useful. [1] http://docs.codehaus.org/display/MAVENUSER/Maven+Best+Practice+Guide Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: How to perform ordered tasks in Maven2 build
For the most part, I agree with Wayne's sentiment. We did it in stages, and even now it isn't fully adopted. Like just about everyone else, before Maven we were using ant. A number of more agile projects which had more empowerment heard about Maven and just tried it on their projects. Some of these projects were fairly small and others were pretty large. The important part is that the developers decided to do it themselves and were thus committed to it. It worked well, and word began to spread amongst the grass roots of the development community. It was key for us that it happened in a grass roots fashion. Wayne mentioned earlier that you should try and get higher level org buy in. But I don't think that really ever happens. The grass roots, or the pigs (for those that are familiar with scrum terminology) are the ones who start the change. Once you hit a certain critical mass, larger parts of the org start to follow suit. A meritocrocy approach, while slow, is generally the best way to get buy in. If you force it, everyone will hate it and not be very productive. -Original Message- From: Wayne Fay [mailto:wayne...@gmail.com] Sent: Thursday, March 18, 2010 2:07 PM To: Maven Users List Subject: Re: How to perform ordered tasks in Maven2 build Can you provide examples of large organizations that made the move from Ant to Maven and were happy with the process and felt that the benefits outweighed the initial costs. I can only speak for the companies that I work for, and Maven has only been adopted in pockets, not broadly due to the way my company is organized -- development is not under one division/person. And we are not primarily a development shop. I would expect that Sonatype could talk more broadly about Maven's adoption at E*Trade, eBay, Overstock, Intuit, Qualcomm, etc. My personal opinion (and it is shared by many of the active people on this list) is that jumping in with your first Maven project as a big Ant migration is the worst possible way to get started with Maven and is nearly guaranteed to fail. Wayne - 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: How to perform ordered tasks in Maven2 build
On 3/18/10 2:06 PM, Wayne Fay wrote: My personal opinion (and it is shared by many of the active people on this list) is that jumping in with your first Maven project as a big Ant migration is the worst possible way to get started with Maven and is nearly guaranteed to fail. Just to echo this... it's actually two-fold: 1) As an organization, you should first use Maven on a greenfield project. 2) As a build architect (or whatever you want to call it), you should first use Maven on a greenfield project. Failing to do BOTH of these will result in failure. An experienced build architect who has used Maven on a variety of projects MAY be able to do #1, but it is very risky. As an aside, a Best Practices Guide is a fine idea, but I don't see it working as a community project. Justin Wayne - 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: How to perform ordered tasks in Maven2 build
It was key for us that it happened in a grass roots fashion. A meritocrocy approach, while slow, is generally the best way to get buy in. If you force it, everyone will hate it and not be very productive. I agree 100% with the grassroots, meritocracy approach. But it sounded like the OP in this thread has no real power to re-architect his projects/builds and he is working with zealous ant users. We know that is the path to failure. So someone, somewhere needs to give him this power -- ideally its the dev team(s) he is working with, but it could also be the person they report to, depending on the culture of the org and the norms in their locale (Asia vs Europe vs US etc). Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Dealing with artifacts that have been moved - What to do?
Wayne Fay wrote: - unambiguous - no you might do this or mayby that just if your situation is this and you want the best development environment do exactly this. But notice some recent questions on the list... - how to compile from multiple source directories - migrating a large ant build to maven without any power to reorg the files/projects - etc It seems pretty rare that someone is looking for what you are proposing to create... My suspicion is that these are caused by not following the Best Practice for Maven. Under what circumstance would you recommend to a user that they set up a project that required 2 source directories? In the end, I suspect that they really have 2 (or more) projects with 1 source directory each with dependencies between them. Once they Mavenize their project structure, they will find that they do not need these gymnastics. Migration is always tough and may be one of the last Best Practices to emerge. Your suggestion, if I recall correctly was to not try to Mavenize in the face of an entrenched Ant lobby until you had established a high level buy-in. That in itself could be the root of a Best Practice that is less about Maven technical issues and more about how to plan and organize a large scale methodology upgrade and how to justify the investment to management and the rest of the team. The fact that a number of people are not looking for the right things is due to a certain extent to the power and flexibility of Maven and the lack of a set of Best Practices. Maven is one of those tools that really needs a warning note Just because Maven can do it, does not mean that you should do it. How many Maven project structures and development methodologies are radically different but equally recommended can you come up with for a small team of less than 5 developers that are developing a webapp in Java with Spring on Eclipse or Netbeans for deployment on Tomcat, Glassfish or Websphere? How difficult would it be to get a consensus on which one of your suggestions is the best. How hard would it be to get agreement on what is the criteria for best. Just for a starting point, in my opinion, the best practice for the above situation would suggest that the project needs a subversion repository, a Nexus community version repository, the Spring STS version of Eclipse, a master POM for the project, a set of library POMs for the shared code and utilities, and a single project POM to build the WAR file. Lots of details to flesh out but they would fit on 1 page with a few pages of POMs, settings and misc. xml samples attached. How many variants would that Best Practice need to satisfy 90% of the target use cases. Ron PS- Who is producing and assuming ongoing responsibility for this BPG? The community. Sounds like the Maven User Wiki is a fine place to start. I started the document [1] for the community to add/edit as it deems useful. [1] http://docs.codehaus.org/display/MAVENUSER/Maven+Best+Practice+Guide Wayne - 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: How to perform ordered tasks in Maven2 build
I believe there are some blog posts over at Soantype's blog about success stories migrating to Maven. Have a look there! http://blogs.sonatype.com /Anders On Thu, Mar 18, 2010 at 18:35, Ron Wheeler rwhee...@artifact-software.comwrote: Wayne Fay wrote: Guys, I am trying to push Maven in my organization, so I am facing the reality of existing mega projects with mega chaos and the resistance of some zealous ant users. Do you have an operative suggestions? It sounds like you would benefit from a mandate from someone higher up that will gently require people to adopt Maven over some period of time. In an org full of zealous ant users, you're fighting an uphill battle without some support. At the least, you need to be able to re-organize the projects to get them to conform to Maven's standards for where source files should be and to split things up into modules where it makes sense etc. Without a mandate or some power in general over the projects, this will probably be yet another failed migration effort. I am less of a fan of the parallel non-disruptive approach suggested by Curtis because it is much harder to accomplish due to the excessive configuration that is required, unless you can do all your work in one big branch in SVN and then check it all in at once after it is working. But that is going to be very disruptive, too. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org Can you provide examples of large organizations that made the move from Ant to Maven and were happy with the process and felt that the benefits outweighed the initial costs. Ron Ron - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Javadoc plugin configuration: can I specify it once for build and reporting?
I don't see an easy way to specify the same configuration values for the maven-javadoc-plugin so that they'll apply when it is used from buildplugins as well as from reporting. What's the best way to do this? Thanks, Laird
Re: Dealing with artifacts that have been moved - What to do?
On 3/18/10 3:55 PM, Ron Wheeler wrote: Wayne Fay wrote: - unambiguous - no you might do this or mayby that just if your situation is this and you want the best development environment do exactly this. But notice some recent questions on the list... - how to compile from multiple source directories - migrating a large ant build to maven without any power to reorg the files/projects - etc It seems pretty rare that someone is looking for what you are proposing to create... My suspicion is that these are caused by not following the Best Practice for Maven. Under what circumstance would you recommend to a user that they set up a project that required 2 source directories? In the end, I suspect that they really have 2 (or more) projects with 1 source directory each with dependencies between them. Once they Mavenize their project structure, they will find that they do not need these gymnastics. But in neither of these cases was the question should I be doing this? It was I need to do this. Tell me how do I do it. Migration is always tough and may be one of the last Best Practices to emerge. Your suggestion, if I recall correctly was to not try to Mavenize in the face of an entrenched Ant lobby until you had established a high level buy-in. That in itself could be the root of a Best Practice that is less about Maven technical issues and more about how to plan and organize a large scale methodology upgrade and how to justify the investment to management and the rest of the team. Except that Wayne's wrong about this :) Management buy-in doesn't mean shit. The fact that a number of people are not looking for the right things is due to a certain extent to the power and flexibility of Maven and the lack of a set of Best Practices. I don't agree that this is what's going on here. Maven is one of those tools that really needs a warning note Just because Maven can do it, does not mean that you should do it. Seriously? How many Maven project structures and development methodologies are radically different but equally recommended can you come up with for a small team of less than 5 developers that are developing a webapp in Java with Spring on Eclipse or Netbeans for deployment on Tomcat, Glassfish or Websphere? How difficult would it be to get a consensus on which one of your suggestions is the best. How hard would it be to get agreement on what is the criteria for best. Just for a starting point, in my opinion, the best practice for the above situation would suggest that the project needs a subversion repository, a Nexus community version repository, the Spring STS version of Eclipse, a master POM for the project, a set of library POMs for the shared code and utilities, and a single project POM to build the WAR file. Lots of details to flesh out but they would fit on 1 page with a few pages of POMs, settings and misc. xml samples attached. But IMHO you should be using Git instead of Subversion and STS doesn't have enough management tools to support a large-scale rollout. Are we actually going to be able to reach consensus on those things? In all seriousness, you should publish this as Ron's Best Practices. If you put something up on Lulu or whatever, I would read it and I would probably recommend it to others. There isn't enough documentation about Maven; I just don't think the community can produce the type of documentation you're describing. Justin How many variants would that Best Practice need to satisfy 90% of the target use cases. Ron PS- Who is producing and assuming ongoing responsibility for this BPG? The community. Sounds like the Maven User Wiki is a fine place to start. I started the document [1] for the community to add/edit as it deems useful. [1] http://docs.codehaus.org/display/MAVENUSER/Maven+Best+Practice+Guide Wayne - 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: Dealing with artifacts that have been moved - What to do?
Interesting. Much of what you say I think is already documented. For example the definitive guide explains quite well that by convention Maven supports one artifact per project. It also contains many if not most of the best practices that users often ask on this list how to circumvent. But I know what you are getting at. This best practices guide would be a short summary of statements you find in books like the Definitive Guide, Better Builds with Maven and many of the blogs on the Sonatype web site. But the guide would need to at least reference why these practices are in fact best practices. What are the consequences of not following a best practice? In many cases, these explanations would be short but in others it wouldn't. This could make the best practices document turn into a fairly large beast that just re-iterated what is already in other documents. This duplication can be a pain to manage. As the true documents change over time, the best practices document would have to change also. Just one more document to update and keep in sync. Who will want to do that? I don't want to rain on your idea too much, since I think it does have a lot of merit. However, I also am not fully bought into it. As a final note, the best practices guide should NOT say what repository manager or SCM one should use. That isn't a space I think Maven should get into. I think it is valid to say that its a best practice that a repo manager is used, but to get into which one is best. Same with SCM. It also shouldn't say which which libraries to use. Those can be completely different depending on the project. It could perhaps list certain libraries and discuss the pros/cons of each, but again, this can change over time and isn't really a best practice. It also could perhaps state which SCMs Maven currently works with, which would help someone looking into Maven to decide if they wanted to use it. But again, this kind of information is hard to keep up to date and isn't really a Best Practices thing. -Original Message- From: Ron Wheeler [mailto:rwhee...@artifact-software.com] Sent: Thursday, March 18, 2010 3:55 PM To: Maven Users List Subject: Re: Dealing with artifacts that have been moved - What to do? Wayne Fay wrote: - unambiguous - no you might do this or mayby that just if your situation is this and you want the best development environment do exactly this. But notice some recent questions on the list... - how to compile from multiple source directories - migrating a large ant build to maven without any power to reorg the files/projects - etc It seems pretty rare that someone is looking for what you are proposing to create... My suspicion is that these are caused by not following the Best Practice for Maven. Under what circumstance would you recommend to a user that they set up a project that required 2 source directories? In the end, I suspect that they really have 2 (or more) projects with 1 source directory each with dependencies between them. Once they Mavenize their project structure, they will find that they do not need these gymnastics. Migration is always tough and may be one of the last Best Practices to emerge. Your suggestion, if I recall correctly was to not try to Mavenize in the face of an entrenched Ant lobby until you had established a high level buy-in. That in itself could be the root of a Best Practice that is less about Maven technical issues and more about how to plan and organize a large scale methodology upgrade and how to justify the investment to management and the rest of the team. The fact that a number of people are not looking for the right things is due to a certain extent to the power and flexibility of Maven and the lack of a set of Best Practices. Maven is one of those tools that really needs a warning note Just because Maven can do it, does not mean that you should do it. How many Maven project structures and development methodologies are radically different but equally recommended can you come up with for a small team of less than 5 developers that are developing a webapp in Java with Spring on Eclipse or Netbeans for deployment on Tomcat, Glassfish or Websphere? How difficult would it be to get a consensus on which one of your suggestions is the best. How hard would it be to get agreement on what is the criteria for best. Just for a starting point, in my opinion, the best practice for the above situation would suggest that the project needs a subversion repository, a Nexus community version repository, the Spring STS version of Eclipse, a master POM for the project, a set of library POMs for the shared code and utilities, and a single project POM to build the WAR file. Lots of details to flesh out but they would fit on 1 page with a few pages of POMs, settings and misc. xml samples attached. How many variants would
Re: Dealing with artifacts that have been moved - What to do?
Justin Edelson wrote: On 3/18/10 3:55 PM, Ron Wheeler wrote: Wayne Fay wrote: - unambiguous - no you might do this or mayby that just if your situation is this and you want the best development environment do exactly this. But notice some recent questions on the list... - how to compile from multiple source directories - migrating a large ant build to maven without any power to reorg the files/projects - etc It seems pretty rare that someone is looking for what you are proposing to create... My suspicion is that these are caused by not following the Best Practice for Maven. Under what circumstance would you recommend to a user that they set up a project that required 2 source directories? In the end, I suspect that they really have 2 (or more) projects with 1 source directory each with dependencies between them. Once they Mavenize their project structure, they will find that they do not need these gymnastics. But in neither of these cases was the question should I be doing this? It was I need to do this. Tell me how do I do it. Migration is always tough and may be one of the last Best Practices to emerge. Your suggestion, if I recall correctly was to not try to Mavenize in the face of an entrenched Ant lobby until you had established a high level buy-in. That in itself could be the root of a Best Practice that is less about Maven technical issues and more about how to plan and organize a large scale methodology upgrade and how to justify the investment to management and the rest of the team. Except that Wayne's wrong about this :) Management buy-in doesn't mean shit. Thats why it might take a long time to come to a consensus. That should not stop work on other use cases. The fact that a number of people are not looking for the right things is due to a certain extent to the power and flexibility of Maven and the lack of a set of Best Practices. I don't agree that this is what's going on here. You could be right. I am reading in a bit into the reason that someone would need 2 source directories in a POM. There was not much detail given as to why but I have never seen any of the more experience folks here recommend that as a solution to any development strategy issue. I am jumping to the conclusion that they really have 2 projects and so on. Maven is one of those tools that really needs a warning note Just because Maven can do it, does not mean that you should do it. Seriously? Yes. Very. How many Maven project structures and development methodologies are radically different but equally recommended can you come up with for a small team of less than 5 developers that are developing a webapp in Java with Spring on Eclipse or Netbeans for deployment on Tomcat, Glassfish or Websphere? How difficult would it be to get a consensus on which one of your suggestions is the best. How hard would it be to get agreement on what is the criteria for best. Just for a starting point, in my opinion, the best practice for the above situation would suggest that the project needs a subversion repository, a Nexus community version repository, the Spring STS version of Eclipse, a master POM for the project, a set of library POMs for the shared code and utilities, and a single project POM to build the WAR file. Lots of details to flesh out but they would fit on 1 page with a few pages of POMs, settings and misc. xml samples attached. But IMHO you should be using Git instead of Subversion and STS doesn't have enough management tools to support a large-scale rollout. Are we actually going to be able to reach consensus on those things? I would have no objection to the inclusion of Git in this Best Practice. I have not used it but I have heard good things about it. I am not sure that a 5 man team would be doing a large roll out. There would have to be another Best Practice for that. I am sure that this Best Practice could also be extended to include the use of other IDEs without seriously affecting the methodology. It might require one or 2 pages of addenda to cover minor setup changes but I suspect that it would not affect the POM structure at all. In all seriousness, you should publish this as Ron's Best Practices. If you put something up on Lulu or whatever, I would read it and I would probably recommend it to others. There isn't enough documentation about Maven; I just don't think the community can produce the type of documentation you're describing. Justin Ron's Best Practices would have to be Ron's Best Practice I can only make suggestion about what I have learned in my own experience. I have not done a large scale roll-out. I have a small team. For example, I do not need many of the features of Nexus Professional but that does not mean that some of the people starting out with there first project will not have a larger team and a more demanding management structure, I am not even sure if I am doing
Re: Dealing with artifacts that have been moved - What to do?
Thiessen, Todd (Todd) wrote: Interesting. Much of what you say I think is already documented. For example the definitive guide explains quite well that by convention Maven supports one artifact per project. It also contains many if not most of the best practices that users often ask on this list how to circumvent. But I know what you are getting at. This best practices guide would be a short summary of statements you find in books like the Definitive Guide, Better Builds with Maven and many of the blogs on the Sonatype web site. But the guide would need to at least reference why these practices are in fact best practices. What are the consequences of not following a best practice? In many cases, these explanations would be short but in others it wouldn't. This could make the best practices document turn into a fairly large beast that just re-iterated what is already in other documents. This duplication can be a pain to manage. As the true documents change over time, the best practices document would have to change also. Just one more document to update and keep in sync. Who will want to do that? I would hope that the Best Pratices would link to other documents for most of the details. There is no need to get too redundant in this day of easy hyperlinks I don't want to rain on your idea too much, since I think it does have a lot of merit. However, I also am not fully bought into it. As a final note, the best practices guide should NOT say what repository manager or SCM one should use. That isn't a space I think Maven should get into. I think it is valid to say that its a best practice that a repo manager is used, but to get into which one is best. Same with SCM. It also shouldn't say which which libraries to use. Those can be completely different depending on the project. I agree with this with the caviate that the Best Practice needs to be specific about some things and I would want to have a paragraph discussing the differences in the Best practice that is caused by choosing one SCM over another. If you use Eclipse and Subversion then you need to do the following but if you use Git then you need to do this other thing. The specification of the use case also has an impact on the Best Practice. If the use case is We have a Subversion SCM and use Eclipse STS as our IDE and do not have a Maven repository, it will be different than We are considering either Git or Subversion as our SCM and are using Netbeans as or IDE. A lot will be the same in terms of strategy but the details and reference links will be different. There is a s in Best Practices for a reason. It could perhaps list certain libraries and discuss the pros/cons of each, but again, this can change over time and isn't really a best practice. It also could perhaps state which SCMs Maven currently works with, which would help someone looking into Maven to decide if they wanted to use it. But again, this kind of information is hard to keep up to date and isn't really a Best Practices thing. This is the kind of info that a Best Practice links to rather than documents. -Original Message- From: Ron Wheeler [mailto:rwhee...@artifact-software.com] Sent: Thursday, March 18, 2010 3:55 PM To: Maven Users List Subject: Re: Dealing with artifacts that have been moved - What to do? Wayne Fay wrote: - unambiguous - no you might do this or mayby that just if your situation is this and you want the best development environment do exactly this. But notice some recent questions on the list... - how to compile from multiple source directories - migrating a large ant build to maven without any power to reorg the files/projects - etc It seems pretty rare that someone is looking for what you are proposing to create... My suspicion is that these are caused by not following the Best Practice for Maven. Under what circumstance would you recommend to a user that they set up a project that required 2 source directories? In the end, I suspect that they really have 2 (or more) projects with 1 source directory each with dependencies between them. Once they Mavenize their project structure, they will find that they do not need these gymnastics. Migration is always tough and may be one of the last Best Practices to emerge. Your suggestion, if I recall correctly was to not try to Mavenize in the face of an entrenched Ant lobby until you had established a high level buy-in. That in itself could be the root of a Best Practice that is less about Maven technical issues and more about how to plan and organize a large scale methodology upgrade and how to justify the investment to management and the rest of the team. The fact that a number of people are not looking for the right things is due to a certain extent to the power and flexibility of Maven and the lack of a set of Best Practices. Maven is one of those tools that really needs
RE: How to perform ordered tasks in Maven2 build
Hey Wayne, We don't need to start name calling here. zealous ant users? Would that be someone who believes that their favorite tool must be best for everybody. Remind you of anyone? There are ant users and maven users. And there are zealous users and pragmatic users. You don't have to be a zealous user to believe that the tool you are using is working fine and it would be a lot of work to change. Instead of insisting that people change and complaining (or name calling) if they are reluctant, let's take the approach of trying to supply the information we believe that they are not aware of yet. You know, that information that if they knew it then they would definitely agree with us. So what is it that these zealous ant users should know? I think maybe it is Where is the evidence that me using Maven will make my customers happier? We've all heard of the latest greatest thing that would provide massive long term benefits if only we would accept the short term pain. Pascal, CASE tools, OOD, UML, giving up smoking, losing weight, etc. Some people just want you to try everything they think is good. Other people are naturally resistant. I told the engineers here that management had decided that we would have to change to Maven because it would look so good on everybody's resume. It's odd to have management insisting that we change. After so many years complaining that management only looked at the short term goals, now it's management that is looking at the long term and the engineers still doubt that they know what they're doing. So, even management buy-in isn't the magic pill to success. !-- Frank Gorham-Engard → It is a misnomer to label any practice 'a best practice'; a practice is only best in the specific context in which it performs well. -Original Message- From: Wayne Fay [mailto:wayne...@gmail.com] Sent: Thursday, March 18, 2010 2:28 PM To: Maven Users List Subject: Re: How to perform ordered tasks in Maven2 build It was key for us that it happened in a grass roots fashion. A meritocrocy approach, while slow, is generally the best way to get buy in. If you force it, everyone will hate it and not be very productive. I agree 100% with the grassroots, meritocracy approach. But it sounded like the OP in this thread has no real power to re-architect his projects/builds and he is working with zealous ant users. We know that is the path to failure. So someone, somewhere needs to give him this power -- ideally its the dev team(s) he is working with, but it could also be the person they report to, depending on the culture of the org and the norms in their locale (Asia vs Europe vs US etc). Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to perform ordered tasks in Maven2 build
Hey Wayne, We don't need to start name calling here. zealous ant users? Would that be someone who believes that their favorite tool must be best for everybody. Remind you of anyone? Read the posts in this thread from Ronen Perez before making assumptions about me calling anyone names... this is simply incorrect. In the words of Benjamin Franklin it is better to be thought a fool than to open your mouth and remove all doubt. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
including dependency jars within EJB jar
Hi All, I am creating an EJB jar (not EJB-client). Its supposed to have a dependency jar (ussi.jar) included within it for deployment, but the EJB jar created never contains the ussi.jar. I am using compile-scope dependencies. If you do have a few minutes, please take a look at the following -- if needed, I can send the entire POM as well as contents of JAR file. The ussi.jar is a simple library, and was put into local (~/.m2/repository) using the mvn install command-line. mvn install:install-file \ -Dfile=ussi/dist/ussi.jar \ -DgroupId=com.uss-infr\ -DartifactId=ussi\ -Dversion=1.10\ -Dpackaging=jar\ -DgeneratePom=true 1st relevant portion of the POM for EJB project is: modelVersion4.0.0/modelVersion groupIdorg.ASUX.CmdLineClients/groupId artifactIdCronJarTemplate/artifactId packagingejb/packaging version2.1/version 2nd relevant portion of the POM for EJB project is: dependency groupIdcom.uss-infr/groupId artifactIdussi/artifactId version1.10/version scopecompile/scope optionalfalse/optional !-- not having this element makes no difference -- /dependency For compile scope, the build is successful with no warnings or errors. If I change the scope to runtime the built fails (as it should). # OS name: linux version: 2.6.31-20-generic arch: amd64 Family: unix # Java version: 1.6.0_18 # Maven version: 2.0.8 Upgrading to Maven 2.2.1 did not make any difference. Thanks in advance! Sarma Seetamraju smime.p7s Description: S/MIME Cryptographic Signature
Re: including dependency jars within EJB jar
Its supposed to have a dependency jar (ussi.jar) included within it for deployment, but the EJB jar created never contains the ussi.jar. I am using compile-scope dependencies. Google for maven ejb jar bundle gave this link at the top: http://magnus-k-karlsson.blogspot.com/2009/08/bundle-common-jar-into-ejb-jar-with.html As always when this question is posted, I have to ask, what Java app server or EJB container and JVM/JDK are you using? AFAIK few classloaders support this arrangement of jar-within-jar. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
3rd party JARs -- local vs. remote repositories
Hi, For the following, lets take a simple example of :- Create a Session Bean that is deployed --by itself-- and not within a EAR. And also, lets assume that the session bean depends on a commercial (3rd party) JAR for (say) statistical analysis. EJB jars always had dependency JARs located under META-INF/lib; Has this changed? i.e., should each EJB and all the JARs that it depends on, be packages as an EAR? Thanks for the google link. I didn't use the keyword bundle, when I did my searches. I just googled maven 3rd party jars and got a completely new set of links. Except that all the suggestions fail for me, with the --only-- difference that I am using local (~/.m2/repository) instead of a remote repository. Why should that matter? Thanks again in advance! Wayne Fay wrote: Its supposed to have a dependency jar (ussi.jar) included within it for deployment, but the EJB jar created never contains the ussi.jar. I am using compile-scope dependencies. Google for maven ejb jar bundle gave this link at the top: http://magnus-k-karlsson.blogspot.com/2009/08/bundle-common-jar-into-ejb-jar-with.html As always when this question is posted, I have to ask, what Java app server or EJB container and JVM/JDK are you using? AFAIK few classloaders support this arrangement of jar-within-jar. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org smime.p7s Description: S/MIME Cryptographic Signature
Tar header error from assembly plugin
Anyone have any help for this? [INFO] Failed to create assembly: Error creating assembly archive src: Problem creating TAR: request to write '4218' bytes exceeds size in header of '4095' bytes - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [ANN] Riding Ruby on Rails3 with Maven3
On Thu, Mar 18, 2010 at 7:18 PM, Karl Heinz Marbaise k...@soebes.de wrote: But i know of the nar plugins which are used for C++/C compilings etc. and dependency download (nar-files) etc. and they are working for MVN 2.2.1 as well... http://duns.github.com/maven-nar-plugin/ that is great - I will have a look at it and see if I can borrow something. but when I look at polyglot-maven ruby support then that should be the tool for working with ruby projects and polyglot-maven is maven3. so I think the future is maven3 (hopefully it sees some beta release soon ;-)) regards Kristian Kind regards Karl Heinz Marbaise -- View this message in context: http://old.nabble.com/-ANN--Riding-Ruby-on-Rails3-with-Maven3-tp27941758p27945765.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 -- Kristian Meier + Saumya Sharma + Sanuka Meier Vadakkethu House, Edayanmula West PO - 689532, Pathanamthitta District, Kerala, INDIA tel: +91 468 2319577 protect your privacy while searching the net: www.ixquick.com _=_ q(-_-)p '_) (_` /__/ \ _(_ / )_ (__\_\_|_/__) - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: 3rd party JARs -- local vs. remote repositories
EJB jars always had dependency JARs located under META-INF/lib; Has this changed? Again, what Java app server or EJB container and JVM/JDK are you using? This is not part of the JAR specification [1] and does not comply with Sun's advice regarding J2EE packaging in general [2]. i.e., should each EJB and all the JARs that it depends on, be packages as an EAR? Yes, an Ear or a War, or in some situations a Rar or another format. [1] http://java.sun.com/j2se/1.4.2/docs/guide/jar/jar.html [2] http://java.sun.com/j2ee/verified/packaging.html Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
