https://bugs.eclipse.org/bugs/show_bug.cgi?id=350414
This doesn't directly affect any of our products, but as we begin to support Maven
more and more, this could be a big problem for adoption of our tooling.
I'd also ask for an inventory of existing m2e extensions. My opinion is that all
plugins provided by Apache should be supported, and I'd probably add the Codehaus
plugins as well.
In my opinion, it was very bad form to release a new version that had less functionality
than the previous. While I understand there were issues with the architecture used in the
previous version, all a user sees is that there are errors in projects that used to
compile, and to fix them they need to pollute their poms with m2e crap. Or they become
plugin developers and write the extensions themselves, but where do they put them? At
least the m2e project could have some sort incubator to house the extensions people
write.
This is a big pain point when upgrading m2e and it will be an issue for users.
----- Original Message -----
Here's a few:
https://issues.jboss.org/browse/JBDS-1983 JBDS Welcome Screen
*
https://bugs.eclipse.org/bugs/show_bug.cgi?id=370119
https://issues.jboss.org/browse/JBIDE-8838 Source Features
*
https://bugs.eclipse.org/bugs/show_bug.cgi?id=374349
*
https://bugs.eclipse.org/bugs/show_bug.cgi?id=374663
*
https://bugs.eclipse.org/bugs/show_bug.cgi?id=371504
On 03/22/2012 01:48 PM, Max Rydahl Andersen wrote:
> hi guys,
>
> I'm going to eclipsecon next week and its normally a good
> place/time to get Eclipse bugzillas fixed.
>
> So if you got such in tycho, m2e, jdt, core, wtp, etc. let me know
> the bugzilla link via mail and i'll try and see
> who/what I can track down.
>
> Please send it before end of friday :)
>
> /max
>
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev