Passing config parameters to a plugin goal on the command line

Hi, We have a Maven plugin that previously was using the Maven Javadoc-style annotations. When we wanted to test out something quick and dirty, we were able to invoke the plugin goals from the command-line and pass in the configuration parameters using -Dparam=value like this: mvn

Re: Passing config parameters to a plugin goal on the command line

As you found out and explained on the dev list, it does work if you apply the correct annotation parameters in your plugin code. /Anders On Fri, Sep 20, 2013 at 6:44 AM, Robert Patrick robert.patr...@oracle.comwrote: Hi, We have a Maven plugin that previously was using the Maven

Re: dependency:tree gets wrong version?

Hi James, James Green wrote: Gotta be a simple one this! Upgraded ourselves to apache-cxf-2.7.6 and we've been getting errors since. Well-publicised solution is to find and remove any dependencies on woodstox prior to 4.2.0. So dependency:tree only shows us having 4.2.0. Yet clean

Release Plugin doesn't commit poms correctly anymore

Hi folks, I have used the release plugin fro a millions of releases. And suddenly it stopped working as expected. I am doing: $ mvn release:prepare $ mvn release:perform And usually I see commits of the kind: [maven-release-plugin] prepare release v3.2.2 When i did an minor upgrade today, I

Re: Release Plugin doesn't commit poms correctly anymore

Am 20.09.2013 10:10, schrieb Christian Grobmeier: Hi folks, I have used the release plugin fro a millions of releases. And suddenly it stopped working as expected. I am doing: $ mvn release:prepare $ mvn release:perform And usually I see commits of the kind: [maven-release-plugin] prepare

Re: Release Plugin doesn't commit poms correctly anymore

Am 20.09.2013 10:46, schrieb Tim Kettler: Am 20.09.2013 10:10, schrieb Christian Grobmeier: Hi folks, I have used the release plugin fro a millions of releases. And suddenly it stopped working as expected. I am doing: $ mvn release:prepare $ mvn release:perform And usually I see commits of

Re: Release Plugin doesn't commit poms correctly anymore

Thanks a lot Tim. v2.4.1 works well for me. For the record: with my reinstallation of MacPort I upgraded GIT to 1.8.4. With that in mind it makes sense why it suddenly stopped. Cheers Tim Kettler schrieb: Am 20.09.2013 10:46, schrieb Tim Kettler: Am 20.09.2013 10:10, schrieb Christian

Re: dependency:tree gets wrong version?

org.apache.maven.plugins:maven-dependency-plugin:2.8 The only way we resolved our problem was by loading the project into Eclipse and viewing the graph of dependencies, then dropping each that had a transitive dependency on the older woodstox. Eventually jaxws-rt was dropped and the woodstox

Creating a Camel Project with customized POM

Hi all, I created a camel project with camel-archetype-spring archetype to deploy in ServiceMix 4.4.2. But the versions of all the dependencies in POM are above that of ServiceMix. Example - ServiceMix camel-core version is 2.8.5 whereas the camel-core version in POM is 2.12.0. So I want to

Re: Creating a Camel Project with customized POM

Sounds like you'd want to ask the camel people about this. This list is for generic Maven questions. /Anders On Fri, Sep 20, 2013 at 2:46 PM, madusanka madusankabalasoor...@gmail.comwrote: Hi all, I created a camel project with camel-archetype-spring archetype to deploy in ServiceMix

RE: Creating a Camel Project with customized POM

sounds as if your hierarchy went fubar take a look at this hierarchy for camel-archetype-spring V2.8.3 groupIdorg.apache.camel/groupId artifactIdcamel/artifactId version2.8.3/version packagingpom/packaging || V parent groupIdorg.apache.camel/groupId

Re: dependency:tree gets wrong version?

Hi James, James Green wrote: org.apache.maven.plugins:maven-dependency-plugin:2.8 The only way we resolved our problem was by loading the project into Eclipse and viewing the graph of dependencies, then dropping each that had a transitive dependency on the older woodstox. Eventually