Hi Bruce, I don’t really know enough about Maven to understand why this happens, but I believe that there is a documented workaround.
If you read the documentation page for the Maven bundle plugin (https://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html), you will find a section entitled "Adding OSGi metadata to existing projects without changing the packaging type”. This should allow you to build a bundle while still having the artifact treated as a JAR by Maven. Regards, Neil On 24 April 2014 at 22:07:08, Bruce Jackson ([email protected]) wrote: Hi Everyone We¹re using Amazon¹s AWS SDK for Java for a big OSGi-based project. To this end, we¹ve repackaged the SDK by building from source and using the maven packaging/plugin options and BND tools plugin to turn this into an OSGi bundle. Amazon are actually really helpful: they¹ve taken a couple of patches we¹ve provided to the project where assumptions were being made about ClassLoaders that weren¹t OSGi-safe, and we¹re discussing using the pom.xml file we use to build the SDK Jar for general use. They¹re apparently tried this in the past, but it hasn¹t worked out and I was wondering if any of your guys who are more familiar with maven and BND tools might be able to shed some light on this: Amazon say: When we changed the packaging to 'bundle' the artifacts were uploaded to Maven central as '*.bundle' artifacts: http://repo1.maven.org/maven2/com/amazonaws/aws-java-sdk/1.6.9/ This caused problems for our existing Maven consumers, because they were no longer able to resolve Jar artifacts through Maven and couldn't access the latest release, so we had to revert. If you can shed more light on exactly why that was occurring and causing problems, we'd be happy to listen. Does anyone have any ideas what this means? Best regards Bruce *** DISCLAIMER *** This message, including attachments, is intended solely for the addressee indicated in this message and is strictly confidential or otherwise privileged. If you are not the intended recipient (or responsible for delivery of the message to such person) : - (1) please immediately (i) notify the sender by reply email and (ii) delete this message and attachments, - (2) any use, copy or dissemination of this transmission is strictly prohibited. If you or your employer does not consent to Internet email messages of this kind, please advise Myriad Group AG by reply e-mail immediately. Opinions, conclusions and other information expressed in this message are not given or endorsed by Myriad Group AG unless otherwise indicated by an authorized representative independent of this message. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
