Results 1 to 2 of 2

Thread: ADDON CREATE WRAPPER - An endless journey or Am I missing something?

  1. #1

    Default ADDON CREATE WRAPPER - An endless journey or Am I missing something?

    I wanted to create an ADDON WRAPPER for the Apache-Velocity jars. When I deployed the wrapped Bundle, OSGI asked for werken-xpath jar. I added this to POM.xml. OSGI then asked for antlr. The chain reaction went on: javax.servlet, junit, commons-logging, org.apache.avalon.framework, avalon-logkit & javax.jms.
    Finally, the javax.jms jars were missing in MavenRepository. (<groupId>javax.jms</groupId> <artifactId>jms</artifactId> <version>1.1</version>)
    Please help.

  2. #2
    Join Date
    Dec 2005
    Posts
    930

    Default

    You probably have to add exclusions to your wrapping pom. An example (H2 database) is:
    Code:
        <build>
            <plugins>
                <plugin>
                    <groupId>org.apache.felix</groupId>
                    <artifactId>maven-bundle-plugin</artifactId>
                    <extensions>true</extensions>
                    <configuration>
                        <instructions>
                            <Import-Package>javax.servlet.*;resolution:=optional,org.apache.lucene.*;resolution:=optional,org.slf4j;resolution:=optional,*</Import-Package>
                        </instructions>
                    </configuration>
                </plugin>
            </plugins>
        </build>
    Add one package at a time, build and start the bundle and see what package it complains about next.
    Alan Stewart
    Spring Roo Committer
    twitter @alankstewart

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •