Dear Maven users,
I improved the version.override feature so that the whole maven build life
cycle is now properly supported:
With
*mvn clean deploy -Dversion.override*
a build with an unique version is created without committing anything to
your version control or making your workspace dirty.
- when speaking about SNAPSHOTs we should distinguish between
dependencies and what we produce. With a build we produce an artifact which
is either a SNAPSHOT or release according to the version in the pom.xml. A
dependency resolves either to a SNAPSHOT or a released version of another
library.
Hello,
if interested: the topic of lightweight maven releases is discussed in
DevOps for Developers, Apress, Chapter 8.
Cheers,
Michael
Hello there,
I. find prepare and perform quite heavyweight my self. After prepare did
build everything successfully, it throws away everything, just
maven-releases, or an alternative to the
maven-release-plugin
Hi all
Maybe somebody is interested in how a release could be built in a more
lightweight and safe way than with the maven-release-plugin. Especially
recommended for nightly releases.
It's not yet released, but basically fully
On 30 Apr 2013, at 11:21 PM, Roger Brechbühl rotscher...@gmail.com wrote:
Maybe somebody is interested in how a release could be built in a more
lightweight and safe way than with the maven-release-plugin. Especially
recommended for nightly releases.
It's not yet released, but basically
Graham, well said.
Although the pom.xml is the easiest way to discover the version, it is not
the best location, since it would require a commit.
The solution must be found in a generated file which will be added to the
artifact during packaging. Here you could add a timestamp or revision.
Hello there,
I. find prepare and perform quite heavyweight my self. After prepare did
build everything successfully, it throws away everything, just tags the
source and starts over again during perform.
prepare already checks with scm means, that there are no modifications and
in my experience
Hi all
Maybe somebody is interested in how a release could be built in a more
lightweight and safe way than with the maven-release-plugin. Especially
recommended for nightly releases.
It's not yet released, but basically fully working:
*mvn clean install -Dversion.override=1.2.3-S-5*
kind of formats are supported? jar, war etc.
Thanks
nambi
-Original Message-
From: Roger Brechbühl [mailto:rotscher...@gmail.com]
Sent: Tuesday, April 30, 2013 2:22 PM
To: users@maven.apache.org
Subject: Lightweight maven-releases, or an alternative to the
maven-release-plugin
Hi all
all. Josef
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-releases-using-Git-tp5744976p5745077.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users
Hi,
It is expected behaviour.
A release is actually like storing the state of your code for a precise
event (often represented with a version).
Maybe what you (also?) want is the release:branch goal.
Cheers
Le 29 janv. 2013 18:35, Jeff predato...@gmail.com a écrit :
I've got my first GIT
and what is the proper maven command?
there are so many maven goals, and its
hard to know em all. Josef
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-releases-using-Git-tp5744976p5745077.html
Sent from the Maven - Users mailing list archive at Nabble.com
Hi,
I am using maven for web application development. As it is in development
phase it is versioned as app-1.0-SNAPSHOT. But, application starts in
couple of weeks, I was wondering what should be the best practise for
release during tests. I believe only when it is tested and can go to
production,
release during tests. I believe only when it is tested and can go to
production, then it is versioned to app-1.0. But, during testing how do we
manage its versions?
Just push a version out and call it 1.0-alpha-1 or -beta-1 or
whatever. And test that version until you're happy with it. Keep
What is the standard guidelines or procedures for working with
multiple development streams (ie, trunk, product_test,
bugfix_on_version_x) and using the release plugin?
For streams that are moving through the testing process, do you create
the product_test branch and when that is complete do the
When is the next maven released scheduled? It is 7 months since the last
maven 2 release.
Thanks,
-Moiz
On 11/6/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
When is the next maven released scheduled? It is 7 months since the last
maven 2 release.
Is there a particular fix you're looking for? Most of what makes
Maven work is in the plugins, and several of those have seen releases
in the time
--
Wendy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/Maven-releases--tf2580806s177.html#a7194461
Sent from
://www.nabble.com/Notification-about-new-Maven-releases-tf1890145.html#a5168026
Sent from the Maven - Users forum at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED
19 matches
Mail list logo
