[
https://issues.apache.org/jira/browse/JCLOUDS-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16990167#comment-16990167
]
Markus Kuppe commented on JCLOUDS-1531:
---------------------------------------
Not much, if you look at how they do it for JMC
([https://github.com/openjdk/jmc/blob/7bb3839e95fda8449525f767ed0d893f13ad115b/releng/third-party/pom.xml#L48-L99).]
You essentially list the OSGi/bundles in a pom.xml and run ```mvn p2:site```.
Afterwards, pick a place to publish the result.
> Create p2 as part of maven build to make consumption in Eclipse apps easier
> ---------------------------------------------------------------------------
>
> Key: JCLOUDS-1531
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1531
> Project: jclouds
> Issue Type: Wish
> Reporter: Markus Kuppe
> Priority: Major
>
> Eclipse's primary repository format is p2. Consuming artifacts from a mixture
> of p2 and (plain) maven repositories is brittle. As a workaround, I've been
> building a p2 repository for jclouds [1]. Recently however, I learned about
> a maven plugin [2] to easily create p2 repositories. Would a patch be
> accepted into jclouds that adds p2 repository creation to jcloud's maven
> build?
>
> [1][
> https://github.com/lemmy/jclouds2p2/|https://github.com/lemmy/jclouds2p2/]
> [2] https://github.com/reficio/p2-maven-plugin
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
