[
http://issues.ops4j.org/browse/PAXCONSTRUCT-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12287#action_12287
]
Stuart McCulloch commented on PAXCONSTRUCT-108:
-----------------------------------------------
That's correct - the bundle manifest is created by BND when the bundle is
built, which is done in the packaging phase - so you need to at least do "mvn
package" to regenerate the manifest. We could perhaps add another goal to
re-generate the manifest without building the bundle, but I'd like to
understand why such an option would be necessary. Can you explain your use-case?
> MANIFEST.MF file is not refreshed (or even recreated after a delete) by the
> command mvn org.ops4j:maven-pax-plugin:compile
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: PAXCONSTRUCT-108
> URL: http://issues.ops4j.org/browse/PAXCONSTRUCT-108
> Project: Pax Construct
> Issue Type: Bug
> Components: maven-pax-plugin
> Affects Versions: 1.4
> Reporter: Charles Moulliard
> Assignee: Stuart McCulloch
>
> The content of the file MANIFEST.MF is not refreshed (or even recreated after
> a delete) by the command mvn org.ops4j:maven-pax-plugin:compile
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general