[
https://issues.apache.org/jira/browse/SLING-7913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16610893#comment-16610893
]
Eric Norman commented on SLING-7913:
------------------------------------
I wasn't confused about that. I'm saying that in order to integration test
those various SNAPSHOT artifacts, you have to get them into the
launchpad-testing sling runtime so the tests can run against those unreleased
artifacts.
If I am not mistaken, this is currently done for launchpad-testing (and others)
by pulling in the artifacts from the starter-SNAPSHOT.
So in that case, if I can't use a SNAPSHOT in the starter models, then I also
can't add new tests in launchpad-testing or change existing tests in
launchpad-testing without a lot of extra work to pull in the SNAPSHOT artifacts
that the new tests would be covering.
It seems simpler to me to just use SNAPSHOTS in the starter model so I only
have to change things in one place. If there are problems with any of the
SNAPSHOT artifacts, then the automated tests should detect those problems early
and the person responsible should be ready to address those problems or revert
their changes.
> Ban snapshots in the Sling starter
> ----------------------------------
>
> Key: SLING-7913
> URL: https://issues.apache.org/jira/browse/SLING-7913
> Project: Sling
> Issue Type: Bug
> Components: Starter
> Reporter: Robert Munteanu
> Priority: Major
> Fix For: Starter 11
>
>
> We have agreed to keep only releases in the Sling starter to make it easier
> to release and to make builds reproducible.
> We should enforce this policy to make it impossible to mistakenly add
> SNAPSHOT versions to the project.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
