Hi Craig,
what we are doing at the moment to avoid your problems is to add
exclude statements to our dependencies i.e.,
<dependency>
<groupId>${groupId}</groupId>
<artifactId>org.apache.felix.framework</artifactId>
<exclusions>
<exclusion>
<groupId>${pom.groupId}</groupId>
<artifactId>org.osgi.core</artifactId>
</exclusion>
</exclusions>
</dependency>
Hope this helps.
regards,
Karl
On 7/19/07, Craig L. Ching <[EMAIL PROTECTED]> wrote:
Hi all,
I'm wondering if what I want to do is possible. There are a number of
OS libraries out there with their own dependencies, e.g., jackrabbit
which has the following dependencies:
jcr-1.0.jar
slf4j-log4j12-1.0.jar
log4j-1.2.8.jar
xercesImpl-2.6.2.jar
xmlParserApis-2.0.2.jar
derby-10.1.3.1.jar
concurrent-1.3.4.jar
lucene-1.4.3.jar
So I thought it would be a good idea to package jackrabbit as an OSGi
bundle (since I don't think jackrabbit does this themselves). So I
created a new maven project, added these as dependencies (regular jar
dependencies), and configured the maven bundle plugin. It worked like a
charm and I appear to have valid OSGi bundles.
The problem is that when I create a dependency on this project from
another project (e.g. a webapp project), it not only includes the bundle
in the deployment, but the jars that were used to make up the
deployment. I guess what I'm trying to do could be summed up as being
the same thing as creating an "eclipse plugin project from existing
jars", if that makes sense. Am I going about this the right way?
Cheers,
Craig
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Karl Pauls
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
