On Apr 17, 2014, at 10:24 AM, Benson Margulies wrote:
> I'd like to arrange a system in which the automated builds stamp out
> releases (in the Maven sense),
In my case there is nothing to stamp out, every build is releasable. I deploy
sources and everything else required and have mechanisms t
My solution was to extend the DefaultModelReader where the version is
overridden when a specific system property is set.
There are different possibilities how the version is generated, based on
${project.version} or given from external.
This means, the version in the pom.xml is still a SNAPSHOT ve
I'd like to arrange a system in which the automated builds stamp out
releases (in the Maven sense), but that developers can use the usual
IDE and command-line builds when just building on their particular
machine at some particular instant. So I'd like to spare developers
from 'passing in the versi
For the continuous delivery friendly versions I saw an issue in JIRA as well
that tried to use snapshots.
The version is always a release version, not a snapshot. Snapshots are
definitively not CD friendly. In the system I'm working on that currently uses
this feature it is always a Perforce c
I've been thinking about how to exploit the 3.2.1 feature of
${something}
My idea is that an ordinary developer would end up with 'something'
defined to be a good, old, -SNAPSHOT, while various automated builds
would define it based on git commits.
Is is intended that a POM could declare
