Hello,

i am developing a small m2 plugin for deploying portlet applications on WPS.

I have created custom packaging and it works fine with default lifecycle.
Now i would like to switch to a custom lifecycle (wps-deployment) to provide
WPS-specific naming for deployment phases.

How can tell m2 to use my lifecycle and not the default one?!

Here is my components.xml:


    <component>
      <role>org.apache.maven.lifecycle.LifecycleExecutor</role>
      <implementation>org.apache.maven.lifecycle.DefaultLifecycleExecutor
</implementation>
      <configuration>
        <lifecycles>
          <lifecycle>
            <id>wps-deployment</id>
            <phases>
              <phase>generate-deployment-scripts</phase>
              <phase>process-deployment-scripts</phase>
              <phase>copy-app-to-installables</phase>
              <phase>deploy-portlets</phase>
              <phase>wps-deploy</phase>
            </phases>
          </lifecycle>
          <lifecycle>
            <id>wps-test</id>
            <phases>
              <phase>test-phase</phase>
            </phases>
            <default-phases>
              <test-phase>org.apache.maven.plugins:maven-clean-plugin:clean
</test-phase>
            </default-phases>
          </lifecycle>
        </lifecycles>
      </configuration>
    </component>
..............................................
    <component>
      <role>org.apache.maven.lifecycle.mapping.LifecycleMapping</role>
      <role-hint>wps-legacy-portlet</role-hint>
      <implementation>
org.apache.maven.lifecycle.mapping.DefaultLifecycleMapping</implementation>
      <configuration>
        <lifecycles>
          <lifecycle>
            <id>wps-deployment</id>
            <phases>
              <wps-deploy>com.wpexperts:maven-wps-plugin:xmlaccess
</wps-deploy>
            </phases>
          </lifecycle>
        </lifecycles>
      </configuration>
    </component>
...............................................



Thanks in advance.

Bogdan Sulima.

Reply via email to