[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [m2e-dev] Contributing m2e extension
|
For now, I think it's better to keep this code in independent
repositories. For m2e extensions development to scale, we need a
collaboration of a community of developers; donating code to a
commercial entity is not going to help grow such community. This will
also suggest that Sonatype takes over maintenance and support of the
code, and this is not the case.
Public p2 repository is basically contents of feature/target/site
directory made available over http. I'll see if we can arrange a common
place for this, but you can push your extension's p2 repo to github, for
example.
What exact questions do you have about p2? It maybe easier to answer
them here.
--
Regards,
Igor
On 11-06-30 7:50 PM, Harald Wellmann wrote:
I'm working on an m2e extension for the maven-jaxb2-plugin, which I'd
like to share.
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=350299
I forked the m2e-extras Github repository, created a copy of the
antlr plugin, and for me the easiest way to get on from here would be
to simply send a pull request and see my plugin in the list with
other Sonatype extensions after the next release.
I don't really care if my plugin lives in org.eclipse, org.sonatype
or under any other namespace or license as long as I can continue to
use and modify my own code.
The procedure described in
http://wiki.eclipse.org/Submitting_M2E_marketplace_entries is rather
sketchy and seems to require a public p2 repository, which I don't
have access to. If the idea is to build one's own repository and
simply check it in at Github or anywhere else, then my question is,
how do I build a p2 repository, what's an installable unit etc.
The Plug-in Development Environment Guide is not very good at
explaining p2 for Dummies - is there any other documentation?
Thanks, Harald
