[
https://issues.apache.org/jira/browse/ARIES-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12762549#action_12762549
]
Valentin Mahrwald commented on ARIES-15:
----------------------------------------
I agree that we should not change any of the metadata if it supplied and also
that mixed OSGi/JEE is going to be quite uncommon.
The case I had in mind above is a pure legacy JEE war that contains embedded
libraries, which happen to supply valid bundle manifests. I think this case
will become more common as more utility libraries will be packaged OSGi aware.
Here, again going with the philosophy of not changing supplied manifests, we
should be taking dependency information for the embedded library from its
manifest rather than scanning it.
> Rework RFC 66 import generation
> -------------------------------
>
> Key: ARIES-15
> URL: https://issues.apache.org/jira/browse/ARIES-15
> Project: Aries
> Issue Type: Improvement
> Reporter: Valentin Mahrwald
> Priority: Minor
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Currently, the RFC 66 WAR to WAB conversion generates import statements for
> all discovered dependencies, including those of embedded libraries.
> There are two improvements that should be made even for an initial version:
> - bundle manifests of embedded libraries should be use whenever they exist
> - imports should be generated with "resolution:=optional"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
