[ 
http://issues.apache.org/jira/browse/FELIX-171?page=comments#action_12449130 ] 
            
Toni Menzel commented on FELIX-171:
-----------------------------------

Hi,

I just do that for junit (simple, but something to start with).

It works fine using this pom.xml:
[..]
<plugin>
        <groupId>org.apache.felix</groupId>
        <artifactId>maven-bundle-plugin</artifactId>
        <extensions>true</extensions>
        <configuration>
          <instructions>
            <Bundle-SymbolicName>${pom.artifactId}</Bundle-SymbolicName>
            <Export-Package>junit.awtui;version="3.8.1",
                         junit.extensions;version="3.8.1",
                         junit.framework;version="3.8.1",
                         junit.runner;version="3.8.1",
                         junit.swingui;version="3.8.1",
                         junit.textui;version="3.8.1"</Export-Package>
          </instructions>
        </configuration>
      </plugin>
[..]
the BND-Tool agrees, too.

But compared to a bundle from the OBR and (e.g.) from eclipse (org.junit_3.8.1 
inside of eclipse/plugins) it is different:
they do not make the javax.swing stuff appear in the import directive.

As a result the bnd-tool reports for these bundles:
 Unresolved references to [javax.swing, javax.swing.border, javax.swing.event, 
javax.swing.text, javax.swing.tree] by class(es) on the 
Bundle-Classpath[Jar:junit.jar]: 
[junit/swingui/TestSuitePanel$TestTreeCellRenderer.class, 
junit/swingui/TestRunView.class, junit/swingui/TestRunner$13.class, 
junit/swingui/CounterPanel.class, 
junit/swingui/DefaultFailureDetailView$StackEntryRenderer.class, 
junit/swingui/TestRunner$17.class, junit/swingui/TestTreeModel.class, 
junit/swingui/TestHierarchyRunView$1.class, junit/swingui/TestRunner$16.class, 
junit/swingui/TestSuitePanel$1.class, 
junit/swingui/TestSelector$TestCellRenderer.class, 
junit/swingui/DefaultFailureDetailView$StackTraceListModel.class, 
junit/swingui/TestSuitePanel.class, 
junit/swingui/DefaultFailureDetailView.class, 
junit/swingui/FailureRunView.class, junit/swingui/TestHierarchyRunView.class, 
junit/swingui/ProgressBar.class, junit/swingui/TestSelector$3.class, 
junit/swingui/TestSelector.class, junit/swingui/StatusLine.class, 
junit/swingui/TestRunner.class, junit/swingui/FailureRunView$1.class, 
junit/swingui/TestRunContext.class, junit/swingui/AboutDialog.class, 
junit/swingui/FailureRunView$FailureListCellRenderer.class]

Who makes - if it is - the mistake??

2. Where to contribute the (and possibly more) wrapping pom.xml ?
As described in the newsgroup a couple of hours ago, this work should not be 
done manually, should it?
I will have a look at that thing.

greets,
Toni




> Document process of creating bundles using bnd
> ----------------------------------------------
>
>                 Key: FELIX-171
>                 URL: http://issues.apache.org/jira/browse/FELIX-171
>             Project: Felix
>          Issue Type: Improvement
>          Components: Felix Commons
>         Environment: OSGi application development
>            Reporter: Tim Moloney
>            Priority: Trivial
>         Attachments: template-pom.xml
>
>
> Provide the list of steps required to create a library bundle by wrapping the 
> library jar using bnd (http://www.aqute.biz/Code/Bnd).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira


Reply via email to