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 (https://github.com/sonatype/nexus-p2-repository-plugin) Unfortunately, the Fork, which considered features, is also out of date. But I found a workaround (https://github.com/reficio/p2-maven-plugin) 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 (https://github.com/nachtgold/nexus-p2-bridge-plugin/commit/c0941a2398efd7662dc3c8d64e91fd72d1eb18df) 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: http://maven.40175.n5.nabble.com/Easy-update-sites-for-Eclipse-with-Sonatype-Nexus-tp5731750.html Sent from the Maven Developers mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
