You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jackrabbit.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2019/10/19 13:40:00 UTC

[jira] [Updated] (JCRVLT-371) Include Maven groupId and artifactId of each dependency in the MANIFEST.MF and the properties.xml

     [ https://issues.apache.org/jira/browse/JCRVLT-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Konrad Windszus updated JCRVLT-371:
-----------------------------------
    Summary: Include Maven groupId and artifactId of each dependency in the MANIFEST.MF and the properties.xml  (was: Include Maven groupId and artifactId of each dependency in the MANIFEST.MF)

> 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
>            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)