maven compiler plugin + toolchains

2015-04-22 Thread intel radoux
Hello, I wish to set something like this in my parent pom : plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId version3.3/version configuration source1.6/source

Re: maven compiler plugin + toolchains

2015-04-22 Thread Ron Wheeler
Would setting a property ( java_compliance_version1.6 /java_compliance_version) in your parent and using the property as the value (source$java_compliance_version/source )in the source, work? Ron On 22/04/2015 2:42 PM, intel radoux wrote: Hello, I wish to set something like this in my

Issue with maven-release-plugin and maven 3.3.1

2015-04-22 Thread cody.a.fyler
It appears as though the maven-release-plugin needs to be updated for Maven 3.3.1 (similar to the maven-invoker-plugin)? I get this error trying a dry run: [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.5.1:prepare (default-cli) on project parent: Failed

[ANN] Apache Maven Release Plugin 2.5.2 Released

2015-04-22 Thread Robert Scholte
The Apache Maven team is pleased to announce the release of the Apache Maven Release Plugin, version 2.5.2 This plugin is used to release a project with Maven, saving a lot of repetitive, manual work. Releasing a project is made in two steps: prepare and perform.

Running ALL tests in a multi-module , then failing the entire build.

2015-04-22 Thread Kevin Burton
For our continuous integration setup, I want each module to run tests, and continue even if the tests failed. This way I can see the list of ALL test failures , across all modules, then fix them all at once. My understanding , is that I can enable this, but then the result of the run is a

Re: Running ALL tests in a multi-module , then failing the entire build.

2015-04-22 Thread Mark Derricutt
On 23 Apr 2015, at 17:12, Kevin Burton wrote: My understanding , is that I can enable this, but then the result of the run is a successful build? Is that true? what’s the easiest way to set this up? You could use: mvn --fail-at-end which will run all modules regardless of if any fail,

Re: Issue with maven-release-plugin and maven 3.3.1

2015-04-22 Thread Karl Heinz Marbaise
Hi, a short solution could be https://issues.apache.org/jira/browse/MRELEASE-902 after the new release of maven-release-plugin 2.5.2 is there you could change to the new release which contains a fix for that... Kind regards Karl Heinz Marbaise On 4/22/15 10:02 PM,

RE: Issue with maven-release-plugin and maven 3.3.1

2015-04-22 Thread cody.a.fyler
That works for me. Thanks! Cody Fyler Lending Grid Build Team G=Lending Grid Builds (515) – 441 - 0814 -Original Message- From: Karl Heinz Marbaise [mailto:khmarba...@gmx.de] Sent: Wednesday, April 22, 2015 3:11 PM To: Maven Users List Subject: Re: Issue with maven-release-plugin and

Re: Maven + Jenkins not packaging war with jars

2015-04-22 Thread Stephen Connolly
http://javaadventure.blogspot.ie/2013/11/jenkins-maven-job-type-considered-evil.html On 21 April 2015 at 17:12, Gandikota, Murthy mgandik...@westechmed.com wrote: Hi All Using Jenkins 1.596, the jar files are not included in the WAR by maven which is given the following goals: clean