[jira] [Commented] (SLING-9922) scriptingbundle-maven-plugin: Move "metadata" mojo to another default phase

["Radu Cotescu (Jira)" <ji...@apache.org>]

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

Radu Cotescu commented on SLING-9922:
-------------------------------------

What about {{process-sources}}? In the end this is what the mojo does - it reads the project's file-system structure to determine the provided and required capabilities.

> scriptingbundle-maven-plugin: Move "metadata" mojo to another default phase
> ---------------------------------------------------------------------------
>
>                 Key: SLING-9922
>                 URL: https://issues.apache.org/jira/browse/SLING-9922
>             Project: Sling
>          Issue Type: Improvement
>          Components: Scripting
>    Affects Versions: Scripting Bundle Maven Plugin 0.2.2
>            Reporter: Konrad Windszus
>            Priority: Major
>             Fix For: Scripting Bundle Maven Plugin 0.2.4
>
>
> Currently the "metadata" mojo is bound to phase "prepare-package".
> That does not work together with the bnd-maven-plugin which generates all metadata in phase "process-classes" (https://github.com/bndtools/bnd/tree/master/maven/bnd-maven-plugin#bnd-process-goal).
> Instead I propose the following default phase "process-classes" or "compile".
> Unfortunately it will share the phase with either the htl-maven-plugin or the bnd-maven-plugin.
> This becomes obsolete once SLING-9776 is implemented.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)