How to Release Snapshot artifacts in 1.2.2

[SoumenTrivedi]

Hi all,
I am using Archiva ver 1.2.2 & Maven for development and have the following
queries:

1. How to move SNAPSHOT artifacts to RELEASE stage in Archiva
2. The SNAPSHOT jars is project specific and not upon apache, should it
still be staged on the
http://people.apache.org/repo/m2-snapshot-repository/website?
3. What steps should be followed to stage the release? I have a Application
Server on which Archiva runs and want to stage the releases in the same
server along with the /data/repositories directory? Can this be possible?

Any answers or pointers to the above queries will be very helpful.

Please feel free to ask questions to me if you feel what I described above
does not make any sense to you? I am new to Archiva and trying to understand
& implement the process involved Archiva administration and release
activity.

--
Thanks & Regards,
Soumen Trivedi
Email: Soumen.Trivedi@...

[Wendy Smoak-3]

On Mon, Sep 14, 2009 at 11:04 AM, Soumen Trivedi
<soumen.trivedi@...> wrote:

> 1. How to move SNAPSHOT artifacts to RELEASE stage in Archiva

That you have SNAPSHOT artifacts in the repository implies that you're
using Maven to build your project.

If so, you can use the Maven Release plugin to automate the process of
creating a tag and building a released version of your project.

I'm not sure what you meant in (2) about project specific jars and the
website, can you re-state the question?

> 3. What steps should be followed to stage the release? I have a Application
> Server on which Archiva runs and want to stage the releases in the same
> server along with the /data/repositories directory? Can this be possible?

It sounds like you want to deploy your released application.  There's
nothing in Archiva to help with that, but there are other ways to
automate it.  If you are using Maven there might be a plugin for your
app server, or you might take a look at the Cargo project.

--
Wendy

[SoumenTrivedi]

Thanks for replying back Wendy. Yes I want to release application specific
contents into Archiva as RELEASE and not as SNAPSHOT before it is actually
sent to production env. Do you reckon using Maven for this purpose? I
apologies for this question, I was thinking that we upload artifacts into
Archiva as SNAPSHOT and then Archiva helps to move those into RELEASE stage.



On Mon, Sep 14, 2009 at 7:55 PM, Wendy Smoak <wsmoak@...> wrote:

> On Mon, Sep 14, 2009 at 11:04 AM, Soumen Trivedi
> <soumen.trivedi@...> wrote:
>
> > 1. How to move SNAPSHOT artifacts to RELEASE stage in Archiva
>
> That you have SNAPSHOT artifacts in the repository implies that you're
> using Maven to build your project.
>
> If so, you can use the Maven Release plugin to automate the process of
> creating a tag and building a released version of your project.
>
> I'm not sure what you meant in (2) about project specific jars and the
> website, can you re-state the question?
>
> > 3. What steps should be followed to stage the release? I have a
> Application
> > Server on which Archiva runs and want to stage the releases in the same
> > server along with the /data/repositories directory? Can this be possible?
>
> It sounds like you want to deploy your released application.  There's
> nothing in Archiva to help with that, but there are other ways to
> automate it.  If you are using Maven there might be a plugin for your
> app server, or you might take a look at the Cargo project.
>
> --
> Wendy
>

--
Thanks & Regards,
Soumen Trivedi
[phone]
Email: Soumen.Trivedi@...

[Wendy Smoak-3]

On Tue, Sep 15, 2009 at 6:01 AM, Soumen Trivedi
<soumen.trivedi@...> wrote:
> Thanks for replying back Wendy. Yes I want to release application specific
> contents into Archiva as RELEASE and not as SNAPSHOT before it is actually
> sent to production env. Do you reckon using Maven for this purpose? I
> apologies for this question, I was thinking that we upload artifacts into
> Archiva as SNAPSHOT and then Archiva helps to move those into RELEASE stage.

This is probably best discussed on the Maven users list, but snapshots
are just a point in time.  They may depend on other snapshots, they
have no associated tag in the scm repo, and generally are not
reproducible, so you wouldn't want to take one and promote it to
release status.

If you check JIRA you may find a feature request for staging and
promoting _releases_ but that implies that you have done an official
release first.

--
Wendy