[ 
https://issues.apache.org/jira/browse/JCRVLT-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16955848#comment-16955848
 ] 

Konrad Windszus edited comment on JCRVLT-371 at 10/21/19 8:01 AM:
------------------------------------------------------------------

For a Maven artifact an example value would be 
{{mygroup:packagename:1.0.4-SNAPSHOT=maven:com.example.mygroupid:mmyartifactId:1.0.4-SNAPSHOT:zip}}

{{maven}} would be a custom scheme being used by filevault-package-maven-plugin.


was (Author: kwin):
For a Maven artifact an example value would be 
{{mygroup:packagename:1.0.4-SNAPSHOT=maven:com.example.mygroupid:mmyartifactId:1.0.4-SNAPSHOT:zip}}

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

Reply via email to