RE: IT test in src/test/java is not executed by failsafe:integration-test, or fails oddly with verify

> -Original Message- > From: KARR, DAVID > Sent: Wednesday, October 25, 2017 10:56 AM > To: users@maven.apache.org > Subject: IT test in src/test/java is not executed by > failsafe:integration-test, or fails oddly with verify > > I work on a large multiproject build that mostly produces

RE: IT test in src/test/java is not executed by failsafe:integration-test, or fails oddly with verify

> -Original Message- > From: Robert Patrick [mailto:robert.patr...@oracle.com] > Sent: Wednesday, October 25, 2017 11:32 AM > To: Maven Users List > Subject: RE: IT test in src/test/java is not executed by > failsafe:integration-test, or fails oddly with verify >

RE: IT test in src/test/java is not executed by failsafe:integration-test, or fails oddly with verify

In our integration tests' parent POM, we configured the compiler plugin to run the test-compile goal: org.apache.maven.plugins maven-compiler-plugin test-compile

IT test in src/test/java is not executed by failsafe:integration-test, or fails oddly with verify

I work on a large multiproject build that mostly produces OSGi bundle artifacts. The codebase has a lot of unit tests that work fine from the build. We also have quite a few IT tests, but we only execute those from Eclipse, as the nature of the framework makes those tests unreliable. I now

Re: how to use both buildnumber-maven-plugin and maven-release-plugin

Doh! I misinterpreted the docs and was thinking that the flatten-maven-plugin was something only needed for multi-module projects… Thanks for clearing that up. Steve C > On 25 Oct 2017, at 7:46 pm, Karl Heinz Marbaise wrote: > > Hi, > > On 25/10/17 08:50, Stephen Coy

Re: how to use both buildnumber-maven-plugin and maven-release-plugin

Hi, On 25/10/17 08:50, Stephen Coy wrote: Hi Pascal, Unfortunately this method results in pom files being deployed with releases that do not have corresponding versions in them. In fact, the version is literally: ${revision} This results in build warnings for consumers of the

[ANN] Apache Maven 3.5.2 Released

The Apache Maven team is pleased to announce the release of the Apache Maven 3.5.2 You can download the appropriate sources etc. from the download page Contributors The Apache Maven team would like to thank the following contributors, without whom this release would not have been

Re: how to use both buildnumber-maven-plugin and maven-release-plugin

Hi Pascal, Unfortunately this method results in pom files being deployed with releases that do not have corresponding versions in them. In fact, the version is literally: ${revision} This results in build warnings for consumers of the released artifact. Cheers, Steve C > On 24 Oct