[EMAIL PROTECTED] schrieb:
[EMAIL PROTECTED] schrieb:
hi,
when building a bundle dependency-jars get extracted and class files
get copied respective to package structure
mainBundleJar:
-own/classes
-external/libClasses
this approach works, but it hinders when wanting to get an overview,
which libraries are included and licence-information+resources are
spread around everywhere. that's when working with external
libraries i think the best is to include it as a encapsulated jar like:
mainBundleJar:
-own/classes
-externalLibrary1.jar
-externalLibrary2.jar
-META-INF/<ManifestTellingToIncludeEncapsulatedJarsToClasspath.mf>
i know with standard classLoader this encapsulated jars are not
supported, but through a custom classLoader (as OSGI uses its own,
too) this could be done.
so is it possible to provide inner jars with maven-bundle-plugin or
does this layout not conform to OSGI spec anyway, so cannot be
implemented?
it seems that i got the option to enable (inline has to be set to false):
<Embed-Dependency>*;groupId=!org.eclipse.equinox;inline=false</Embed-Dependency>
this way dependencies are included as jars.
but this still does not work completely because the classes still get
extracted and inlined. so i end up with classes getting extracted and
jar-bundles to be placed too. or do i misunderstand the semantics
behind inline property?
error again on my side...
i forgot to reset <Private-Package>*</Private-Package>. this way
depedency got included twice.
hence using <Embed-Dependency> does not influence <Private-Package>
property.
--
manuel aldana
[EMAIL PROTECTED]
homepage: www.aldana-online.de
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
