maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jason van Zyl <>
Subject Re: Easy update sites for Eclipse with Sonatype Nexus
Date Mon, 19 Nov 2012 12:11:15 GMT
You probably want to take this up on the Nexus list.

Today if you manage the creation of the update site or TP you can deploy the zip to Nexus
and it will unpack it into a site repository and then further manipulation will require work.
But you can share update sites and TPs in a primitive way. There are a handful of plugins
that exist for Nexus for generating p2 metadata but, I believe, you want to build and deploy
to Nexus and have Nexus generate the composite along with any additional metadata. 

To see how this currently works you'll need to build an install the unpack plugin[1] and if
you want to see how it's used for deploying m2e and all the extras you can take a look at
this pom[2]. Most of the bits and pieces exist to do what you want and I don't think composite
generation would be terribly difficult. I see people trying to implement this over and over
so I encourage you to bring it up on the Nexus because you're not the only one trying to do
this. In fact the Eclipse Foundation is trying to solve this problem as well.


On Nov 19, 2012, at 3:12 AM, "kai.zimmermann" <> wrote:

> Hi guys,
> I'm looking for a better solution for a problem, I solved it last week, but
> I'm not happy ;)
> My task: Create a fully functional Eclipse update site with Nexus (can be
> used for updates and target platform definitions)
> My problem: The original extension for P2 sites for Nexus only considers
> plugins (
> Unfortunately, the Fork, which considered features, is also out of date. But
> I found a workaround ( in Maven
> P2 plugin. If a plugin is categorized, you can install it with Eclipse.
> Therefore, I searched for a way to categorize my plugins. I build with
> Tycho, but the Nexus does not consider the metadata of Tycho. So I had to
> find a way to let Nexus categorize my plugins without Tycho. Finally, I
> patched
> (
> the Nexus P2 bridge plugin and add a default category to each plugin. In
> addition, we can use this way to omit features!
> Categorization with Eclipse, I only know the composition of repositories.
> Tycho can categorize repositories as well, but the Nexus completely ignored
> the metadata.
> Does anyone have a suggestion on how to categorize plugins or bundles? The
> target is to construct a more useful processing with these metadata in P2
> Nexus plugin.
> thx Kai
> --
> View this message in context:
> Sent from the Maven Developers mailing list archive at
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:



Jason van Zyl
Founder & CTO, Sonatype
Founder,  Apache Maven

Three people can keep a secret provided two of them are dead.

 -- Benjamin Franklin

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message