[
https://issues.jboss.org/browse/SRAMP-487?page=com.atlassian.jira.plugin....
]
Brett Meyer commented on SRAMP-487:
-----------------------------------
From [~eric.wittmann]:
{quote}
Consider: don't allow updates for non-SNAPSHOT artifacts. For SNAPSHOT
artifacts add a new one (do not update). So in other words, *never*
update the s-ramp artifact. Instead, either fail (non-SNAPSHOT) or
create new (SNAPSHOT).
The latter should never be done, but can be supported anyway (users
probably shouldn't be putting snapshot artifacts in s-ramp).
{quote}
Improved handling of artifact updates
-------------------------------------
Key: SRAMP-487
URL:
https://issues.jboss.org/browse/SRAMP-487
Project: S-RAMP
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Reporter: Brett Meyer
Assignee: Brett Meyer
Fix For: 0.6.0
Currently, artifacts can be deployed multiple times, duplicating extracted/derived
content. [~eric.wittmann] pointed out that the spec is a little ambiguous with regards to
updating artifacts. My gut reaction is that it probably shouldn't be allowed (think
Nexus). However, snapshots should probably be updatable, and therefore would need
extracted/derived content (and their relationships) removed prior to updating.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)