Generic Project Configurators when lifecycle-mapping mappingId = customizable

[Scott Olcott]

I am developing a project configurator for an open source project called Jamon. While developing the configurator I have been trying to decide if it should be a generic configurator by setting generic="true" in plugin.xml. I then tried debuging this on a project that has customizable in the lifecycle-mapping plugin configuration. None of my breakpoints were ever hit. Testing this out with other generic configurators produces the same results, they are never called. Is this supposed to be the case? Do generic project configurators not get run when the mappingId is customizable? Thanks, Scott

[Scott Olcott]

I also doesn't work when I define it as a configurator in the plugin configuration. It throws a IllegalArgumentException.

Scott Olcott wrote:

I am developing a project configurator for an open source project called Jamon. While developing the configurator I have been trying to decide if it should be a generic configurator by setting generic="true" in plugin.xml. I then tried debuging this on a project that has customizable in the lifecycle-mapping plugin configuration. None of my breakpoints were ever hit. Testing this out with other generic configurators produces the same results, they are never called. Is this supposed to be the case? Do generic project configurators not get run when the mappingId is customizable? Thanks, Scott

[Igor Fedorenko-4]

There is probably no good reason to do so, but customizable lifecycle
mapping ignores generic project configurators. Please open new
enhancement request in m2e JIRA [1] if this causes problems, should be
easy to fix.

I need to understand more about IllegalArgumentException you see. Can
you provide full stack trace? And sample project that demonstrates the
problem would be even better.

[1] https://issues.sonatype.org/browse/MNGECLIPSE

--
Regards,
Igor

Scott Olcott wrote:

> I also doesn't work when I define it as a configurator in the plugin
> configuration. It throws a IllegalArgumentException.
>
>     Scott Olcott wrote:
>     I am developing a project configurator for an open source project
>     called Jamon. While developing the configurator I have been trying
>     to decide if it should be a generic configurator by setting
>     generic="true" in plugin.xml. I then tried debuging this on a
>     project that has customizable in the lifecycle-mapping plugin
>     configuration. None of my breakpoints were ever hit. Testing this
>     out with other generic configurators produces the same results, they
>     are never called. Is this supposed to be the case? Do generic
>     project configurators not get run when the mappingId is
>     customizable? Thanks, Scott
>
>
> ------------------------------------------------------------------------
> View this message in context: Re: Generic Project Configurators when
> lifecycle-mapping mappingId = customizable
> <http://www.nabble.com/Generic-Project-Configurators-when-lifecycle-mapping-mappingId-%3D-customizable-tp25933102p25934828.html>
> Sent from the Maven Eclipse - User mailing list archive
> <http://www.nabble.com/Maven-Eclipse---User-f14525.html> at Nabble.com.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Scott Olcott]

I created https://issues.sonatype.org/browse/MNGECLIPSE-1794 and attached a sample project.  There wasn't an option to create it as an enhancement so I created it as a bug ticket.

Igor Fedorenko-4 wrote:

There is probably no good reason to do so, but customizable lifecycle
mapping ignores generic project configurators. Please open new
enhancement request in m2e JIRA [1] if this causes problems, should be
easy to fix.

I need to understand more about IllegalArgumentException you see. Can
you provide full stack trace? And sample project that demonstrates the
problem would be even better.

[1] https://issues.sonatype.org/browse/MNGECLIPSE

--
Regards,
Igor

Scott Olcott wrote:
> I also doesn't work when I define it as a configurator in the plugin
> configuration. It throws a IllegalArgumentException.
>
>     Scott Olcott wrote:
>     I am developing a project configurator for an open source project
>     called Jamon. While developing the configurator I have been trying
>     to decide if it should be a generic configurator by setting
>     generic="true" in plugin.xml. I then tried debuging this on a
>     project that has customizable in the lifecycle-mapping plugin
>     configuration. None of my breakpoints were ever hit. Testing this
>     out with other generic configurators produces the same results, they
>     are never called. Is this supposed to be the case? Do generic
>     project configurators not get run when the mappingId is
>     customizable? Thanks, Scott
>
>
> ------------------------------------------------------------------------
> View this message in context: Re: Generic Project Configurators when
> lifecycle-mapping mappingId = customizable
> <http://www.nabble.com/Generic-Project-Configurators-when-lifecycle-mapping-mappingId-%3D-customizable-tp25933102p25934828.html>
> Sent from the Maven Eclipse - User mailing list archive
> <http://www.nabble.com/Maven-Eclipse---User-f14525.html> at Nabble.com.


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email