[ 
https://issues.apache.org/jira/browse/FELIX-2692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930570#action_12930570
 ] 

Alex Blewitt commented on FELIX-2692:
-------------------------------------

Whilst updating to the latest bnd probably makes sense too (but should probably 
be a separate JIRA - Peter, care to file one?) the 'bundle' packaging type by 
Maven will put all the classes at the top level of the bundle, whereas the 
'war' type will put them in WEB-INF\classes. So even if the _wab option is 
present, it won't move the classes to the right place if the packaging type is 
'bundle'.

I fought for hours trying to get this working - in the end, I just went with a 
WAR type and then added the manifest entry by hand. There are some interplays 
on bnd not picking up an external file when it does it, and the configuration 
page is a lot more complex than it needs to be:

http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html#ApacheFelixMavenBundlePlugin%28BND%29-AddingOSGimetadatatoexistingprojectswithoutchangingthepackagingtype

Being able to use 'wab' and have it use Maven's web plugin for shifting classes 
etc. would be a lot easier.

> Support maven type 'wab' for web bundles
> ----------------------------------------
>
>                 Key: FELIX-2692
>                 URL: https://issues.apache.org/jira/browse/FELIX-2692
>             Project: Felix
>          Issue Type: New Feature
>          Components: Maven Bundle Plugin
>    Affects Versions: maven-bundle-plugin-2.0.1
>            Reporter: Alex Blewitt
>
> Given the standardisation on WABs as part of the official specification, and 
> that WARs currently don't have web data associated with them, would it make 
> sense to support a new packaging type 'wab' for Maven projects that does the 
> same as the WAR plugin, but adding metadata as well? It might need to 
> determine the difference between 'compile' and 'provided' for inclusion in 
> the 'WEB-INF/lib' subdirectory, so that the dependency information is 
> recorded but not packaged into the WAR file.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to