search

truptivala / hamcrest

Automatically exported from code.google.com/p/hamcrest
0 stars 0 forks source link

Use Maven-Bundle-Plugin to delivery Hamcrest as a OSGi bundle #173

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
People have to wrap Hamcrest to be able to used in a OSGi environment. It would 
much better to delivery hamcrest as an bundle already using the easy felix 
maven-bundle-plugin.

Original issue reported on code.google.com by cvgav...@gmail.com on 29 Jan 2012 at 4:32

GoogleCodeExporter commented 8 years ago

Original comment by marc.von...@gmail.com on 12 Apr 2012 at 8:04

GoogleCodeExporter commented 8 years ago 
For which project should a bundle be created? hamcrest-integration? (And this 
should include all the hamcrest dependencies in one jar?)

Sorry, I have not worked with OSGI before. What packages should be exported? 
Simply all? Is an Activator mandatory or optional? If you have already done 
this for hamcrest, could you send be a sample configuration?

Original comment by marc.von...@gmail.com on 12 Apr 2012 at 10:32

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
Hi,
I haven't done it myself but I'm using the ones supplied by Eclipse Orbit: 
http://download.eclipse.org/tools/orbit/downloads/drops/S20120308061416/

As you can see in the list, the hamcrest bundles are for version 1.1.0, but you 
can watch the pom examples there.
let me know if you need more information.

Original comment by cvgav...@gmail.com on 12 Apr 2012 at 11:05

GoogleCodeExporter commented 8 years ago 
tagged Java

Original comment by t.denley on 12 May 2012 at 10:13

GoogleCodeExporter commented 8 years ago 
Correct me if I'm wrong, but isn't this just a matter of including the 
appropriate properties in the MANIFEST.MF of each of the hamcrest jars?

Something like this perhaps:

Bundle-ManifestVersion: 2
Bundle-Name: Hamcrest Core
Bundle-Description: Core Hamcrest classes
Bundle-SymbolicName: org.hamcrest.core
Bundle-Version: 1.3
Bundle-Vendor: Hamcrest
Export-Package: org.hamcrest;version="1.3"
Bundle-RequiredExecutionEnvironment: J2SE-1.5
Bundle-ActivationPolicy: lazy

Original comment by t.denley on 20 May 2012 at 7:53

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
Strange I wasn't notified in your last comment. So, sorry for late answer.

It is exactly the goal...

Using the plugin is just to automate the creation of the MANIFEST.MF and its 
maintenance when using maven to build the projects...

Original comment by cvgav...@gmail.com on 30 May 2012 at 9:43