Using osgi plugin to generate manifests
We current specify manifests for some of the jars that enable them to be used as OSGi bundles. These (IIRC) are based on some sent in near the start of the year. One problem I think we face is in tracking the content of these to keep them current. I did some experimentation with the maven-osgi-plugin from Apache Felix which allows the OSGi manifest entries to be automatically generated - attached is a delta to the POM for the sca-api module that generates the manifest rather than relying on the one in the source tree. Can someone more OSGi literate than me please check that this is a reasonable manifest and see if this is a better approach? Thanks -- Jeremy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using osgi plugin to generate manifests
The attachment is missing. :-) Raymond - Original Message - From: "Jeremy Boynes" <[EMAIL PROTECTED]> To: Sent: Friday, July 21, 2006 2:41 PM Subject: Using osgi plugin to generate manifests We current specify manifests for some of the jars that enable them to be used as OSGi bundles. These (IIRC) are based on some sent in near the start of the year. One problem I think we face is in tracking the content of these to keep them current. I did some experimentation with the maven-osgi-plugin from Apache Felix which allows the OSGi manifest entries to be automatically generated - attached is a delta to the POM for the sca-api module that generates the manifest rather than relying on the one in the source tree. Can someone more OSGi literate than me please check that this is a reasonable manifest and see if this is a better approach? Thanks -- Jeremy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using osgi plugin to generate manifests
You may need to zip the attachments since it looks as if the list stripped them. Jim On Jul 21, 2006, at 2:41 PM, Jeremy Boynes wrote: We current specify manifests for some of the jars that enable them to be used as OSGi bundles. These (IIRC) are based on some sent in near the start of the year. One problem I think we face is in tracking the content of these to keep them current. I did some experimentation with the maven-osgi-plugin from Apache Felix which allows the OSGi manifest entries to be automatically generated - attached is a delta to the POM for the sca-api module that generates the manifest rather than relying on the one in the source tree. Can someone more OSGi literate than me please check that this is a reasonable manifest and see if this is a better approach? Thanks -- Jeremy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using osgi plugin to generate manifests
Sometimes they work and sometimes they don't ... let's try this
Index: pom.xml
===
--- pom.xml (revision 424385)
+++ pom.xml (working copy)
@@ -18,13 +18,19 @@
4.0.0
org.osoa
sca-api-r0.95
+1.0-SNAPSHOT
+osgi-bundle
SCA API
-1.0-SNAPSHOT
+API classes for the Service Component Architecturedescription>
2.0.4
+
+The Apache Software Foundation
+http://www.apache.org
+
The Apache Software License, Version 2.0
@@ -40,9 +46,9 @@
scp:///www/people.apache.org/repo/m2-snapshot-
repository
- apache-snapshot-repository
- Apache SNAPSHOT Repository
- scp:///www/people.apache.org/repo/m2-snapshot-
repository
+apache-snapshot-repository
+Apache SNAPSHOT Repository
+scp:///www/people.apache.org/repo/m2-snapshot-
repository
@@ -61,6 +67,13 @@
+
+
+apache-snapshot-repository
+Apache SNAPSHOT Repository
+http://people.apache.org/repo/m2-snapshot-
repository
+
+
@@ -72,12 +85,18 @@
-org.apache.maven.plugins
-maven-jar-plugin
+org.apache.felix.plugins
+maven-osgi-plugin
+true
-
-src/main/resources/META-INF/
MANIFEST.MF
-
+
+${pom.name}
+${pom.description}bundleDescription>
+${pom.organization.name}bundleVendor>
+plugin
+org.osoa.scabundleSymbolicName>
+org.osoa.sca,
org.osoa.sca.annotations
+
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using osgi plugin to generate manifests
Several questions:
1) What's going to happen if a 3rd party dependency is not OSGi bundled?
2) How does it deal with "Require-Bundle"? It seems that it can populate
"Import-Package" automatically.
3) Can you post a sample MANIFEST.MF generated by the plugin?
I found this document useful:
http://docs.safehaus.org/display/OSGI/OSGi+Plugin+for+Maven+2.0
Thanks,
Raymond
- Original Message -
From: "Jeremy Boynes" <[EMAIL PROTECTED]>
To:
Sent: Friday, July 21, 2006 3:00 PM
Subject: Re: Using osgi plugin to generate manifests
Sometimes they work and sometimes they don't ... let's try this
Index: pom.xml
===
--- pom.xml (revision 424385)
+++ pom.xml (working copy)
@@ -18,13 +18,19 @@
4.0.0
org.osoa
sca-api-r0.95
+1.0-SNAPSHOT
+osgi-bundle
SCA API
-1.0-SNAPSHOT
+API classes for the Service Component Architecturedescription>
2.0.4
+
+The Apache Software Foundation
+http://www.apache.org
+
The Apache Software License, Version 2.0
@@ -40,9 +46,9 @@
scp:///www/people.apache.org/repo/m2-snapshot-
repository
- apache-snapshot-repository
- Apache SNAPSHOT Repository
- scp:///www/people.apache.org/repo/m2-snapshot-
repository
+apache-snapshot-repository
+Apache SNAPSHOT Repository
+scp:///www/people.apache.org/repo/m2-snapshot-
repository
@@ -61,6 +67,13 @@
+
+
+apache-snapshot-repository
+Apache SNAPSHOT Repository
+http://people.apache.org/repo/m2-snapshot-
repository
+
+
@@ -72,12 +85,18 @@
-org.apache.maven.plugins
-maven-jar-plugin
+org.apache.felix.plugins
+maven-osgi-plugin
+true
-
-src/main/resources/META-INF/
MANIFEST.MF
-
+
+${pom.name}
+${pom.description}bundleDescription>
+${pom.organization.name}bundleVendor>
+plugin
+org.osoa.scabundleSymbolicName>
+org.osoa.sca,
org.osoa.sca.annotations
+
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using osgi plugin to generate manifests
On Jul 21, 2006, at 3:25 PM, Raymond Feng wrote: Several questions: 1) What's going to happen if a 3rd party dependency is not OSGi bundled? 2) How does it deal with "Require-Bundle"? It seems that it can populate "Import-Package" automatically. 3) Can you post a sample MANIFEST.MF generated by the plugin? Manifest-Version: 1.0 Archiver-Version: Plexus Archiver Created-By: Apache Maven Built-By: jboynes Build-Jdk: 1.5.0_06 Extension-Name: sca-api-r0.95 Specification-Title: API classes for the Service Component Architecture Specification-Vendor: The Apache Software Foundation Implementation-Vendor: The Apache Software Foundation Implementation-Title: sca-api-r0.95 Implementation-Version: 1.0-SNAPSHOT Export-Package: org.osoa.sca.annotations, org.osoa.sca Bundle-Version: 1.0.SNAPSHOT Bundle-Vendor: The Apache Software Foundation Bundle-Name: SCA API Bundle-Classpath: . Bundle-Localization: plugin Bundle-Description: API classes for the Service Component Architecture Bundle-SymbolicName: org.osoa.sca I found this document useful: http://docs.safehaus.org/display/OSGI/ OSGi+Plugin+for+Maven+2.0 That's as much as I know as well. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using osgi plugin to generate manifests
On 7/24/06, Jeremy Boynes <[EMAIL PROTECTED]> wrote: > On Jul 21, 2006, at 3:25 PM, Raymond Feng wrote: > >> Several questions: >> >> 1) What's going to happen if a 3rd party dependency is not OSGi >> bundled? >> 2) How does it deal with "Require-Bundle"? It seems that it can >> populate "Import-Package" automatically. >> 3) Can you post a sample MANIFEST.MF generated by the plugin? > > Manifest-Version: 1.0 > Archiver-Version: Plexus Archiver > Created-By: Apache Maven > Built-By: jboynes > Build-Jdk: 1.5.0_06 > Extension-Name: sca-api-r0.95 > Specification-Title: API classes for the Service Component > Architecture > Specification-Vendor: The Apache Software Foundation > Implementation-Vendor: The Apache Software Foundation > Implementation-Title: sca-api-r0.95 > Implementation-Version: 1.0-SNAPSHOT > Export-Package: org.osoa.sca.annotations, org.osoa.sca > Bundle-Version: 1.0.SNAPSHOT > Bundle-Vendor: The Apache Software Foundation > Bundle-Name: SCA API > Bundle-Classpath: . > Bundle-Localization: plugin > Bundle-Description: API classes for the Service Component Architecture > Bundle-SymbolicName: org.osoa.sca i'm not an OSGI expert so i'll just comment on the java stuff. looks like the Specification-Version and the Implementation-Vendor-Id attributes are missing. both these attributes are recommended by Java specifications. IMHO it might be better to include tuscany in the implementation title but i don't think that the current manefest is uncomplient. - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
OSGI headers, was: Using osgi plugin to generate manifests
Joel With your knowledge of OSGi, is this header set reasonable or are there others we should be adding? -- Jeremy On Jul 21, 2006, at 3:33 PM, Jeremy Boynes wrote: On Jul 21, 2006, at 3:25 PM, Raymond Feng wrote: Several questions: 1) What's going to happen if a 3rd party dependency is not OSGi bundled? 2) How does it deal with "Require-Bundle"? It seems that it can populate "Import-Package" automatically. 3) Can you post a sample MANIFEST.MF generated by the plugin? Manifest-Version: 1.0 Archiver-Version: Plexus Archiver Created-By: Apache Maven Built-By: jboynes Build-Jdk: 1.5.0_06 Extension-Name: sca-api-r0.95 Specification-Title: API classes for the Service Component Architecture Specification-Vendor: The Apache Software Foundation Implementation-Vendor: The Apache Software Foundation Implementation-Title: sca-api-r0.95 Implementation-Version: 1.0-SNAPSHOT Export-Package: org.osoa.sca.annotations, org.osoa.sca Bundle-Version: 1.0.SNAPSHOT Bundle-Vendor: The Apache Software Foundation Bundle-Name: SCA API Bundle-Classpath: . Bundle-Localization: plugin Bundle-Description: API classes for the Service Component Architecture Bundle-SymbolicName: org.osoa.sca I found this document useful: http://docs.safehaus.org/display/ OSGI/OSGi+Plugin+for+Maven+2.0 That's as much as I know as well. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: OSGI headers, was: Using osgi plugin to generate manifests
That's excately what I used. The one thing I'd add a version for the exported packages. It helps the package admin service avoid runtime incompatabilities when sewing up bundle dependencies. > Export-Package: org.osoa.sca.annotations;version="1.0", > org.osoa.sca;version="1.0" Cheers, Joel -Original Message- From: Jeremy Boynes [mailto:[EMAIL PROTECTED] Sent: Wed 8/9/2006 7:32 PM To: tuscany-dev@ws.apache.org Subject: OSGI headers, was: Using osgi plugin to generate manifests Joel With your knowledge of OSGi, is this header set reasonable or are there others we should be adding? -- Jeremy On Jul 21, 2006, at 3:33 PM, Jeremy Boynes wrote: > On Jul 21, 2006, at 3:25 PM, Raymond Feng wrote: > >> Several questions: >> >> 1) What's going to happen if a 3rd party dependency is not OSGi >> bundled? >> 2) How does it deal with "Require-Bundle"? It seems that it can >> populate "Import-Package" automatically. >> 3) Can you post a sample MANIFEST.MF generated by the plugin? > > Manifest-Version: 1.0 > Archiver-Version: Plexus Archiver > Created-By: Apache Maven > Built-By: jboynes > Build-Jdk: 1.5.0_06 > Extension-Name: sca-api-r0.95 > Specification-Title: API classes for the Service Component > Architecture > Specification-Vendor: The Apache Software Foundation > Implementation-Vendor: The Apache Software Foundation > Implementation-Title: sca-api-r0.95 > Implementation-Version: 1.0-SNAPSHOT > Export-Package: org.osoa.sca.annotations, org.osoa.sca > Bundle-Version: 1.0.SNAPSHOT > Bundle-Vendor: The Apache Software Foundation > Bundle-Name: SCA API > Bundle-Classpath: . > Bundle-Localization: plugin > Bundle-Description: API classes for the Service Component Architecture > Bundle-SymbolicName: org.osoa.sca > > >> I found this document useful: http://docs.safehaus.org/display/ >> OSGI/OSGi+Plugin+for+Maven+2.0 > > That's as much as I know as well. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
