[
https://issues.apache.org/jira/browse/JCRVLT-555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated JCRVLT-555:
-----------------------------------
Description:
The goal "check-signature" is automatically executed for each content-package
project by default in phase "process-classes". As
- most embedded bundles are usually build within the same Maven reactor in a
dedicated Maven module where the signature check already happened or
- the mandatory "signature" parameter is not being set
this goal should only be executed if explicitly bound to a phase.
was:The goal "analyze-classes" is automatically executed for each
content-package project by default in phase "process-classes". As the output is
currently only included in the MANIFEST.MF but not evaluated by any tool
(https://jackrabbit.apache.org/filevault/properties.html#Manifest_File), it
should only be executed if explicitly configured.
> Don't bind "check-signature" goal by default
> --------------------------------------------
>
> Key: JCRVLT-555
> URL: https://issues.apache.org/jira/browse/JCRVLT-555
> Project: Jackrabbit FileVault
> Issue Type: Improvement
> Components: package maven plugin
> Reporter: Konrad Windszus
> Priority: Major
> Fix For: package-maven-plugin-1.1.10
>
>
> The goal "check-signature" is automatically executed for each content-package
> project by default in phase "process-classes". As
> - most embedded bundles are usually build within the same Maven reactor in a
> dedicated Maven module where the signature check already happened or
> - the mandatory "signature" parameter is not being set
> this goal should only be executed if explicitly bound to a phase.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
