Re: [m2e-dev] Discovery catalog for m2e 1.3

[Igor Fedorenko <igor@xxxxxxxxxxxxxx>]

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