I'm in this same position, and have been for a year now. Unless someone can
correct me, I think I'm stuck in a position that I can't use the release
plugin (as much as I love to use it when I can).

1) On this project, the client already has lots of pom files.

2) Sadly, they are so tightly coupled, they really DO have to have the same
version number on every module.  This code is (bad) more tightly coupled
then Tom Cruise and Katie Holmes.  I will try to make it more loosely
coupled as I continue to consult on the project and gain respect.  But
that's a thread for another day.

3) Sometimes we need to rev versions on a branch.  Thus the release plugin
doesn't help because it seems destined to a workflow of
SNAPSHOT->RELEASENUMBERONBRANCH->SNAPSHOT.  What we need is a direct
RELEASENUMBER->NEXTRELEASENUMBER.

4) Sadly, with the ClearCase Remote Client SCM system (yes, it doesn't have
a command line interface Virginia), we can't integrate with the SCM plugins
that Maven offers.  Big sigh...

So, what I'm asking if anyone knows about is:
1) A plugin/means other than a perl script to increment from RELEASEVERSION
to NEXTRELEASEVERSION (e.g. 4.0.1 to 4.0.2) on local files without SCM
plugins getting involved.  I can then use the CCRC GUI to check in the
modified files manually.

-Matthew McCullough
[EMAIL PROTECTED]


Graham Leggett wrote:
> 
> Michael McCallum wrote:
> 
>> so tell management to keep out of the code
> 
> I fix problem projects for a living, and one thing I have learned, over 
> and over again, is that management don't keep out of the code.
> 
> Leading a project to the light is about 10% technology, and 90% 
> diplomacy, and when your tools don't help with the diplomacy part, you 
> are doomed to fail.
> 
> Regards,
> Graham
> --
> 
>  
> 

-- 
View this message in context: 
http://www.nabble.com/Defining-version-in-single-location--tp14275006s177p14299727.html
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to