|Re: [cross-project-issues-dev] Using maven artifacts directly in eclipse target platform / tycho builds|
Improving the Maven compatibility is certainly a good idea, but for my (small number of) users the problem is the other way round. How to make Eclipse standalone project releases easily consumable by Maven.
https://www.eclipse.org/forums/index.php/mv/msg/1097672/1826580/#msg_1826580 is an attempt by a user to contribute.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=562307 is my fruitless attempts to actually publish via https://repo.eclipse.org although I gather that is now going out of fashion.
As a naive traditional Eclipse releng I have successfully struggled to keep the P2 builds going. I see P2-to-Maven as a generic capability that the EF (or some skilled contributor) should solve on behalf of the community. As with downloads, when everyone does their own thing, it takes a lot of effort to produce an inconsistent mess.
Happy new year everyone,
I'd like to introduce a new feature in m2e / Tycho that supports the seaming-less integration for maven artifacts (OSGi and even non OSGi ones) to be used both in Eclipse IDE and Tycho Maven build.
This consists of two complementary features, a m2e extension for PDE that allows the adding/editing of a new target location type "Maven" and support for this location type in Tycho itself.
I have written a more detailed description in the following article .
I'd like to get some feedback so let me know if something is missing or bugs you encountered either via mailing-list, by directly contacting me or simply open a bug/enhancement in the m2e bugtracker , also please let me know if you think the article itself needs some deeper description of a given aspect of the new feature!
cross-project-issues-dev mailing list
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
Back to the top