> -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
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
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
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
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
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