[overlord-issues] [JBoss JIRA] (SRAMP-508) Restrict s-ramp artifacts depends on the environment

[Eric Wittmann (JIRA)]

     [ https://issues.jboss.org/browse/SRAMP-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Wittmann updated SRAMP-508:
--------------------------------

    Description: 
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.

  was:
The main idea proposed by Gary is to avoid snapshots artifacts in production.
The solution proposed by Eric is to recognize if the s-ramp artifact deployed contains the SNAPSHOT keyword. Then:
    In case it contains SNAPSHOT: allow Snapshots and Released artifacts.
    Not contains SNAPSHOT: allow just Released artifacts.



> 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)