Hi Todd,
The more I think about the problem, the more I believe I should
negotiate a way to straighten the release process of the project,
instead of warping Maven configuration.
Thank you for your answer.
Cheers,
Henrique
Todd Thiessen wrote:
You could change the POM to point to an SCM you do have access to and
cut a real release.
---
Todd Thiessen
-----Original Message-----
From: Henrique Prange [mailto:[email protected]]
Sent: Monday, March 09, 2009 2:55 PM
To: Maven Users List
Subject: Re: Deploying "Fake" Releases
Hi Kalle,
This is valid if I can't found another solution.
I want to have daily builds of this project producing
SNAPSHOT versions.
However, I don't want to store every SNAPSHOT produced. That
is why I want to make those "fake" releases monthly or
weekly. I want to store only "fake" releases indefinitely.
Anyway, thanks for your idea.
Cheers,
Henrique
Kalle Korhonen wrote:
Why not use just uniquely versioned snapshots in that case? Even in
other poms you can refer to unique snapshot version of a
dependency if
you so wish.
Kalle
On Mon, Mar 9, 2009 at 7:10 AM, Henrique Prange
<[email protected]> wrote:
Hello there,
Is there a way to deploy "fake" releases of a project into
a repository?
I need to make releases based on the SCM revision periodically.
Something like "my-project-1.0-rXXXX". But I can't make
real releases
because I don't have privilege to write to the SCM.
I tried the buildnumber-maven-plugin, which works for the binary
artifacts produced. But it doesn't work for parent pom artifacts.
This is a problem in a multi-project because an artifact
my-project-1.0-rXXXX will depend on a parent pom
my-parent-1.0-SNAPSHOT instead of my-parent-1.0-rXXXX.
I also took a look at the release:stage goal, but it
doesn't seem to
solve my problem.
I appreciate any advice on this subject.
Cheers,
Henrique
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
