dsay
> -Original Message-
> From: Ron Wheeler [mailto:rwhee...@artifact-software.com]
> Sent: Tuesday, 18 January 2011 3:38 a.m.
> To: users@maven.apache.org
> Subject: Re: Distinguishing artifacts created on branches
>
> Using the branch id in the version number will
Using the branch id in the version number will make it easier to
understand the relation between the source and the binary that it makes.
If you every want to know how developer X actually got the test to work
last month, it will be nice to be able to use the dependencies from his
project to fin
Using a classifier MAY be appropriate for this use case.
On Jan 17, 2011 8:57 AM, "Lóránt Pintér" wrote:
> Hi,
>
> I want to deploy alternate artifacts from my branches so that other
> developers can depend on them. Say, I have a product called
>
> com.mycompany.tool
> tool
> 5.2-SNAPSHOT
>
> Now,
2011/1/17 Lóránt Pintér :
> Now, I'd like to create a branch of this one where I add a new feature. And
> this early adopter developer here wants to already build on my new feature,
> even before I merge it back to trunk, so I deploy my artifacts to Nexus.
> Now, I obviously can't deploy them under
Hi,
I want to deploy alternate artifacts from my branches so that other
developers can depend on them. Say, I have a product called
com.mycompany.tool
tool
5.2-SNAPSHOT
Now, I'd like to create a branch of this one where I add a new feature. And
this early adopter developer here wants to already
