You can get rid of the messages by forcing the maven-bundle-plugin to use a more recent version of bnd. Here's my plugin config:

<plugin>
    <groupId>org.apache.felix</groupId>
    <artifactId>maven-bundle-plugin</artifactId>
    <version>2.0.0</version>
    <extensions>true</extensions>
    <configuration>
        ...
    </configuration>
    <dependencies>
        <dependency>
            <groupId>biz.aQute</groupId>
            <artifactId>bndlib</artifactId>
            <version>0.0.313</version>
        </dependency>
    </dependencies>
</plugin>

This particular version of bndlib isn't in the central repo, but is listed as a release version on Peter Kriens' site, http://www.aqute.biz/Code/Download (Interestingly, the 0.0.311 version that maven-bundle-plugin 2.0.0 depends on is not listed). To get 0.0.313 you need to add Peter's maven repository to your pom.xml:

<repository>
    <id>maven2-repository.aqute.biz</id>
    <name>aQute/Bnd Repository for Maven</name>
    <url>http://www.aqute.biz/repo/</url>
</repository>

Jim

On Apr 27, 2009, at 11:09 AM, Stuart McCulloch wrote:

2009/4/28 Lewis, Eric <eric.le...@ipi.ch>

Hi

I'm using the bundle plugin to repackage the JBoss client JARs and make
an OSGi bundle from them.
It's a huge load of classes, and I want to export them all.

However, I get the following exception in my Maven log:

[INFO] [bundle:manifest {execution: bundle-manifest}]
Index 560:Exceptions
Index 560:Exceptions
Index 560:Exceptions
Index 560:Exceptions
Index 560:Exceptions
Index 560:Exceptions
Index 560:Exceptions
Index 560:Exceptions
Index 560:Exceptions
Index 560:Exceptions
Index 560:Exceptions
Index 560:Exceptions
Index 560:Exceptions
Index 560:Exceptions
Index 560:Exceptions
Index 560:Exceptions
Index 560:Exceptions
Index 560:Exceptions
Index 560:Exceptions
Index 560:Exceptions
Index 560:Exceptions
Index 560:Exceptions

Does anyone know where that comes from?


it's a trace message that appears when BND processes a large class
(it was unintentionally enabled in the version we picked up for v 2.0.0)

you can safely ignore it and it won't be there in the next release...

Best regards
Eric

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@felix.apache.org
For additional commands, e-mail: users-h...@felix.apache.org

--
Cheers, Stuart

Reply via email to