You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2009/06/11 08:55:07 UTC
[jira] Commented: (SLING-1001) Take the Maven -SNAPSHOT convention
into account when comparing bundle version numbers
[ https://issues.apache.org/jira/browse/SLING-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718321#action_12718321 ]
Bertrand Delacretaz commented on SLING-1001:
--------------------------------------------
This behavior should be configurable (configure the -SNAPSHOT string, empty means no special behavior), as there could be unwanted side effects.
> Take the Maven -SNAPSHOT convention into account when comparing bundle version numbers
> --------------------------------------------------------------------------------------
>
> Key: SLING-1001
> URL: https://issues.apache.org/jira/browse/SLING-1001
> Project: Sling
> Issue Type: Improvement
> Components: JCR Install
> Affects Versions: JCR Install 2.0.4
> Reporter: Bertrand Delacretaz
>
> When doing Maven-based development, it is common to create a new version of a bundle with the same xyz-SNAPSHOT version number as the previous one.
> Currently, jcrinstall does not update the bundle if a new one with the same xyz-SNAPSHOT version number is copied into the repository.
> It should update in this case, i.e. consider the bundle as a new version if the version string is the same as the installed one but contains -SNAPSHOT.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.