in svn it'd be easy, but in cvs it'd be quite difficult, the 'newest' file may be a 1.2 revision,
mixing a little development process and policies, one could ask to write the revision id of the pom.xml, since that file should change at least once on each release, and thus, would be a valid identifier for the 'build number', IMHO this is an acceptable thing to ask
On 1/31/06, Trygve Laugstøl <[EMAIL PROTECTED]> wrote:
On Sun, 2006-01-22 at 01:15 -0300, Miguel Griffa wrote:
> Hi all
> I was wondering if there would be any interest in hosting a build
> number plugin at mojo.
> For political reasons, I need this functionallity in a project, in
> this case read
> political = stupid + closed to discussion.
> Any ideas?
I'd like the scm plugin to be able to write the "revision id" to a
properties file or a Java file which we'll run when building test and
production artifacts.
Not sure now to handle SCMs without a change set notion like CVS, the
only real option that I can think of is to find the newest file in the
repository and use that file's date as the id.
--
Trygve
--
Miguel Griffa
Skype: miguel.griffa
Y!: m_griffa
MSN: [EMAIL PROTECTED]
Cell: 54-911-62519355
