On Apr 2, 2010, at 5:39 PM, Scott Susslin wrote:
> We're working in Agile, and QA needs to know what version number their
> working against. Since they're QAing about every day, I'd like to have them
> know exactly which version they're hitting without forcing the developers to
> change the version number manually every day. We'd only be using this number
> below the major.minor in our version, and only for SNAPSHOTs, so I don't see
> the harm in using it for that. A release build will be an agreed-up, solid
> number.
>
> When I tried it, the output from "install" looked like the following:
>
> [INFO] Installing PROJECT/artifact-0.1.334-SNAPSHOT.swc to
> ~.m2/repository/PROJECT/artifact/0.1.${buildNumber}-SNAPSHOT/artifact-0.1.${buildNumber}-SNAPSHOT.swc
>
> Obviously, ${buildNumber} shoulda been "334"
>
>
>
> ----- Original Message ----
> From: Wendy Smoak <[email protected]>
> To: Maven Users List <[email protected]>
> Sent: Fri, April 2, 2010 2:17:08 PM
> Subject: Re: Using variables in POM's version field
>
> On Fri, Apr 2, 2010 at 5:14 PM, Scott Susslin <[email protected]> wrote:
>
>> Why?
>>
>> Also, is it possible?
>
> What happened when you tried it?
>
> What are you trying to accomplish? Snapshots are already timestamped
> with a build number...
As Wendy said, snapshots are already timestamped. You seem to be doing
something dangerous like not using a real repository manager such as
Artifactory or Nexus. (I prefer Nexus, having used both.)
If you are using NFS to share your .m2/repository directory you are in for
trouble.
-K
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
