[jira] [Resolved] (JCRVLT-350) Make all goals support parallel builds (mark as threadSafe)
[ https://issues.apache.org/jira/browse/JCRVLT-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved JCRVLT-350. Resolution: Fixed Fixed in http://svn.apache.org/r1868692. > Make all goals support parallel builds (mark as threadSafe) > --- > > Key: JCRVLT-350 > URL: https://issues.apache.org/jira/browse/JCRVLT-350 > Project: Jackrabbit FileVault > Issue Type: Wish > Components: package maven plugin >Affects Versions: package-maven-plugin-1.0.4 >Reporter: Konrad Windszus >Priority: Major > Fix For: package-maven-plugin-1.0.5 > > > There are some hints on how to achieve that in > https://cwiki.apache.org/confluence/display/MAVEN/Parallel+builds+in+Maven+3. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (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 resolved JCRVLT-371. Fix Version/s: 3.4.2 Resolution: Fixed Fixed in http://svn.apache.org/r1868686 and http://svn.apache.org/r1868687. > 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: 3.4.2, 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)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16955871#comment-16955871 ] Tobias Bocanegra commented on JCRVLT-371: - +1 > 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)
[jira] [Comment Edited] (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: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)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16955848#comment-16955848 ] Konrad Windszus commented on JCRVLT-371: 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)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16955844#comment-16955844 ] Tobias Bocanegra commented on JCRVLT-371: - what would be an example of the {{Package-Dependencies-Location}} properties? > 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)