:-) we tag our repo with "branchname!RP-BL-mavenlabel" to help in location. Rp
is for release prepare and bl is for baseline (carryover from clearcase
terminology)
Just remember that in git a hash doesn't belong to a branch, it is simply
attached to a linked list of hashes. A "branch" is simply a tag pointing to a
hash being designated as a "head". You can just as easily use the tag created
by the release plugin to checkout, and then make some bugfix branch from that
location.
Sent from my Blackberry.
----- Original Message -----
From: Seth Call <sethc...@gmail.com>
To: users@maven.apache.org <users@maven.apache.org>
Sent: Tue Mar 06 22:01:07 2012
Subject: Is it possible to tie current git branch to project version?
Hi there,
I've seen indication when searching the internet that it isn't possible to
put variables in <version> of a project (unless those variables are
hardcoded <properties> or provided at the command line), but I thought I'd
ask the list ...
Say there was a plugin that would invoke 'git branch' to determine the
current branch, and to then make that available to the project as a
variable; call it ${branch}. I'd like to use this variable then in the
version tag:
<project>
<groupId>blah</groupId>
<artifactId>blah</artifactId>
<version>${branch}-SNAPSHOT</version>
</project>
The reason I want to do this is that I'm realizing, for our internal-only
code projects, that a branch is always synonymous with a version of a
project, and ideally the act of being of switching branches would be all it
takes to switch your maven project's version.
Is this possible if I were to make a maven plugin?
Thanks!
Seth
--
View this message in context:
http://maven.40175.n5.nabble.com/Is-it-possible-to-tie-current-git-branch-to-project-version-tp5543110p5543110.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
