You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Erik Brakkee (JIRA)" <ji...@apache.org> on 2010/04/10 23:00:40 UTC
[jira] Updated: (FELIX-1571) Bundle-ClassPath without "." while
using maven-bundle-plugin in a war project confuses the plugin
[ https://issues.apache.org/jira/browse/FELIX-1571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Erik Brakkee updated FELIX-1571:
--------------------------------
Attachment: wicket-cdi.tar.gz
This is an example of a small wicket application that has a similar issue. The example as I have attached it builds and runs fine on glassfish v3.
The problem is with the Import-Package declaration. If I leave it out, then I only get 'org.wamblee' which is the package of the classes in the war.
If I use the bundle plugin to build the example (and not the war plugin), then the Import-Package declaration are completely mixed up and I even get junit dependencies, which is weird.
Definitely, some fixes and advice are necessary on how to build a hybrid web app.
> Bundle-ClassPath without "." while using maven-bundle-plugin in a war project confuses the plugin
> -------------------------------------------------------------------------------------------------
>
> Key: FELIX-1571
> URL: https://issues.apache.org/jira/browse/FELIX-1571
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-2.0.0
> Reporter: Sahoo
> Fix For: maven-bundle-plugin-2.1.0
>
> Attachments: test.zip, wicket-cdi.tar.gz
>
>
> I am using a war type project, so the packaging is governed by
> maven-war-plugin. For the OSGi meta data in the war, I am using manifest
> goal of maven-bundle-plugin in process-classes phase. Yes, I have already
> looked at the excellent examples on this use case at [1]. However, my use
> case has one difference. I don't want "." in Bundle-ClassPath. Why? Because,
> it should never be. Files at the root level of .war file is never used
> directly by class loaders in web container; WEB-INF/classes and
> WEB-INF/lib/*.jar are used instead. As soon as I remove the "." from
> Bundle-ClassPath settings, bundle plugin is confused. I don't know why "."
> is necessary for bundle plugin to generate meta data? My guess is without
> it, it does not find any classes in the target dir?
> Please see the attached test case. I want to know two things:
> 1. How to configure bundle plugin to generate Bundle-ClassPath that contains WEB-INF/classes and WEB-INF/lib/*.jar, but "." should not be part of the classpath?
> 2. How to configure bundle plugin to generate Import-Package statements for classes packaged in WEB-INF/lib/*.jar?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira