Maven 3 no longer supporting dynamic configuration of plugins?
Over time, I have written several Maven plugins that configure other plugins by manipulating their configuration section (with the Xpp3Dom API). This technique has often proved to be a life saver. For example, I have a plugin that determines dynamically which JUnit tests should be run, and configures Surefire accordingly (by adding includes). With Maven 3, this technique no longer seems to work. I don't get any errors, but the plugins to be configured don't see any changes made to their configuration section, even if I perform the changes as early as in the initialize phase. Is this an intentional change? And what is the alternative? Cheers, Peter PS: Is there any documentation about writing plugins for Maven 3 (Guice DI, new APIs, breaking changes, etc.)? Can't find anything.
Maven 3 no longer supporting dynamic configuration of plugins?
Over time, I have written several Maven plugins that configure other plugins by manipulating their configuration section (with the Xpp3Dom API). This technique has often proved to be a life saver. For example, I have a plugin that determines dynamically which JUnit tests should be run, and configures Surefire accordingly (by adding includes). With Maven 3, this technique no longer seems to work. I don't get any errors, but the plugins to be configured don't see any changes made to their configuration section, even if I perform the changes as early as in the initialize phase. Is this an intentional change? And what is the alternative? Cheers, Peter PS: Is there any documentation about writing plugins for Maven 3 (Guice DI, new APIs, breaking changes, etc.)? Can't find anything. -- View this message in context: http://maven.40175.n5.nabble.com/Maven-3-no-longer-supporting-dynamic-configuration-of-plugins-tp3279449p3279449.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: Maven 3 no longer supporting dynamic configuration of plugins?
This is a good example of my belief, that it should be possible to invoke other plugins dynamically by supplying an own configuration section from your own plugin. On Thu, Nov 25, 2010 at 6:00 AM, Peter Niederwieser pnied...@gmail.com wrote: Over time, I have written several Maven plugins that configure other plugins by manipulating their configuration section (with the Xpp3Dom API). This technique has often proved to be a life saver. For example, I have a plugin that determines dynamically which JUnit tests should be run, and configures Surefire accordingly (by adding includes). With Maven 3, this technique no longer seems to work. I don't get any errors, but the plugins to be configured don't see any changes made to their configuration section, even if I perform the changes as early as in the initialize phase. Is this an intentional change? And what is the alternative? Cheers, Peter PS: Is there any documentation about writing plugins for Maven 3 (Guice DI, new APIs, breaking changes, etc.)? Can't find anything. -- I Am What I Am And That's All What I Yam (Popeye) - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
maven 3 parallel build with jspc plugin
Hi, I am using maven-jetty-jspc-plugin in my pom to pre-compile jsps. I tried the parallel build of maven 3 but it fails for this plugin as its not threadsafe. I then tried jspc-maven-plugin also but its not not threadsafe. Anybody have any idea about these plugins or any other plugin to pre-compile jsp and supports parallel builds. Thanks Bhushan
Re: Problem with annotations processing and maven compiler plugin
typewar/type /dependency /dependencies A dependency of type war means basically nothing to Javac. You're basically just putting the War file on the classpath and javac doesn't know how to deal with wars (only jars) so it just gets ignored. Try again after you package your annotation processor up in its own jar, and depend on that. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven 3.0 timestamp
On Thu, Nov 25, 2010 at 12:24 AM, Moser, Christian c...@metrohm.com wrote: I wonder in which specific time/timezone maven 3.0 writes the timestamp into maven-metadata for local and remote artifacts? Is it supposed to write GMT + 0:0 or the same time set on the local machine, in my case Maven 2.x writes the timestamp data using GMT+0:0. I have no specific knowledge that M3 does the same, but cannot imagine it would have been changed -- that would potentially break a lot of things in difficult to diagnose ways. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven 3 parallel build with jspc plugin
I am using maven-jetty-jspc-plugin in my pom to pre-compile jsps. I tried the parallel build of maven 3 but it fails for this plugin as its not threadsafe. I then tried jspc-maven-plugin also but its not not threadsafe. Anybody have any idea about these plugins or any other plugin to pre-compile jsp and supports parallel builds. It may be simple to just modify those existing open-source plugins to support parallel builds. I don't know much about parallel building in M3 in general, but know the jspc-m-p and the code is pretty easy to understand, so you could probably modify it (minimally, I'd hope) to make it work. Otherwise file a JIRA ticket and wait for someone else to need this and work on it. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Mvn 3: Dependency list vs Dependency tree
Hello, I have just migrated from Maven 2.0.9 to Maven 3.0.0. Everything compiles, tests as expected, but it doesn't run. I get some useless librairies in my WEB-INF\lib with old versions. Looking in the dependency tree for the origin of theses dependencies, they are not present. But they are present in dependency list! Look at the net.sf.ehcache:ehcache:jar:1.5.0 or com.mycompany:fwk-i18nImpl:jar:1.5 or com.oracle:ojdbc14:jar:10.2.0.4.0 dependencies in the following logs. I have tried to tweak dependency exclusions without success. What can I do to understand what's happening and fix it? Gérald [INFO] --- maven-dependency-plugin:2.1:tree (default-cli) @ app-remoting --- [INFO] com.mycompany:app-remoting:war:2.1.0-SNAPSHOT [INFO] +- com.mycompany:app-facade1:jar:2.1.0-SNAPSHOT:compile [INFO] | +- com.mycompany:app-domain:jar:2.1.0-SNAPSHOT:compile [INFO] | | +- com.mycompany:hab-domain:jar:1.1.6:compile [INFO] | | +- com.mycompany:ref-domain:jar:1.6.4:compile [INFO] | | +- com.mycompany:fwk-i18n:jar:1.6.6:compile [INFO] | | +- javax.persistence:persistence-api:jar:1.0:compile [INFO] | | +- net.sf.ehcache:ehcache-core:jar:2.1.0:runtime [INFO] | | +- backport-util-concurrent:backport-util-concurrent:jar:3.1:runtime [INFO] | | \- net.sourceforge.jexcelapi:jxl:jar:2.6:compile [INFO] | \- com.mycompany:app-integration:jar:2.1.0-SNAPSHOT:compile [INFO] | +- org.springframework.integration:spring-integration-core:jar:1.0.3.RELEASE:compile [INFO] | \- org.springframework.integration:spring-integration-file:jar:1.0.3.RELEASE:compile [INFO] +- com.mycompany:app-facade1Impl:jar:2.1.0-SNAPSHOT:runtime [INFO] | +- com.mycompany:hab-core-facade:jar:2.0.0:runtime [INFO] | | \- com.mycompany:hab-core-domain:jar:2.0.0:runtime [INFO] | +- com.mycompany:ref-facade:jar:1.6.4:runtime [INFO] | +- com.mycompany:ref-facadeImpl:jar:1.6.4:runtime [INFO] | +- com.mycompany:ref-repository:jar:1.6.4:runtime [INFO] | +- com.mycompany:ref-repositoryImpl:jar:1.6.4:runtime [INFO] | +- org.springframework:spring-jms:jar:2.5.6:runtime [INFO] | +- javax.sql:jdbc-stdext:jar:2.0:runtime [INFO] | \- com.mycompany:syn-fwk-observer:jar:2.2.4:runtime [INFO] +- com.mycompany:app-facade2:jar:2.1.0-SNAPSHOT:compile [INFO] | \- com.mycompany:arp-comm:jar:0.42:compile [INFO] +- com.mycompany:app-facade2Impl:jar:2.1.0-SNAPSHOT:runtime [INFO] | +- com.mycompany:fwk-impression:jar:1.6.6:runtime [INFO] | +- com.mycompany:fwk-impressionImpl:jar:1.6.6:runtime [INFO] | | +- org.apache.ws.commons.axiom:axiom-impl:jar:1.2.7:runtime [INFO] | | | +- org.apache.ws.commons.axiom:axiom-api:jar:1.2.7:runtime [INFO] | | | | \- jaxen:jaxen:jar:1.1.1:runtime [INFO] | | | +- org.apache.geronimo.specs:geronimo-activation_1.1_spec:jar:1.0.1:runtime [INFO] | | | +- org.apache.geronimo.specs:geronimo-javamail_1.4_spec:jar:1.2:runtime [INFO] | | | +- org.codehaus.woodstox:wstx-asl:jar:3.2.4:runtime [INFO] | | | \- org.apache.geronimo.specs:geronimo-stax-api_1.0_spec:jar:1.0.1:runtime [INFO] | | \- org.codehaus.castor:castor:jar:1.2:runtime [INFO] | +- org.springframework.ws:spring-ws-core:jar:1.5.7:runtime [INFO] | | +- org.springframework.ws:spring-xml:jar:1.5.7:runtime [INFO] | | +- org.springframework.ws:spring-oxm:jar:1.5.7:runtime [INFO] | | \- wsdl4j:wsdl4j:jar:1.6.1:runtime [INFO] | +- org.springframework.ws:spring-ws-core-tiger:jar:1.5.7:runtime [INFO] | +- com.mycompany:hab-core-facadeImpl:jar:2.0.0:runtime [INFO] | | \- com.mycompany:hab-core-repository:jar:2.0.0:runtime [INFO] | \- com.mycompany:hab-core-repositoryImpl:jar:2.0.0:runtime [INFO] +- com.mycompany:app-commun:jar:2.1.0-SNAPSHOT:compile [INFO] | +- com.mycompany:etj-xom:jar:2.0.4:compile [INFO] | \- quartz:quartz:jar:1.6.5:compile [INFO] +- com.mycompany:app-communImpl:jar:2.1.0-SNAPSHOT:runtime [INFO] +- com.mycompany:app-integrationImpl:jar:2.1.0-SNAPSHOT:runtime [INFO] | +- org.springframework.integration:spring-integration-ws:jar:1.0.3.RELEASE:runtime [INFO] | | \- org.springframework.integration:spring-integration-adapter:jar:1.0.3.RELEASE:runtime [INFO] | +- org.springframework.integration:spring-integration-xml:jar:1.0.3.RELEASE:runtime [INFO] | +- org.springframework.ws:spring-oxm-tiger:jar:1.5.7:runtime [INFO] | \- org.springframework.integration:spring-integration-jms:jar:1.0.3.RELEASE:runtime [INFO] +- com.mycompany:app-impression:jar:2.1.0-SNAPSHOT:runtime [INFO] +- com.mycompany:syn-refRemoteFacade:jar:2.2.4-R1.6.4:runtime [INFO] | +- com.mycompany:syn-refSchema:jar:2.2.4-R1.6.4:runtime [INFO] | | \- com.mycompany:syn-fwkSchema:jar:2.2.4-R1.6.4:runtime [INFO] | +- com.mycompany:syn-fwk-Moteur:jar:2.2.4:runtime [INFO] | | \- com.mycompany:syn-fwk-observerImpl:jar:2.2.4:runtime [INFO] | +- org.springframework.integration:spring-integration-stream:jar:1.0.3.RELEASE:runtime [INFO] | \- com.thoughtworks.xstream:xstream:jar:1.3.1:runtime [INFO] | \- xpp3:xpp3_min:jar:1.1.4c:runtime [INFO] +-
Create jar from ear project or create 2 jars from jar project
Hi, we need to create a jar that only contains 2 xml files but nothing more. Because we have just those 2 files, we don't want to create a new project for that (especially since Eclipse can't display projects hierarchically). So the question is: Is it possible to create a JAR containing those 2 files from either an EAR-Module or a JAR-Module? I tried both, using the maven-jar-plugin, but wasn't yet successful. The problem is that normal EAR or JAR creation should not be affected, however in the EAR project the artifact was deployed/installed using the EAR's artifact id. Is there a way to create two artifacts from one EAR project? Or is there a way to create two distinct jars from one JAR project in one run, e.g. not having to start multiple runs with different profiles/properties ? Thanks in advance.
Re: Mvn 3: Dependency list vs Dependency tree
Hello, check your dependency:tree again, I can see net.sf.ehcache:ehcache:jar:1.5.0 and com.oracle:ojdbc14:jar:10.2.0.4.0 at least. I also recommend you to check help:effective-pom to check if these dependencies didn't get included through your pom hierarchy. Vincent 2010/11/25 Gérald Quintana gerald.quint...@gmail.com Hello, I have just migrated from Maven 2.0.9 to Maven 3.0.0. Everything compiles, tests as expected, but it doesn't run. I get some useless librairies in my WEB-INF\lib with old versions. Looking in the dependency tree for the origin of theses dependencies, they are not present. But they are present in dependency list! Look at the net.sf.ehcache:ehcache:jar:1.5.0 or com.mycompany:fwk-i18nImpl:jar:1.5 or com.oracle:ojdbc14:jar:10.2.0.4.0 dependencies in the following logs. I have tried to tweak dependency exclusions without success. What can I do to understand what's happening and fix it? Gérald [INFO] --- maven-dependency-plugin:2.1:tree (default-cli) @ app-remoting --- [INFO] com.mycompany:app-remoting:war:2.1.0-SNAPSHOT [INFO] +- com.mycompany:app-facade1:jar:2.1.0-SNAPSHOT:compile [INFO] | +- com.mycompany:app-domain:jar:2.1.0-SNAPSHOT:compile [INFO] | | +- com.mycompany:hab-domain:jar:1.1.6:compile [INFO] | | +- com.mycompany:ref-domain:jar:1.6.4:compile [INFO] | | +- com.mycompany:fwk-i18n:jar:1.6.6:compile [INFO] | | +- javax.persistence:persistence-api:jar:1.0:compile [INFO] | | +- net.sf.ehcache:ehcache-core:jar:2.1.0:runtime [INFO] | | +- backport-util-concurrent:backport-util-concurrent:jar:3.1:runtime [INFO] | | \- net.sourceforge.jexcelapi:jxl:jar:2.6:compile [INFO] | \- com.mycompany:app-integration:jar:2.1.0-SNAPSHOT:compile [INFO] | +- org.springframework.integration:spring-integration-core:jar:1.0.3.RELEASE:compile [INFO] | \- org.springframework.integration:spring-integration-file:jar:1.0.3.RELEASE:compile [INFO] +- com.mycompany:app-facade1Impl:jar:2.1.0-SNAPSHOT:runtime [INFO] | +- com.mycompany:hab-core-facade:jar:2.0.0:runtime [INFO] | | \- com.mycompany:hab-core-domain:jar:2.0.0:runtime [INFO] | +- com.mycompany:ref-facade:jar:1.6.4:runtime [INFO] | +- com.mycompany:ref-facadeImpl:jar:1.6.4:runtime [INFO] | +- com.mycompany:ref-repository:jar:1.6.4:runtime [INFO] | +- com.mycompany:ref-repositoryImpl:jar:1.6.4:runtime [INFO] | +- org.springframework:spring-jms:jar:2.5.6:runtime [INFO] | +- javax.sql:jdbc-stdext:jar:2.0:runtime [INFO] | \- com.mycompany:syn-fwk-observer:jar:2.2.4:runtime [INFO] +- com.mycompany:app-facade2:jar:2.1.0-SNAPSHOT:compile [INFO] | \- com.mycompany:arp-comm:jar:0.42:compile [INFO] +- com.mycompany:app-facade2Impl:jar:2.1.0-SNAPSHOT:runtime [INFO] | +- com.mycompany:fwk-impression:jar:1.6.6:runtime [INFO] | +- com.mycompany:fwk-impressionImpl:jar:1.6.6:runtime [INFO] | | +- org.apache.ws.commons.axiom:axiom-impl:jar:1.2.7:runtime [INFO] | | | +- org.apache.ws.commons.axiom:axiom-api:jar:1.2.7:runtime [INFO] | | | | \- jaxen:jaxen:jar:1.1.1:runtime [INFO] | | | +- org.apache.geronimo.specs:geronimo-activation_1.1_spec:jar:1.0.1:runtime [INFO] | | | +- org.apache.geronimo.specs:geronimo-javamail_1.4_spec:jar:1.2:runtime [INFO] | | | +- org.codehaus.woodstox:wstx-asl:jar:3.2.4:runtime [INFO] | | | \- org.apache.geronimo.specs:geronimo-stax-api_1.0_spec:jar:1.0.1:runtime [INFO] | | \- org.codehaus.castor:castor:jar:1.2:runtime [INFO] | +- org.springframework.ws:spring-ws-core:jar:1.5.7:runtime [INFO] | | +- org.springframework.ws:spring-xml:jar:1.5.7:runtime [INFO] | | +- org.springframework.ws:spring-oxm:jar:1.5.7:runtime [INFO] | | \- wsdl4j:wsdl4j:jar:1.6.1:runtime [INFO] | +- org.springframework.ws:spring-ws-core-tiger:jar:1.5.7:runtime [INFO] | +- com.mycompany:hab-core-facadeImpl:jar:2.0.0:runtime [INFO] | | \- com.mycompany:hab-core-repository:jar:2.0.0:runtime [INFO] | \- com.mycompany:hab-core-repositoryImpl:jar:2.0.0:runtime [INFO] +- com.mycompany:app-commun:jar:2.1.0-SNAPSHOT:compile [INFO] | +- com.mycompany:etj-xom:jar:2.0.4:compile [INFO] | \- quartz:quartz:jar:1.6.5:compile [INFO] +- com.mycompany:app-communImpl:jar:2.1.0-SNAPSHOT:runtime [INFO] +- com.mycompany:app-integrationImpl:jar:2.1.0-SNAPSHOT:runtime [INFO] | +- org.springframework.integration:spring-integration-ws:jar:1.0.3.RELEASE:runtime [INFO] | | \- org.springframework.integration:spring-integration-adapter:jar:1.0.3.RELEASE:runtime [INFO] | +- org.springframework.integration:spring-integration-xml:jar:1.0.3.RELEASE:runtime [INFO] | +- org.springframework.ws:spring-oxm-tiger:jar:1.5.7:runtime [INFO] | \- org.springframework.integration:spring-integration-jms:jar:1.0.3.RELEASE:runtime [INFO] +- com.mycompany:app-impression:jar:2.1.0-SNAPSHOT:runtime [INFO] +- com.mycompany:syn-refRemoteFacade:jar:2.2.4-R1.6.4:runtime [INFO] | +- com.mycompany:syn-refSchema:jar:2.2.4-R1.6.4:runtime [INFO] | | \-
Re: Create jar from ear project or create 2 jars from jar project
Hi, one project = one artifact. You'll get hurt (to various degrees) if you try to fight that principle. Here are a few hints to explore though : - build-helper-plugin to attach additional artifacts to your build - dependency-plugin to copy/unpack resources from other artifacts Vincent 2010/11/25 Thomas Göttlich guo.tu...@googlemail.com Hi, we need to create a jar that only contains 2 xml files but nothing more. Because we have just those 2 files, we don't want to create a new project for that (especially since Eclipse can't display projects hierarchically). So the question is: Is it possible to create a JAR containing those 2 files from either an EAR-Module or a JAR-Module? I tried both, using the maven-jar-plugin, but wasn't yet successful. The problem is that normal EAR or JAR creation should not be affected, however in the EAR project the artifact was deployed/installed using the EAR's artifact id. Is there a way to create two artifacts from one EAR project? Or is there a way to create two distinct jars from one JAR project in one run, e.g. not having to start multiple runs with different profiles/properties ? Thanks in advance.
Re: Problem with annotations processing and maven compiler plugin
Thanks Wayne. I'll try that and post here according to the results. J. 2010/11/25 Wayne Fay wayne...@gmail.com typewar/type /dependency /dependencies A dependency of type war means basically nothing to Javac. You're basically just putting the War file on the classpath and javac doesn't know how to deal with wars (only jars) so it just gets ignored. Try again after you package your annotation processor up in its own jar, and depend on that. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
use version of some dependency for another dependency
Hi. A project indirectly depends on foo-api.jar via some meta artifact
foo-client.
I know the version of this meta artifact, but not the version of
foo-api.jar.
There's also foo-impl.jar that depends on foo-api.jar with the same
version. For example, if foo-client 1.3 depends on foo-api 1.1, I need
to depend on foo-impl 1.1
Now I need to add the foo-impl.jar to my dependencies, and it must be
the same version as foo-api.jar. How?
dependencies
dependency
groupIdorg.foo/groupId
artifactIdfoo-client/artifactId
typepom/type
version1.3/version
/dependency
dependency
groupIdorg.foo/groupId
artifactIdfoo-impl/artifactId
version${version-of-foo-api?}/version
/dependency
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: use version of some dependency for another dependency
On Thu, Nov 25, 2010 at 6:59 AM, Ilya Basin basini...@gmail.com wrote:
Now I need to add the foo-impl.jar to my dependencies, and it must be
the same version as foo-api.jar. How?
Set a property elsewhere in the pom (or further up the hierarchy) and
use that for both versions: ${foo.version}
You'll see this in various open source projects for things like Spring
which have a lot of pieces. As an example, search for 'properties' in
this pom: http://svn.apache.org/repos/asf/archiva/trunk/pom.xml
--
Wendy
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Mvn 3: Dependency list vs Dependency tree
Vincent, You're right for ojdbc14 but not for ehcache (tree contains ehcache-core:jar:2.1.0) and fwk-i18nImpl:jar:1.5. The effective POM doesn't help me to find the culprit. Gérald 2010/11/25 Vincent Latombe vincent.lato...@gmail.com: Hello, check your dependency:tree again, I can see net.sf.ehcache:ehcache:jar:1.5.0 and com.oracle:ojdbc14:jar:10.2.0.4.0 at least. I also recommend you to check help:effective-pom to check if these dependencies didn't get included through your pom hierarchy. Vincent 2010/11/25 Gérald Quintana gerald.quint...@gmail.com Hello, I have just migrated from Maven 2.0.9 to Maven 3.0.0. Everything compiles, tests as expected, but it doesn't run. I get some useless librairies in my WEB-INF\lib with old versions. Looking in the dependency tree for the origin of theses dependencies, they are not present. But they are present in dependency list! Look at the net.sf.ehcache:ehcache:jar:1.5.0 or com.mycompany:fwk-i18nImpl:jar:1.5 or com.oracle:ojdbc14:jar:10.2.0.4.0 dependencies in the following logs. I have tried to tweak dependency exclusions without success. What can I do to understand what's happening and fix it? Gérald [INFO] --- maven-dependency-plugin:2.1:tree (default-cli) @ app-remoting --- [INFO] com.mycompany:app-remoting:war:2.1.0-SNAPSHOT [INFO] +- com.mycompany:app-facade1:jar:2.1.0-SNAPSHOT:compile [INFO] | +- com.mycompany:app-domain:jar:2.1.0-SNAPSHOT:compile [INFO] | | +- com.mycompany:hab-domain:jar:1.1.6:compile [INFO] | | +- com.mycompany:ref-domain:jar:1.6.4:compile [INFO] | | +- com.mycompany:fwk-i18n:jar:1.6.6:compile [INFO] | | +- javax.persistence:persistence-api:jar:1.0:compile [INFO] | | +- net.sf.ehcache:ehcache-core:jar:2.1.0:runtime [INFO] | | +- backport-util-concurrent:backport-util-concurrent:jar:3.1:runtime [INFO] | | \- net.sourceforge.jexcelapi:jxl:jar:2.6:compile [INFO] | \- com.mycompany:app-integration:jar:2.1.0-SNAPSHOT:compile [INFO] | +- org.springframework.integration:spring-integration-core:jar:1.0.3.RELEASE:compile [INFO] | \- org.springframework.integration:spring-integration-file:jar:1.0.3.RELEASE:compile [INFO] +- com.mycompany:app-facade1Impl:jar:2.1.0-SNAPSHOT:runtime [INFO] | +- com.mycompany:hab-core-facade:jar:2.0.0:runtime [INFO] | | \- com.mycompany:hab-core-domain:jar:2.0.0:runtime [INFO] | +- com.mycompany:ref-facade:jar:1.6.4:runtime [INFO] | +- com.mycompany:ref-facadeImpl:jar:1.6.4:runtime [INFO] | +- com.mycompany:ref-repository:jar:1.6.4:runtime [INFO] | +- com.mycompany:ref-repositoryImpl:jar:1.6.4:runtime [INFO] | +- org.springframework:spring-jms:jar:2.5.6:runtime [INFO] | +- javax.sql:jdbc-stdext:jar:2.0:runtime [INFO] | \- com.mycompany:syn-fwk-observer:jar:2.2.4:runtime [INFO] +- com.mycompany:app-facade2:jar:2.1.0-SNAPSHOT:compile [INFO] | \- com.mycompany:arp-comm:jar:0.42:compile [INFO] +- com.mycompany:app-facade2Impl:jar:2.1.0-SNAPSHOT:runtime [INFO] | +- com.mycompany:fwk-impression:jar:1.6.6:runtime [INFO] | +- com.mycompany:fwk-impressionImpl:jar:1.6.6:runtime [INFO] | | +- org.apache.ws.commons.axiom:axiom-impl:jar:1.2.7:runtime [INFO] | | | +- org.apache.ws.commons.axiom:axiom-api:jar:1.2.7:runtime [INFO] | | | | \- jaxen:jaxen:jar:1.1.1:runtime [INFO] | | | +- org.apache.geronimo.specs:geronimo-activation_1.1_spec:jar:1.0.1:runtime [INFO] | | | +- org.apache.geronimo.specs:geronimo-javamail_1.4_spec:jar:1.2:runtime [INFO] | | | +- org.codehaus.woodstox:wstx-asl:jar:3.2.4:runtime [INFO] | | | \- org.apache.geronimo.specs:geronimo-stax-api_1.0_spec:jar:1.0.1:runtime [INFO] | | \- org.codehaus.castor:castor:jar:1.2:runtime [INFO] | +- org.springframework.ws:spring-ws-core:jar:1.5.7:runtime [INFO] | | +- org.springframework.ws:spring-xml:jar:1.5.7:runtime [INFO] | | +- org.springframework.ws:spring-oxm:jar:1.5.7:runtime [INFO] | | \- wsdl4j:wsdl4j:jar:1.6.1:runtime [INFO] | +- org.springframework.ws:spring-ws-core-tiger:jar:1.5.7:runtime [INFO] | +- com.mycompany:hab-core-facadeImpl:jar:2.0.0:runtime [INFO] | | \- com.mycompany:hab-core-repository:jar:2.0.0:runtime [INFO] | \- com.mycompany:hab-core-repositoryImpl:jar:2.0.0:runtime [INFO] +- com.mycompany:app-commun:jar:2.1.0-SNAPSHOT:compile [INFO] | +- com.mycompany:etj-xom:jar:2.0.4:compile [INFO] | \- quartz:quartz:jar:1.6.5:compile [INFO] +- com.mycompany:app-communImpl:jar:2.1.0-SNAPSHOT:runtime [INFO] +- com.mycompany:app-integrationImpl:jar:2.1.0-SNAPSHOT:runtime [INFO] | +- org.springframework.integration:spring-integration-ws:jar:1.0.3.RELEASE:runtime [INFO] | | \- org.springframework.integration:spring-integration-adapter:jar:1.0.3.RELEASE:runtime [INFO] | +- org.springframework.integration:spring-integration-xml:jar:1.0.3.RELEASE:runtime [INFO] | +- org.springframework.ws:spring-oxm-tiger:jar:1.5.7:runtime [INFO] | \-
Re[2]: use version of some dependency for another dependency
WS Set a property elsewhere in the pom (or further up the hierarchy) and
WS use that for both versions: ${foo.version}
I don't know the version of foo-api and foo-impl.
--
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
maven-release-plugin: computed releaseVersion used as property?
Hello,
I would like to use the maven-release-plugin and set a different
release tag without the need of interacting.
Additional I need to use the computed release version as part of the tag.
I tried to configure it like this:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-release-plugin/artifactId
configuration
tag${project.groupId}.${project.artifactId}-${releaseVersion}/tag
/configuration
/plugin
Unfortunately, there is no ${releaseVersion} property.
${project.version} is computed with the old -SNAPSHOT value.
Is there a way, how I can configure the maven-release-plugin to work this way?
Regards,
Lars
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Re[2]: use version of some dependency for another dependency
foo-impl:1.2.3 should depend on foo-api:1.2.3. Then add a dependency
on foo-impl:1.2.3, and you'll get a dependency on foo-api:1.2.3.
Gérald
2010/11/25 Ilya Basin basini...@gmail.com:
WS Set a property elsewhere in the pom (or further up the hierarchy) and
WS use that for both versions: ${foo.version}
I don't know the version of foo-api and foo-impl.
--
-
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
Range resolution does not work as docuented? was: Range resolution changed from 2.1?
On 11/17/2010 07:36 PM, uwe schaefer wrote: Hello, i am sorry, but i am really puzzled about this. the way i get it, (Snapshots aside) maven, from 2.2 on, does no longer work as documented here: http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution can someone please confirm this and point me to the right document? currently, we cannot update from 2.1 due to this problem, and we don´t know what to change. It is the same for a bunch of archetype POMs existing, the one from Apache Wicket being one of them. thanks, uwe - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Re[2]: use version of some dependency for another dependency
On Thu, Nov 25, 2010 at 7:49 AM, Ilya Basin basini...@gmail.com wrote:
WS Set a property elsewhere in the pom (or further up the hierarchy) and
WS use that for both versions: ${foo.version}
I don't know the version of foo-api and foo-impl.
If your project code depends on it, you need to know.
If it's a transitive dependency, then it should be in the pom for the
project you depend on, and you won't need to worry about it --
complain to the developers of *that* project until they fix their pom.
(How are they compiling if it's not in there? Is it an optional
dependency?)
--
Wendy
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Increment Project-Version at build with Maven and Hudson
Hello, I use Hudson with Maven for building my Java Application. I have one Maven project, where i want to increment automatically the version of the project in the pom-file everytime when a Hudson-build runs. The Maven-Release-Plugin isn't suitable in this case because i don't use Snapshot-versions of that project. I know the Maven-Versions-Plugin and its set-goal, but there i have to declare explicitly the new version, as far as i understand the function of that goal.. Is there any other Maven- or Hudson-Plugin which can i use? Regards, Manuel - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Mvn 3: Dependency list vs Dependency tree
The problem doesn't occur with Maven 2.2.1 either, so it's related to something different between 2.2.1 et 3.0.0 Gérald 2010/11/25 Gérald Quintana gerald.quint...@gmail.com: Hello, I have just migrated from Maven 2.0.9 to Maven 3.0.0. Everything compiles, tests as expected, but it doesn't run. I get some useless librairies in my WEB-INF\lib with old versions. Looking in the dependency tree for the origin of theses dependencies, they are not present. But they are present in dependency list! Look at the net.sf.ehcache:ehcache:jar:1.5.0 or com.mycompany:fwk-i18nImpl:jar:1.5 or com.oracle:ojdbc14:jar:10.2.0.4.0 dependencies in the following logs. I have tried to tweak dependency exclusions without success. What can I do to understand what's happening and fix it? Gérald - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Problem with annotations processing and maven compiler plugin
It works very well. Thanks to both of you! J. 2010/11/25 Julien Martin bal...@gmail.com Thanks Wayne. I'll try that and post here according to the results. J. 2010/11/25 Wayne Fay wayne...@gmail.com typewar/type /dependency /dependencies A dependency of type war means basically nothing to Javac. You're basically just putting the War file on the classpath and javac doesn't know how to deal with wars (only jars) so it just gets ignored. Try again after you package your annotation processor up in its own jar, and depend on that. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: RE: Continuous Delivery and Maven
http://jira.codehaus.org/browse/MRELEASE-621 will be needed to get the hooks in place for v-m-p... once I have that done (and pushed a m-r-p release) then I will do the v-m-p stuff (assuming I have got v-m-p's integration tests portable by then!) -Stephen On 24 November 2010 20:02, Stephen Connolly stephen.alan.conno...@gmail.com wrote: That's an enhancement to versions-maven-plugin This is the hook for deployment (aka shipping) - Stephen --- Sent from my Android phone, so random spelling mistakes are a direct result of using swype to type on the screen On 24 Nov 2010 18:45, Yanko, Curtis curt_ya...@uhc.com wrote: I though the idea we talked about was to re-write the POM that get's packaged with the actual version used from a version range? Curt Yanko | Continuous Integration Services | UnitedHealth Group IT Making IT Happen, one build at a time, 600 times a day -Original Message- From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] ... This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. - To unsubscribe, e-mail: user...
Re: Increment Project-Version at build with Maven and Hudson
Why not follow the maven way, leave the version in SCM as a SNAPSHOT, and let hudson do the releases for you... If you object to maven-release -plugin effectively running the build twice, then switch the preparationGoals to validate - Stephen --- Sent from my Android phone, so random spelling mistakes are a direct result of using swype to type on the screen On 25 Nov 2010 14:42, Manuel Doninger manuel.donin...@googlemail.com wrote: Hello, I use Hudson with Maven for building my Java Application. I have one Maven project, where i want to increment automatically the version of the project in the pom-file everytime when a Hudson-build runs. The Maven-Release-Plugin isn't suitable in this case because i don't use Snapshot-versions of that project. I know the Maven-Versions-Plugin and its set-goal, but there i have to declare explicitly the new version, as far as i understand the function of that goal.. Is there any other Maven- or Hudson-Plugin which can i use? Regards, Manuel - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Doxia Tools shared component 1.3 Released
The Maven team is pleased to announce the release of the Maven Doxia Tools shared component, version 1.3 This component assists in using Doxia for site generation and report creation. http://maven.apache.org/shared/maven-doxia-tools/ You should specify the version in your project's dependency configuration: dependency groupIdorg.apache.maven.shared/groupId artifactIdmaven-doxia-tools/artifactId version1.3/version /dependency Release Notes - Maven Shared Components - Version maven-doxia-tools 1.3 ** Improvement * [MSHARED-158] - add GAV to information message Parent project loaded from repository * [MSHARED-164] - Avoid needless resolution of local parent POM if relativePath is empty ** Task * [MSHARED-156] - update maven-reporting-api dependency to 3.0 (decoupled from Maven Core) * [MSHARED-157] - upgrade source to java 5 * [MSHARED-170] - Update to Doxia 1.1.4 Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven 3.0 doesn't download sources
Hi, Artifactory 2.3.0+ supports the m3 format for maven-metadata.xml for snapshot artifacts. But, if you upgraded to 2.3.x and still think there is something wrong on the Artifactory side, better ask on the Artifactory user list and we'll be happy to assist you there. Thanks, On Wed, Nov 24, 2010 at 8:34 AM, Moser, Christian c...@metrohm.com wrote: I could imagine the culprit could be artifactory. We were forced to update from 2.2.2 to 2.2.3, otherwise we weren't be able to deploy with maven 3.0 (metadata issue in Artifactory 2.2.2, deploy worked only in legacy mode). In the meantime just to be sure, we updated to 2.3.1. But were also required to change all our repositories to handle non-unique snapshots and to deploy every snapshot again. It was necessary to use non-unique snapshots in artifactory because maven was overriding newer locally installed artifacts, with older remote artifacts everytime we tried to install a new artifact. But regarding my two maven user list entries (Maven 3.0 doesn't download sources / Maven 3.0 doesn't update snapshot artifacts) it seems there are some metadata issues with artifactory maven 3.0. So, the right way to go with maven 3.0 is to use repositories with unique (timestamped) snapshots artifacts? But this won't work with artifactory at least not with version 2.2.3. -thx Chris -Ursprüngliche Nachricht- Von: Brett Porter [mailto:br...@porterclan.net] Im Auftrag von Brett Porter Gesendet: Dienstag, 23. November 2010 23:14 An: Maven Users List Betreff: Re: Maven 3.0 doesn't download sources There's a couple of potential things in the way you've described it: - Maven 3.0 does not support non-unique snapshots - you would need to use timestamps and rely on the repo manager to purge old versions - if I've misunderstood the above, the difference on timestamps is that Maven 3.0 will actually store separate metadata per classifier. They should be the same in the scenario you describe, but maybe Artifactory doesn't support the new metadata format and affects it in some way. HTH, Brett On 24/11/2010, at 3:21 AM, Stephen Connolly wrote: Don't know what it should be but I think we may have found a possible culpret. Check with Benjamin Bentmann, he'd know what m3 is supposed to do -Stephen On 23 November 2010 14:30, Moser, Christian c...@metrohm.com wrote: They are from snapshot artifacts. We use non-unique snapshots in artifactory. The sources are deployed on the same time like the compiled artifacts. So the timestamp should be equals, shouldn't it? If not, how could I archieve it? -Chris -Ursprüngliche Nachricht- Von: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] Gesendet: Dienstag, 23. November 2010 14:39 An: Maven Users List Betreff: Re: Maven 3.0 doesn't download sources Are these sources of snapshots or releases? If snapshots it may be that the sources were deployed with a different timestamp, in which case the maven metadata my not be letting maven 3 find the artifacts. IIRC Maven 3 pays more attention to the metadata, whereas Maven 2 might not trust it as much (but I could be wrong, my recollection is fuzzy) -Stephen On 23 November 2010 12:13, Moser, Christian c...@metrohm.com wrote: I'm unable to download artifact sources with maven 3.0 and 3.0.1-RC1 with following command. Sources classifier is: -sources (default) mvn -U validate dependency:sources -DoverWriteSnapshots=true -DoverWriteReleases=true the artifacts with classifier -sources are available in the locale remote-repository manager (artifactory). Is there another call to force maven to download sources? Greez Chris - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - 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 -- Yoav
Need help with a dependency problem...
Hello, Due to a restructuring in a maven project, I am experiencing problems with the following POM. I have two classes in the maven project below: com.jeanbaptistemartin.annotations.MethodLevelAnnotation (an annotation) com.jeanbaptistemartin.annotations.TestAnnotationsProcessor (my annotation processor) Here is what I get when I do a build: *Compiling 2 source files to /home/julien/NetBeansProjects/jbm-annotation-processor/target/classes [ERROR]BUILD FAILURE Compilation failure error: Annotation processor 'com.jeanbaptistemartin.annotations.TestAnnotationsProcessor' not found * Can anyone please help? Thanks in advance, J. ?xml version=1.0 encoding=UTF-8? projectxmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdcom.jeanbaptistemartin/groupId artifactIdjbm-annotation-processor/artifactId packagingjar/packaging version1.0/version namejbm-annotation-processor/name urlhttp://maven.apache.org/url dependencies dependency groupIdjunit/groupId artifactIdjunit/artifactId version4.8.2/version scopetest/scope /dependency /dependencies build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId configuration source1.6/source target1.6/target compilerArguments processorcom.jeanbaptistemartin.annotations.TestAnnotationsProcessor/processor /compilerArguments /configuration /plugin /plugins /build /project
Re: Maven 3.0 doesn't update snapshot artifacts
We witnessed the same issue here at work. While the latest Maven 2 works properly, our developpers using Maven 3 had the problem and had to go through the same procedure of deleting the jar within the local repo. We, on the other hand, use archiva for our artifact deployement. It is a major blocker for our dev team to upgrade to M3. I don't know the culprit and I have not tried using the uniqueVersion toggle to timestamp the snapshot, since I need to discuss this change with our CM's. -Patrick On Tue, Nov 23, 2010 at 9:43 AM, Moser, Christian c...@metrohm.com wrote: I'm unable to download the newest artifacts (compiled jar) with maven 3.0 and 3.0.1-RC1 from cmd line. The artifacts were deployed to artifactory 2.3.1. After calling mvn -U on a dependend artifact, maven just updates the metadata, but doesn't override the old artifacts contained in the local repository. I have to delete the local repository to receive the newest artifacts from remote after calling mvn -U. the artifacts are all snapshots version. Is there another, new way to force update snapshots? -Chris - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: Maven 3.0 doesn't download sources
At the moment I have no idea which tool is causing the problem. I still have problems with artifactory 2.3.1. Just a quick question: Does artifactory 2.3.0+ supports the m3 format with both, unique and non-unique repositories? Currently the build system is running with 2.3.1 and non-unique snapshot repositories deployed with maven 3.0 and it still doesn't download artifact-sources neither it's downloading newer artifactory-snapshots deployed on the artifactory if build is called with maven -U. - Chris -Ursprüngliche Nachricht- Von: Yoav Landman [mailto:yland...@gmail.com] Gesendet: Donnerstag, 25. November 2010 20:44 An: Maven Users List Betreff: Re: Maven 3.0 doesn't download sources Hi, Artifactory 2.3.0+ supports the m3 format for maven-metadata.xml for snapshot artifacts. But, if you upgraded to 2.3.x and still think there is something wrong on the Artifactory side, better ask on the Artifactory user list and we'll be happy to assist you there. Thanks, On Wed, Nov 24, 2010 at 8:34 AM, Moser, Christian c...@metrohm.com wrote: I could imagine the culprit could be artifactory. We were forced to update from 2.2.2 to 2.2.3, otherwise we weren't be able to deploy with maven 3.0 (metadata issue in Artifactory 2.2.2, deploy worked only in legacy mode). In the meantime just to be sure, we updated to 2.3.1. But were also required to change all our repositories to handle non-unique snapshots and to deploy every snapshot again. It was necessary to use non-unique snapshots in artifactory because maven was overriding newer locally installed artifacts, with older remote artifacts everytime we tried to install a new artifact. But regarding my two maven user list entries (Maven 3.0 doesn't download sources / Maven 3.0 doesn't update snapshot artifacts) it seems there are some metadata issues with artifactory maven 3.0. So, the right way to go with maven 3.0 is to use repositories with unique (timestamped) snapshots artifacts? But this won't work with artifactory at least not with version 2.2.3. -thx Chris -Ursprüngliche Nachricht- Von: Brett Porter [mailto:br...@porterclan.net] Im Auftrag von Brett Porter Gesendet: Dienstag, 23. November 2010 23:14 An: Maven Users List Betreff: Re: Maven 3.0 doesn't download sources There's a couple of potential things in the way you've described it: - Maven 3.0 does not support non-unique snapshots - you would need to use timestamps and rely on the repo manager to purge old versions - if I've misunderstood the above, the difference on timestamps is that Maven 3.0 will actually store separate metadata per classifier. They should be the same in the scenario you describe, but maybe Artifactory doesn't support the new metadata format and affects it in some way. HTH, Brett On 24/11/2010, at 3:21 AM, Stephen Connolly wrote: Don't know what it should be but I think we may have found a possible culpret. Check with Benjamin Bentmann, he'd know what m3 is supposed to do -Stephen On 23 November 2010 14:30, Moser, Christian c...@metrohm.com wrote: They are from snapshot artifacts. We use non-unique snapshots in artifactory. The sources are deployed on the same time like the compiled artifacts. So the timestamp should be equals, shouldn't it? If not, how could I archieve it? -Chris -Ursprüngliche Nachricht- Von: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] Gesendet: Dienstag, 23. November 2010 14:39 An: Maven Users List Betreff: Re: Maven 3.0 doesn't download sources Are these sources of snapshots or releases? If snapshots it may be that the sources were deployed with a different timestamp, in which case the maven metadata my not be letting maven 3 find the artifacts. IIRC Maven 3 pays more attention to the metadata, whereas Maven 2 might not trust it as much (but I could be wrong, my recollection is fuzzy) -Stephen On 23 November 2010 12:13, Moser, Christian c...@metrohm.com wrote: I'm unable to download artifact sources with maven 3.0 and 3.0.1-RC1 with following command. Sources classifier is: -sources (default) mvn -U validate dependency:sources -DoverWriteSnapshots=true -DoverWriteReleases=true the artifacts with classifier -sources are available in the locale remote-repository manager (artifactory). Is there another call to force maven to download sources? Greez Chris - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
