Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-dev] Configurator priorities

No, in most cases there is only one configurator for each maven plugin
goal and to keep things simple I suggest you do the same even if this
results in some code duplication between i18n and generateAsync
configurators.

--
Regards,
Igor

On 11-07-19 5:12 PM, Olivier NOUGUIER wrote:
You are (again) perfectly right, I wanted to say:
"So It's common to provide more than one configurator (GWT) for
supporting a *maven plugin*"

Given the fact that they are only differ by their BuildParticipant, then
what is the best practice for i18n and generateAsync:
- 2 generators
- 1 generator with a switch based on the execution goal to return the
right BuildParticipant.

Thank again.

On Tue, Jul 19, 2011 at 2:05 PM, Igor Fedorenko <igor@xxxxxxxxxxxxxx
<mailto:igor@xxxxxxxxxxxxxx>> wrote:

    Not sure I understand. Term "mojo" refers to a single maven plugin goal
    and m2e only allows single mapping for any given mojo, regardless how
    many times the mojo is bound to project build lifecycle. Although it is
    possible to map multiple unrelated plugin goals to the same project
    configurators, m2e will treat these as multiple unrelated mappings and
    will call the configurator for each corresponding plugin execution
    separately.

    I am not familiar with maven gwt support, but it looks like you need
    separate project configurator (and lifecycle mapping) for each of the
    goal you mentioned, i.e. "i18n", "generateAsync" and "generateAsync".

    --
    Regards,
    Igor


    On 11-07-19 12:33 PM, Olivier NOUGUIER wrote:

        Thank you Igor.
        So It's common to provide more than one configurator (GWT) for
        supporting a mojo.
        In my situation (GWT) I have some goals that I want to support:
          - compile (phase package)
          - i18n (phase process-resources)
          - generateAsync

        "i18n" and "generateAsync"z run early as they are generating
        some sources

        (phase process-resources)
        "compile" need to runs after the JDT configuration to be able to add
        GWTNature (phase package).

        So to support those goal I've had to provide 2 configurators:
        one for
        "compile" and one for "i18n" and "generateAsync".

        Could we generalize by saying that goals support of a given mojo
        have
        to/can be gathered in same configurator on the basis of their
        running
        phase ?

        Regards,
        Olivier

        On Tue, Jul 19, 2011 at 7:17 AM, Igor Fedorenko
        <igor@xxxxxxxxxxxxxx <mailto:igor@xxxxxxxxxxxxxx>
        <mailto:igor@xxxxxxxxxxxxxx <mailto:igor@xxxxxxxxxxxxxx>>> wrote:

            Configurators are invoked in the order of their
        corresponding maven
            plugin executions.

            --
            Regards,
            Igor


            On 11-07-19 1:24 AM, Olivier NOUGUIER wrote:

                hi,
                  I have the feeling that configurators providing build
                participant are
                run before the other, is it the reality ?

                --
        "Computers are useless. They can only give you answers."
                - Pablo Picasso -


                ___________________________________________________
                m2e-dev mailing list
        m2e-dev@xxxxxxxxxxx <mailto:m2e-dev@xxxxxxxxxxx>
        <mailto:m2e-dev@xxxxxxxxxxx <mailto:m2e-dev@xxxxxxxxxxx>>

        https://dev.eclipse.org/____mailman/listinfo/m2e-dev
        <https://dev.eclipse.org/__mailman/listinfo/m2e-dev>
        <https://dev.eclipse.org/__mailman/listinfo/m2e-dev
        <https://dev.eclipse.org/mailman/listinfo/m2e-dev>>

            ___________________________________________________
            m2e-dev mailing list
        m2e-dev@xxxxxxxxxxx <mailto:m2e-dev@xxxxxxxxxxx>
        <mailto:m2e-dev@xxxxxxxxxxx <mailto:m2e-dev@xxxxxxxxxxx>>

        https://dev.eclipse.org/____mailman/listinfo/m2e-dev
        <https://dev.eclipse.org/__mailman/listinfo/m2e-dev>
        <https://dev.eclipse.org/__mailman/listinfo/m2e-dev
        <https://dev.eclipse.org/mailman/listinfo/m2e-dev>>




        --
        "Computers are useless. They can only give you answers."
        - Pablo Picasso -


        _________________________________________________
        m2e-dev mailing list
        m2e-dev@xxxxxxxxxxx <mailto:m2e-dev@xxxxxxxxxxx>
        https://dev.eclipse.org/__mailman/listinfo/m2e-dev
        <https://dev.eclipse.org/mailman/listinfo/m2e-dev>

    _________________________________________________
    m2e-dev mailing list
    m2e-dev@xxxxxxxxxxx <mailto:m2e-dev@xxxxxxxxxxx>
    https://dev.eclipse.org/__mailman/listinfo/m2e-dev
    <https://dev.eclipse.org/mailman/listinfo/m2e-dev>




--
"Computers are useless. They can only give you answers."
- Pablo Picasso -


_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-dev


Back to the top