To: dev@maven.apache.org
Subject: Re: More hard problems...
Date: Tue, 26 Nov 2013 22:57:45 +0100
From: e...@zusammenkunft.net
Am 26.11.2013, 22:02 Uhr, schrieb Robert Scholte rfscho...@apache.org:
In addition to this story: There's an open issue called MDEPLOY-118
which
In addition to this story: There's an open issue called MDEPLOY-118 which
describes a related issue: how to release the same version for different
platforms?
The platforms as described here look more like a new kind of profiles:
platform as activation.
In this case I'm not so sure if the
On Tuesday, 26 November 2013, Robert Scholte wrote:
In addition to this story: There's an open issue called MDEPLOY-118 which
describes a related issue: how to release the same version for different
platforms?
The platforms as described here look more like a new kind of profiles:
platform
Am 26.11.2013, 22:02 Uhr, schrieb Robert Scholte rfscho...@apache.org:
In addition to this story: There's an open issue called MDEPLOY-118
which describes a related issue: how to release the same version for
different platforms?
Related there is also the need for features. Larger projects
In addition to the modelVersion evolution problem, there are some other
issues that I think we need to address for Maven 4.0+
* Platform specific builds
* Architecture specific builds
* Native build flavours (e.g. debug vs non-debug)
You could see this as the side-artifact dilemma.
Here are
