[
https://issues.apache.org/jira/browse/SLING-7913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16610851#comment-16610851
]
Robert Munteanu commented on SLING-7913:
----------------------------------------
Sorry, the title might've been misleading. I don't want to ban snapshot
references _to_ the starter application. It's references to snapshot _within_
the starter that I'm after.
For instance we currently have in the sling starter
{noformat}
src/main/provisioning/sling.txt:
org.apache.sling/org.apache.sling.sample.slingshot/0.8.1-SNAPSHOT/slingfeature/slingfeature
src/main/provisioning/sling.txt:
org.apache.sling/org.apache.sling.jcr.jackrabbit.usermanager/2.2.7-SNAPSHOT
src/main/provisioning/sling.txt:
org.apache.sling/org.apache.sling.jcr.jackrabbit.accessmanager/3.0.1-SNAPSHOT
{noformat}
These I would like to avoid in the future and stick with releases only.
See also
https://lists.apache.org/thread.html/bc3c8d9450a715e6d8a04e7d237278384eab37bcca5b5630820394f9@%3Cdev.sling.apache.org%3E
where we briefly discussed this.
> 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)
