maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mario Krizmanic (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MNG-5957) Configuration within lifecycle phase
Date Mon, 04 Jan 2016 22:12:39 GMT

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

Mario Krizmanic updated MNG-5957:
---------------------------------
    Description: 
The lifecycle phase can be configured as a comma-separated list of plugins specified with
the following data: {code}<groupId>:<artifactId>:<version>:<goal>{code}
that are not enough for my plugin.

My plugin has to reconfigure the default lifecycle using other plugins with dedicated configuration
different from their defaults'.

So, I'd propose to enhance the lifecycle phase parsing to support additional configuration
as: {code}<groupId>:<artifactId>:<version>:<goal>[<configuration>]{code}

Finally, the components.xml would support configurations like: {code:xml}<component-set>
    <components>
        <component>
            <role>org.apache.maven.lifecycle.mapping.LifecycleMapping</role>
            ...
            <configuration>
                <lifecycles>
                    <lifecycle>
                        <id>default</id>
                        <phases>
                            <process-resources>
                                org.apache.maven.plugins:maven-resources-plugin:resources
                            </process-resources>
                            ...
                            <install>
                                <![CDATA[
                                org.apache.maven.plugins:maven-install-plugin:install,
                                org.apache.felix:maven-bundle-plugin:install[
                                        &lt;supportedProjectTypes&gt;
                                            &lt;supportedProjectType&gt;buzz&lt;/supportedProjectType&gt;
                                        &lt;/supportedProjectTypes&gt;]]]>
                            </install>
...{code}

  was:
The lifecycle phase can be configured as a comma-separated list of plugins specified with
the following data: {code}<groupId>:<artifactId>:<version>:<goal>{code}
that are not enough for my plugin.

My plugin has to reconfigure the default lifecycle using other plugins with dedicated configuration
different from their defaults'.

So, I'd suppose to enhance the lifecycle phase parsing to support additional configuration
as: {code}<groupId>:<artifactId>:<version>:<goal>[<configuration>]{code}

Finally, the components.xml would support configurations like: {code:xml}<component-set>
    <components>
        <component>
            <role>org.apache.maven.lifecycle.mapping.LifecycleMapping</role>
            ...
            <configuration>
                <lifecycles>
                    <lifecycle>
                        <id>default</id>
                        <phases>
                            <process-resources>
                                org.apache.maven.plugins:maven-resources-plugin:resources
                            </process-resources>
                            ...
                            <install>
                                <![CDATA[
                                org.apache.maven.plugins:maven-install-plugin:install,
                                org.apache.felix:maven-bundle-plugin:install[
                                        &lt;supportedProjectTypes&gt;
                                            &lt;supportedProjectType&gt;buzz&lt;/supportedProjectType&gt;
                                        &lt;/supportedProjectTypes&gt;]]]>
                            </install>
...{code}


> Configuration within lifecycle phase
> ------------------------------------
>
>                 Key: MNG-5957
>                 URL: https://issues.apache.org/jira/browse/MNG-5957
>             Project: Maven
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 3.3.9
>            Reporter: Mario Krizmanic
>
> The lifecycle phase can be configured as a comma-separated list of plugins specified
with the following data: {code}<groupId>:<artifactId>:<version>:<goal>{code}
that are not enough for my plugin.
> My plugin has to reconfigure the default lifecycle using other plugins with dedicated
configuration different from their defaults'.
> So, I'd propose to enhance the lifecycle phase parsing to support additional configuration
as: {code}<groupId>:<artifactId>:<version>:<goal>[<configuration>]{code}
> Finally, the components.xml would support configurations like: {code:xml}<component-set>
>     <components>
>         <component>
>             <role>org.apache.maven.lifecycle.mapping.LifecycleMapping</role>
>             ...
>             <configuration>
>                 <lifecycles>
>                     <lifecycle>
>                         <id>default</id>
>                         <phases>
>                             <process-resources>
>                                 org.apache.maven.plugins:maven-resources-plugin:resources
>                             </process-resources>
>                             ...
>                             <install>
>                                 <![CDATA[
>                                 org.apache.maven.plugins:maven-install-plugin:install,
>                                 org.apache.felix:maven-bundle-plugin:install[
>                                         &lt;supportedProjectTypes&gt;
>                                             &lt;supportedProjectType&gt;buzz&lt;/supportedProjectType&gt;
>                                         &lt;/supportedProjectTypes&gt;]]]>
>                             </install>
> ...{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message