[overlord-issues] [JBoss JIRA] (SRAMP-507) Modify way the snapshot artifacts are stored in s-ramp

RH Bugzilla Integration (JIRA) issues at jboss.org
Tue Jul 29 12:52:31 EDT 2014


    [ https://issues.jboss.org/browse/SRAMP-507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988741#comment-12988741 ] 

RH Bugzilla Integration commented on SRAMP-507:
-----------------------------------------------

Brett Meyer <brmeyer at redhat.com> changed the Status of [bug 1060773|https://bugzilla.redhat.com/show_bug.cgi?id=1060773] from POST to MODIFIED

> Modify way the snapshot artifacts are stored in s-ramp
> ------------------------------------------------------
>
>                 Key: SRAMP-507
>                 URL: https://issues.jboss.org/browse/SRAMP-507
>             Project: S-RAMP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: David virgil naranjo
>            Assignee: David virgil naranjo
>             Fix For: 0.5.0.Beta2
>
>
> Include a property mvn.snapshot.timestamp (in case the name contains the timestamp)
> When deploying a snapshot artifact, maven will include a timestamp in the filename.  The maven repository facade *and* the s-ramp wagon should be updated to store this timestamp info in a new s-ramp property (see above).  In addition, the s-ramp wagon should no longer *ever* attempt to update an artifact.  Here is what it should do:
> h4. Release artifacts
> * If this artifact (GAV) already exists in s-ramp, fail
> * If this artifact doesn't yet exist, add it
> h4. Snapshot artifacts
> * If this artifact (GAV + timestamp) already exists in s-ramp, fail
> * If this artifact doesn't yet exist, add it along with its timestamp information



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)


More information about the overlord-issues mailing list