Great work! Some questions:
* Do we have to do anything to make sure our old configurators remain available? * Will old configurators automatically be available for both m2e 1.0 and 1.1? * What happens if you have different versions of your configurator that is only installable on either juno or indigo (because of a tight dependency on JDT, for example)? Is there any way to specify this? My understanding based on previous conversations is that this isn't possible, but I just want to make sure. * If we need to make changes to existing configurators in the catalog, what's the best way of doing this? On Sat, Jun 9, 2012 at 10:09 AM, Fred Bricon <[email protected]> wrote: > Hi, > > we finally published the latest version of the m2e catalog for both m2e 1.0 > and 1.1 versions, available immediately. I would have published it yesterday > as I planned originally, but had trouble connecting to Eclipse > infrastructure. > > This new catalog adds : > * m2e-apt (annotation processing support) > : https://bugs.eclipse.org/bugs/show_bug.cgi?id=380147 (must be enabled > explicitely in the workspace preferences under Maven > Annotation > Processing) > * m2e-jdt-compiler (support for compilerId=eclipse|jdt) > :https://bugs.eclipse.org/bugs/show_bug.cgi?id=370983 > * m2e-wro4j (support for maven-wro4j-plugin) > : https://bugs.eclipse.org/bugs/show_bug.cgi?id=373129 > > Kudos to Jason Van Zyl, who allowed us to release the catalog jars directly > to Maven Central. I'll try to process/add new catalog entries next week. > > Regards, > > Fred Bricon > > -- > "Have you tried turning it off and on again" - The IT Crowd > > _______________________________________________ > m2e-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/m2e-dev > _______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
