[
https://issues.jboss.org/browse/SRAMP-508?page=com.atlassian.jira.plugin....
]
Brett Meyer commented on SRAMP-508:
-----------------------------------
See my note on
https://github.com/Governance/s-ramp/pull/464. There were some major
issues and I had to back out of the merge.
Restrict s-ramp artifacts depends on the environment
-----------------------------------------------------
Key: SRAMP-508
URL:
https://issues.jboss.org/browse/SRAMP-508
Project: S-RAMP
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: David virgil naranjo
Assignee: David virgil naranjo
By default the S-RAMP Maven integration should not allow maven snapshots to be deployed
to the s-ramp repository (since this is not a use-case we want to encourage). However, we
are planning to support maven snapshots in the code via a flag to enable/disable the
support. This flag will be consumed by the maven repository facade. The flag (e.g.
s-ramp.maven.enable-snapshots) will default to *false* unless the S-RAMP runtime itself is
a SNAPSHOT.
This will make it easier for us during development of s-ramp and dtgov to test out our
demos and dtgov seed data without changing the versions of those artifacts in their
respective pom.xml files.
So in summary - the maven repo facade will not allow SNAPSHOT artifacts to be deployed
unless the flag is set to true *or* the current s-ramp runtime version is a snapshot
version.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)