[
https://issues.apache.org/jira/browse/FELIX-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stuart McCulloch resolved FELIX-370.
------------------------------------
Resolution: Fixed
Hi Stefano,
So to sum up: the bundleplugin will now install OBR metadata as part of the
install phase (using <obrRepository> as the location parameter, as well as
providing a way to turn this feature off by setting it to NONE).
However, the bundleplugin does not have any goals to deploy OBR metadata to
remote repositories. If people need this functionality they need to explicitly
enable it in their build pom using the maven-obr-plugin, which imho is
acceptable.
WDYT? - if further changes are necessary, please re-open this issue, thanks!
> Include maven-obr-plugin in maven-bundle-plugin
> -----------------------------------------------
>
> Key: FELIX-370
> URL: https://issues.apache.org/jira/browse/FELIX-370
> Project: Felix
> Issue Type: Wish
> Components: Maven Bundle Plugin
> Affects Versions: 1.0.0
> Reporter: Stefano Lenzi
> Assignee: Stuart McCulloch
> Priority: Minor
> Attachments: patch-maven-bundle-plugin.txt, patch-maven-obr-plugin.txt
>
>
> I'd like to move the maven-obr-plugin from the Clement's sandbox to the trunk
> and add the plugin to the maven-bundle-plugin.
> I've already added some configuration properties to the maven-obr-plugin in
> order to enable/disable the following goal:
> - repository: the goal create/update a local OBR repository in the
> MAVEN_M2_REPO which all the bundle that you compiled by "mvn install"
> - deploy: the goal create/update a remote OBR repository in same server used
> for deploying maven artifact.
> At the moment the default configuration enable the creation of the local OBR
> repository but disable the creation of the remote OBR repository
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
