[
https://issues.apache.org/jira/browse/JCRVLT-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16955527#comment-16955527
]
Konrad Windszus commented on JCRVLT-371:
----------------------------------------
After having a 2nd though, I think adding a dedicated property for dependency
locations would be better as I won't cause any regressions. I proposed the
change in
https://github.com/apache/jackrabbit-filevault/pull/63/commits/80c3fc0c18dd7b849c4b609155ba724ea03c68ef.
> Include Maven groupId and artifactId of each dependency in the MANIFEST.MF
> and the properties.xml
> -------------------------------------------------------------------------------------------------
>
> Key: JCRVLT-371
> URL: https://issues.apache.org/jira/browse/JCRVLT-371
> Project: Jackrabbit FileVault
> Issue Type: Improvement
> Components: package maven plugin
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
> Fix For: package-maven-plugin-1.0.5
>
>
> To be able to do some static code analysis on existing packages it would be
> helpful if package dependencies would not only be given via the Package ID
> but also in a dedicated Manifest header with Maven groupId and artifactId.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
