maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Barrie Treloar <baerr...@gmail.com>
Subject Re: classpath issue accessing lib/*.jar in a jar
Date Sun, 03 Oct 2010 02:45:35 GMT
On Fri, Oct 1, 2010 at 7:27 PM,  <torsten.reinhard@gi-de.com> wrote:
> Hi,
>
> acually I´m working on a SAP Web AS integration, so I need to access some
> classes from external 3rd party jars.
> these jars seem to be OSGI bundels, with a MANIFEST.MF containing for
> example:
>
> Require-Bundle: com.tssap.sap.libs.logging
> Bundle-Vendor: %provider.name
> Bundle-ClassPath: lib/sap.com~tc~exception~impl.jar
> Bundle-Version: 2.0.0.091202153157
> Bundle-Localization: plugin
> Bundle-Name: %plugin.name
> Bundle-ManifestVersion: 2
> Bundle-SymbolicName: com.sap.exception;singleton:=true
>
> =>      is there a way to simple deploy these jars and get the classes
> from lib/*.jar into the classpath ?
>        or do I have to extract the lib/*.jar and deploy it separately ?

Have you had a read of the assembly plugin?
http://maven.apache.org/plugins/maven-assembly-plugin/usage.html

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Mime
View raw message