Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-users] [m2e-dev] m2e 1.5./Luna M6 build

I think there was trivial code change going from 3.1.1 to 3.2.0 [1], so
you'll need to at least undo that if you want to go back to 3.1.1. I
don't think there were any other 3.2.x specific changes, but I haven't
really tried.

You can also go forward to 3.2.2 when it's released, I am using
3.2.2-SNAPSHOTs now, so I know it works ;-)

[1] http://git.eclipse.org/c/m2e/m2e-core.git/commit/?id=d3b6df656115e37a1ea4780fe4a84b10c7f0a8af

--
Regards,
Igor

On 2014-03-10, 0:04, Greg Amerson wrote:
Thanks for the update Igor.  If adopters wanted to rollback to embedded
maven 3.1.1 would it be as simple branching the m2e-core repo from the
M6 tag, then rolling back this commit?
http://git.eclipse.org/c/m2e/m2e-core.git/commit/?id=d3b6df656115e37a1ea4780fe4a84b10c7f0a8af

And then rebuilding m2e repo locally?

Thanks,
Greg


On Mon, Mar 10, 2014 at 3:15 AM, Igor Fedorenko <igor@xxxxxxxxxxxxxx
<mailto:igor@xxxxxxxxxxxxxx>> wrote:

    Forgot to mention, full build version is 1.5.0.20140309-1847

    --
    Regards,
    Igor


    On 2014-03-09, 15:12, Igor Fedorenko wrote:

        I just published m2e 1.5.0/Luna M6 build. As usual, installation
        URL and
        instructions are available on m2e download page [1]

        This build includes the new Maven profile management feature
        contributed
        to m2e by Red Hat. New embedded maven runtime which is based on
        recently
        released Apache Maven 3.2.1 is also part of this build (for
        better or
        worse, see below). There are also few bugfixes and improvements,
        you can
        see full list in bugzilla [2].

        Beware that due to Maven MNG-5591 [3], Run As Maven is effectively
        broken for multi-module projects when launch workspace resolution is
        enabled and using Maven 3.2.1. Sadly, the bug is present in m2e
        embedded
        maven runtime and we won't be able to fix it in m2e until after Luna
        because we are past Luna IP deadline already. The workaround is
        to use
        external Maven runtime different from 3.2.1.


        [1] http://eclipse.org/m2e/__download/
        <http://eclipse.org/m2e/download/>
        [2]
        https://bugs.eclipse.org/bugs/__buglist.cgi?list_id=8490933&__product=m2e&query_format=__advanced&target_milestone=1.5.__0%2FLuna%20M6
        <https://bugs.eclipse.org/bugs/buglist.cgi?list_id=8490933&product=m2e&query_format=advanced&target_milestone=1.5.0%2FLuna%20M6>

        [3] http://jira.codehaus.org/__browse/MNG-5591
        <http://jira.codehaus.org/browse/MNG-5591>


        --
        Regards,
        Igor
        _________________________________________________
        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-users mailing list
    m2e-users@xxxxxxxxxxx <mailto:m2e-users@xxxxxxxxxxx>
    https://dev.eclipse.org/__mailman/listinfo/m2e-users
    <https://dev.eclipse.org/mailman/listinfo/m2e-users>




--
Greg Amerson
Liferay Developer Tools
Liferay, Inc. www.liferay.com <http://www.liferay.com>


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



Back to the top