Re: [m2e-dev] Move back default catalog to m2e?

[Fred Bricon <fbricon@xxxxxxxxx>]

I'm fine on principle with moving it back to the eclipse-m2e org, although I can't find the explanation of why it was moved out in the 1st place (https://github.com/eclipse-m2e/m2e-core/commit/b080287849453897a78336922dddd36ef2b88394). 

Maybe Igor and/or Jason can chime in.

We'll probably need Jason's approval to move it back anyway, since it belongs to the takari organization.

Moving the catalog means https://github.com/takari/m2eclipse-discovery (the maven plugin generating the catalog) should also be moved (so the supported m2e version can be updated https://github.com/takari/m2eclipse-discovery/blob/master/org.sonatype.m2e.discovery.publisher.maven-plugin/src/main/java/org/sonatype/m2e/discovery/publisher/M2eDiscoveryMetadataGeneratorMojo.java#L76)

Fred

On Tue, Jun 1, 2021 at 5:08 PM Mickael Istria <mistria@xxxxxxxxxx> wrote:

Hi all,

I see the current catalog references a takari repo.

Could we move this catalog back to eclipse-m2e GitHub organization for better consistency/tracking/discoverability from GitHub (or more specifically could we just copy it to the existing eclipse-m2e/m2e-discovery-catalog) ?

Were there some IP concerns that mandated extraction of the catalog to an external Git repo?

Thanks in advance

--

Mickael Istria

Eclipse IDE developer, for Red Hat Developers

_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/m2e-dev

--

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

And if that fails, then http://goo.gl/tnBgH5