[
https://issues.apache.org/jira/browse/JCRVLT-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16365902#comment-16365902
]
Konrad Windszus commented on JCRVLT-246:
----------------------------------------
The question is what is all considered metadata. E.g. the manifest in the
package is also metadata but it gets data from the the Maven phase
{{process-classes}} for the {{import-packages}} manifest header. So either
# this goal must be bound to a phase {{process-classes}} or later or
# the manifest would still only be generated with the {{package}} goal
> Generate metadata like filter.xml and properties.xml in dedicated goal
> ----------------------------------------------------------------------
>
> Key: JCRVLT-246
> URL: https://issues.apache.org/jira/browse/JCRVLT-246
> Project: Jackrabbit FileVault
> Issue Type: Improvement
> Components: package maven plugin
> Affects Versions: package-maven-plugin-1.0.0
> Reporter: Konrad Windszus
> Priority: Major
>
> To support better IDE integration it would be beneficial if all the metadata
> for content-packages (like filter.xml or properties.xml) would be generated
> in a dedicated goal (by default bound to phase generate-resources). That goal
> should also support m2e integration
> (http://www.eclipse.org/m2e/documentation/m2e-making-maven-plugins-compat.html).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
