Launchpad plugin's LifecycleParticipant doesn't get the default bundle list
version from a execution configuration
------------------------------------------------------------------------------------------------------------------
Key: SLING-2291
URL: https://issues.apache.org/jira/browse/SLING-2291
Project: Sling
Issue Type: Bug
Components: Maven Plugins and Archetypes
Reporter: Justin Edelson
if you have a plugin configuration like this:
<plugin>
<groupId>org.apache.sling</groupId>
<artifactId>maven-launchpad-plugin</artifactId>
<version>2.1.1-SNAPSHOT</version>
<extensions>true</extensions>
<executions>
<execution>
<id>prepare-package</id>
<goals>
<goal>prepare-package</goal>
</goals>
<configuration>
<defaultBundleList>
<version>${project.version}</version>
</defaultBundleList>
</configuration>
</execution>
</executions>
</plugin>
the LifecycleParticipant won't notice that the defaultBundleList version was
overridden. Temporary workaround is to put the configuration outside the
execution:
<plugin>
<groupId>org.apache.sling</groupId>
<artifactId>maven-launchpad-plugin</artifactId>
<version>2.1.1-SNAPSHOT</version>
<extensions>true</extensions>
<executions>
<execution>
<id>prepare-package</id>
<goals>
<goal>prepare-package</goal>
</goals>
</execution>
</executions>
<configuration>
<defaultBundleList>
<version>${project.version}</version>
</defaultBundleList>
</configuration>
</plugin>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
