Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-dev] Discovery catalog for m2e 1.3 
So we do not publish any 1.3 specific entries to the catalog until 1.3.1
is out.

--
Regards,
Igor

On 2013-02-14 7:02 AM, Fred Bricon wrote:

RC4 build for +3 participants was yesterday. Juno SR2 RC4 staging repo
is now complete :-(
Quoting David Williams : "If you find a "bad bug" that only effects your
project, you may want to prepare work-around notes or provide a patched
feature on your project's software site repository."

So I believe having a 1.3.1 available with a proper catalog is the best
way to cope with it.


On Thu, Feb 14, 2013 at 12:47 PM, Igor Fedorenko <igor@xxxxxxxxxxxxxx
<mailto:igor@xxxxxxxxxxxxxx>> wrote:

    Can you create 1.3 catalog as a copy of 1.1 for now? We have to update
    url in m2e before we release... assuming you still plan to do 1.3
    release as part of juno sr2. Speaking of which, when is the final rc,
    btw? Are you sure you have not missed it yet? It would be pretty bad if
    we shipped 1.3 if discovery pointing at 1.1 catalog.

    --
    Regards,
    Igor


    On 2013-02-14 4:21 AM, Fred Bricon wrote:

        That's was the plan, because m2e 1.3 introduces new APIs. New m2e
        extensions leveraging these APIs *might* break, or at least not
        behave
        as expected when run with m2e < 1.3
        Now we had some build issues preventing us from  generating a new
        catalog for 1.3 and we couldn't respin before Juno SR2 RC4.
        So there's a strong chance a dedicated m2e 1.3 catalog won't be
        available for the release next week.

        Fred

        On Thu, Feb 14, 2013 at 9:18 AM, Anders Hammar
        <anders@xxxxxxxxxx <mailto:anders@xxxxxxxxxx>
        <mailto:anders@xxxxxxxxxx <mailto:anders@xxxxxxxxxx>>> wrote:

             Is there going to be a different discovery catalog for m2e
        v1.3?
             I've seen some changes by Fred in github for the discovery
        code that
             suggests so, but having used the staged m2e 1.3 I've found
        it to use
             the "old" 1.1 catalog.

             /Anders

             _________________________________________________
             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>




        --
        "Have you tried turning it off and on again" - The IT Crowd


        _________________________________________________
        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>




--
"Have you tried turning it off and on again" - The IT Crowd


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

Back to the top