Maintaining versions in a multi-module project

I am working on a multi-module project where I see that some of the module POMs have versions different from the parent POM. Apparently, developers have made changes to some of the modules and updated the version of only those modules. I also see another project where irrespective of which

Re: Maintaining versions in a multi-module project

Use whatever works best for you. I have some projects where it is better for me to force them all in lock-step I have other projects where I let them run free. My general rule of thumb: if the modules are in the same GIT repo or the same Subversion trunk then they all will end up being released

m-remote-resources-p mvn 3.2.1 vs mvn 3.2.3

m-remote-resources-p:process has serious bug with excludeTransitive option: * with maven 3.2.1 excludeTransitive=false, my build completes in about 10 seconds * with maven 3.2.3 excludeTransitive=false, my build dies with OOME after about 2 minutes * with maven 3.2.3 excludeTransitive=true, my

maven-surefire-plugin does not fail build if TestNG and JUnit47 are used

I have a module where maven-surefire-plugin (2.10) is configured to use TestNG and JUnit47. The former has several tests that all succeed and the later has two tests that fail. However the build succeeds. How can I configure surefire so the build fails if either have failures which is the

jarsigner plugin: specifying multiple arguments on the CLI

Apologies if this has been answered before. I don't see an entry in the plugin page's FAQ and find it with a quick Google search. I am behind a proxy so in order to specify a TSA I need to use -J-Dhttp.proxyHost=host -J-Dhttp.proxyPort=port as arguments. If I use -Djarsigner.arguments=... then

[ANN] Apache Maven RAR Plugin Version 2.4 Released

The Apache Maven team is pleased to announce the release of the Apache Maven RAR Plugin, Version 2.4 A resource adapter is a system-level software driver that a Java application uses to connect to an enterprise information system (EIS). The RAR plugin has the capability to store these resource

Tell maven to not have the parent pom as a dependency?

I have an OSS module in a multi-module maven project. I want to post this to a public repo… it’s open source. The problem is that the parent module is not OSS. When I setup a dependency it pulls in my OSS module just fine, but then it tries to pull down the parent module, which isn’t in the

Re: Tell maven to not have the parent pom as a dependency?

Move it out as a stand alone project. -D On Thu, Sep 11, 2014 at 8:25 PM, Kevin Burton bur...@spinn3r.com wrote: I have an OSS module in a multi-module maven project. I want to post this to a public repo… it’s open source. The problem is that the parent module is not OSS. When I setup a

Re: Maintaining versions in a multi-module project

I use the maven versions plugin for this… I just run: mvn versions:set -DnewVersion=0.0.3 mvn versions:commit and all my pom.s are updated. On Thu, Sep 11, 2014 at 6:02 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Use whatever works best for you. I have some projects

Re: Tell maven to not have the parent pom as a dependency?

On 12 September 2014 12:55, Kevin Burton bur...@spinn3r.com wrote: I have an OSS module in a multi-module maven project. I want to post this to a public repo… it’s open source. The problem is that the parent module is not OSS. When I setup a dependency it pulls in my OSS module just fine,