oz59 and marc, After spending a fair amount of time trying to get all the latest recommended J2EE plugins to work (and dealing with Eclipse 3.0 incompatibilities), I'm also switching back to Eclipse 2.1.2. Some plugins require 3.0m4, others m6, others m7, etc. Now that I'm doing J2EE work I need several plugins to work well together. So I'm waiting (with much excitement) to use Eclipse 3.0 until it's finally released.
Many plugin venders seem to be spending a lot of time/resources dealing with this 3.0 M issue while it would seem a better use of time for the Eclipse community if plugin venders could focus on just one version of Eclipse, especially since the Eclipse plugin interfaces keep changing. An alternate solution to this mess would be for Eclipse to present stable interfaces to plugin vendors after the first milestone of a release. Thanks everyone for your posts and helping to add clarity to this issue. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3822772#3822772 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3822772 ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
