Re: Preleminary Maven 3.4.0-SNAPSHOT Testing (Take 3)

Am 08/17/16 um 04:09 schrieb Mark Derricutt: > On 17 Aug 2016, at 12:32, Christian Schulte wrote: > >> There is an easy way to solve this. Maven validates the model version in >> the POM to match "4.0.0". Based on that version, Maven can decide how to >> behave. I am thinking about introducing

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing (Take 3)

On 17 Aug 2016, at 12:32, Christian Schulte wrote: > There is an easy way to solve this. Maven validates the model version in > the POM to match "4.0.0". Based on that version, Maven can decide how to > behave. I am thinking about introducing model version "4.1.0" in Maven > 3.4. All existing

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing (Take 3)

Am 08/16/16 um 23:14 schrieb Curtis Rueden: > properly with Maven 3.4.0. But I am very concerned about the precedent > here: at any point in the future, complex builds which used to work might > stop doing so, even without a major version increment, due to future > changes in the logic of core

checkstyle plugin and checking files outside of maven dirs

Hi. I'm using the checkstyle maven plugin to validate my source and resource files. That works so far. But now I encountered, that it won't check files outside of the standard maven dirs. E.g. it would be great if it could check the pom as well. Is this somehow possible? Also when it comes to

Re: Separate Integration & Unit Tests

submit me On Mon, Aug 15, 2016 at 8:17 AM, Jeff Jensen < jeffjen...@upstairstechnology.com> wrote: > On Mon, Aug 15, 2016 at 8:52 AM, Richard W. Adams wrote: > > > Can someone clarify how to separate unit & integration tests in the Maven > > standard directory layout? The

RE: Multiproject build that needs to build one project only if on a particular os?

> -Original Message- > From: Karl Heinz Marbaise [mailto:khmarba...@gmx.de] > Sent: Tuesday, August 16, 2016 12:59 PM > To: Maven Users List > Subject: Re: Multiproject build that needs to build one project only if > on a particular os? > > Hi, > > You should

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing (Take 3)

Hi Stephane, Apologies up front for my long reply here. I divided into sections to help break things up. *== Expected behavior? Or a defect? ==* > if you expect the parent to override something you've defined > in the child, that's not the expected behaviour at all. It certainly _has_ been

Re: Multiproject build that needs to build one project only if on a particular os?

Hi, activtion of modules via profile is a bad idea... http://blog.soebes.de/blog/2013/11/09/why-is-it-bad-to-activate-slash-deactive-modules-by-profiles-in-maven/ Kind regards Karl Heinz Marbaise On 16/08/16 21:54, Bernd Eckenfels wrote: This describes how to control modules with profiles and

Re: Multiproject build that needs to build one project only if on a particular os?

In addition, you can use the --pl option (requires Maven 3.2.1+) to exclude the child module of your choice. This example excludes child module "foo": mvn --pl !foo Cheers, Paul On Tue, Aug 16, 2016 at 2:54 PM, Bernd Eckenfels wrote: > This describes how to control

Re: Multiproject build that needs to build one project only if on a particular os?

Hi, You should take a look to profiles which might solve your problem... http://maven.apache.org/guides/introduction/introduction-to-profiles.html But you might can give an example what can not be built on Windows in particular in a Java project? Or do you make a OSGi build? Kind regards

Re: Multiproject build that needs to build one project only if on a particular os?

This describes how to control modules with profiles and how to activate profiles based on os family: http://books.sonatype.com/mvnref-book/reference/profiles-sect-activation.html Gruss Bernd Am Tue, 16 Aug 2016 19:47:38 + schrieb "KARR, DAVID" : > I have a multiproject

Multiproject build that needs to build one project only if on a particular os?

I have a multiproject build with three modules, not counting the top-level. I can build this on either Windows or Linux, but if I'm building on Windows, one of the subprojects should not be built. I vaguely remember seeing ways to set architecture properties and check for those, but I can't

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing (Take 3)

Hello Curtis, I have no opinion on your project (To be honest, I haven't looked in details yet, quite a large setup) but if you expect the parent to override something you've defined in the child, that's not the expected behaviour at all. That's still a problem for you though, I am not denying