My favorites | Sign in
Project Home Downloads Wiki Issues Source
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 173: Use Maven-Bundle-Plugin to delivery Hamcrest as a OSGi bundle
4 people starred this issue and may be notified of changes. Back to list
Status:  Accepted
Owner:  marc.von...@googlemail.com


Sign in to add a comment
 
Reported by cvgav...@gmail.com, Jan 29, 2012
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.

Apr 12, 2012
Project Member #1 marc.von...@googlemail.com
(No comment was entered for this change.)
Status: Accepted
Owner: marc.von...@googlemail.com
Apr 12, 2012
Project Member #2 marc.von...@googlemail.com
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?
Apr 12, 2012
#5 cvgav...@gmail.com
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. 
May 12, 2012
Project Member #6 t.denley
tagged Java
Labels: Java
May 20, 2012
Project Member #7 t.denley
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
May 30, 2012
#9 cvgav...@gmail.com
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...
Sign in to add a comment

Powered by Google Project Hosting