Craig, Karl,
I am still using the maven-osgi-plugin (not the maven-bundle-plugin)
and it does include the dependencies. See here for example POM:
http://m2.modularity.net.au/snapshots/net/modularity/net.modularity.repository/1.0.0-SNAPSHOT/net.modularity.repository-1.0.0-SNAPSHOT.pom
And the artifact:
http://m2.modularity.net.au/snapshots/net/modularity/net.modularity.repository/1.0.0-SNAPSHOT/net.modularity.repository-1.0.0-SNAPSHOT.jar
regards,
ben
On 7/21/07, Craig L. Ching <[EMAIL PROTECTED]> wrote:
> > Ok, hold on, I do understand what's going on here, but it begs a
> > question. When I specify jackrabbit-core as a dependency,
> there is a
> > pom in the repo that indicates that concurrent is a dependency and
> > that's how it's getting it. But, what are the implications of this
> > with respect to the felix bundle plugin? Does it include this
> > dependency in the bundle? I mean, it should, right?
>
> Well, it will only do this if you tell it to. The plugin
> includes what matches the given Export-Package and
> Private-Package header. So maybe you need to include it
> there... else it should generate imports for this dependencies.
>
Well it doesn't seem to work this way. If I specify this:
<build>
<plugins>
<plugin>
<groupId>org.apache.felix</groupId>
<artifactId>maven-bundle-plugin</artifactId>
<version>1.1.0-SNAPSHOT</version>
<extensions>true</extensions>
<configuration>
<instructions>
<Export-Package>javax.jcr.*,org.apache.jackrabbit.*</Export-Package>
<!--
<Import-Package>javax.jcr.*,org.apache.jackrabbit.*</Import-Package> -->
<Private-Package>EDU.oswego.cs.dl.util.concurrent</Private-Package>
</instructions>
</configuration>
</plugin>
</plugins>
</build>
<dependencies>
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>3.8.1</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.apache.jackrabbit</groupId>
<artifactId>jackrabbit-core</artifactId>
<version>1.3</version>
</dependency>
<!--
<dependency>
<groupId>concurrent</groupId>
<artifactId>concurrent</artifactId>
<version>1.3.4</version>
</dependency>
-->
</dependencies>
The contents of the concurrent artifact are not incorporated into the
resulting bundle. I have to uncomment the concurrent dependency to get
it included *even though* it's specified as a dependency of
jackrabbit-core in the repository. This means I need to manually peruse
the pom of the artifacts and include those dependencies explicitly,
right?
Cheers,
Craig
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
xmpp:[EMAIL PROTECTED]
http://blogs.fortuna.net.au/discussed
"Sometimes, doing nothing is a strategy. Don't worry about the future.
It will unfold." - Bill Rachinger
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
