Jeff,

Thanks for the response, I think this will work!  Just one thing, however.

I couldn't get it to work like you said with ${pom.setCurrentVersion(version)}

I had to do the following:

        <j:set property="currentVersion"
               target="${pom}"
               value="${anthill.version}"
               defaultValue="SNAPSHOT"
               />

Maybe there is an easier way, but I couldn't figure it out...

Also, I don't understand what you meant in step 2 by "constructed new artifact names". Why is this necessary?

Thanks again!
-- Chad

"Jefferson K. French" <[EMAIL PROTECTED]> wrote:

Hi Chad. What I did was add a custom goal uses the version number passed in my Anthill, since that is what Anthill uses when tagging the source code. In particular I:

1. Defined my project's version as SNAPSHOT in project.xml
2. Constructed new artifact names using the 'version' property passed
   in by Anthill
3. Attained xxx:deploy
4. Changed the version number: ${pom.setCurrentVersion(version)}
5. Used <artifact:deploy> to deploy using the new version number

So in our company repo we end up with a project-1.2.3.jar and a
project-SNAPSHOT.jar, for example.

On Fri, 03 Sep 2004, at 16:22:17 [GMT -0700] Chad Woolley wrote:


Hi,


We are setting up Maven with our Continous Integration process (Anthill Pro), to manage several dependent projects, and want to use SNAPSHOT dependencies.


I understand how snapshot dependencies work, and convert-snapshots, but I have some questions/concerns.


We want to be able to tag the version of the snapshot, so the corresponding source can be checked out at a later date.


However, AnthillPro must know the string to tag with before it invokes a build.


I could run two subsequent goals, and maybe trick anthill into using the generated timestamp to tag the project. Unfortunately, I don't know how to obtain a handle on the generated snapshot timestamp in an automated way.


Has anyone else resolved this problem? Am I approaching it the wrong way?


Thanks,
Chad



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



Reply via email to