Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 490511 - How to consume org.eclipse.osgi and org.eclipse.osgi.services bundles from Maven/Gradle build?
Summary: How to consume org.eclipse.osgi and org.eclipse.osgi.services bundles from Ma...
Status: CLOSED WONTFIX
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: Website (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: equinox.website-inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-28 05:27 EDT by Paul Verest CLA
Modified: 2019-08-31 08:34 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Verest CLA 2016-03-28 05:27:56 EDT
How to consume org.eclipse.osgi and org.eclipse.osgi.services bundles from Maven/Gradle build? org.eclipse.osgi and org.eclipse.osgi.services bundles are not in Maven Central.

This issue is not about publishing all to Maven Central, there is 4 year old Bug 365798 - Push org.eclipse.osgi to Maven Central , but how to consume bundle with modern build tools like Maven/Gradle? Possibly documentation issue.

For Apache Felix I could find how to use Maven
http://felix.apache.org/documentation/subprojects/apache-felix-maven-bundle-plugin-bnd.html

http://felix.apache.org/documentation/subprojects/apache-felix-dependency-manager/tutorials/working-with-annotations.html	

I could find only 1 version of bundles in question on Maven central
and use within Gradle, but there are many questions open.

   //http://mvnrepository.com/artifact/org.eclipse.osgi/org.eclipse.osgi 
	compile 'org.eclipse.osgi:org.eclipse.osgi:3.6.0.v20100517'
	compile 'org.eclipse.osgi:org.eclipse.osgi.services:3.2.100.v20100503'
Comment 1 Eclipse Genie CLA 2019-08-31 08:34:48 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.