You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Paul Gier (JIRA)" <ji...@apache.org> on 2016/01/08 20:52:39 UTC

[jira] [Created] (FELIX-5161) Maven bundle plugin does not specify default plugin versions for the "bundle" lifecycle mapping

Paul Gier created FELIX-5161:
--------------------------------

             Summary: Maven bundle plugin does not specify default plugin versions for the "bundle" lifecycle mapping
                 Key: FELIX-5161
                 URL: https://issues.apache.org/jira/browse/FELIX-5161
             Project: Felix
          Issue Type: Bug
          Components: Maven Bundle Plugin
    Affects Versions: maven-bundle-plugin-3.0.0
            Reporter: Paul Gier


The maven bundle plugin provides a custom packaging type (bundle) which defines a custom build lifecycle.  This build lifecycle does not define default plugin versions.
(https://github.com/apache/felix/blob/baf00fa72660905c88f1fe7cd1841ae5489e4a5c/tools/maven-bundle-plugin/src/main/resources/META-INF/plexus/components.xml)

This can cause strange build behavior when using a repository with changing content since Maven will attempt to chose the latest version of a plugin.  If the repository has a bad version of the surefire plugin for example, it could cause a build failure.

Some default versions should be chosen for the lifecycle mapping similar to what is done in Maven itself.
(https://github.com/apache/maven/blob/202f757af3aba6e1b96631de025e0ba692098009/maven-core/src/main/resources/META-INF/plexus/default-bindings.xml)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)