You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Timothee Maret (JIRA)" <ji...@apache.org> on 2015/05/19 12:07:00 UTC
[jira] [Closed] (FELIX-4891) baseline plugin should allow to avoid
comparing non released artifacts
[ https://issues.apache.org/jira/browse/FELIX-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothee Maret closed FELIX-4891.
---------------------------------
Resolution: Fixed
Double checking this, it appears the plugin works as expected with artefacts that are deployed using the SNAPSHOT qualifier. Artefacts that are simply deployed (no branch|tag) are considered as released artifacts by the plugin.
> baseline plugin should allow to avoid comparing non released artifacts
> ----------------------------------------------------------------------
>
> Key: FELIX-4891
> URL: https://issues.apache.org/jira/browse/FELIX-4891
> Project: Felix
> Issue Type: Improvement
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-2.5.4
> Reporter: Timothee Maret
> Fix For: maven-bundle-plugin-2.5.5
>
>
> Currently, the baseline plugin takes into consideration the SNAPSHOT
> artefacts in nexus when computing the versions.
> As a result, a snapshot containing a newer version of a package, or non
> backward compatible changes will block the build unless we bump the
> version to follow semantic versioning.
> I believe we donĀ¹t need that level of strictness and would benefit from
> configuring the baseline plugin to avoid considering anything non released.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)