Uploaded image for project: 'Artificer'
  1. Artificer
  2. ARTIF-508

Restrict s-ramp artifacts depends on the environment

    Details

    • Type: Feature Request
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 0.5.0.Final
    • Component/s: None
    • Labels:
      None

      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.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  virchete David virgil naranjo
                  Reporter:
                  virchete David virgil naranjo
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: