tag:blogger.com,1999:blog-8124028403626039195.post5525305362556807472..comments2023-05-16T12:56:11.150+02:00Comments on Grumpy Apache: The mess that is m2e connectorsJochen Wiedmannhttp://www.blogger.com/profile/09855969156780632315noreply@blogger.comBlogger12125tag:blogger.com,1999:blog-8124028403626039195.post-81953046299531612522014-01-15T13:32:03.385+01:002014-01-15T13:32:03.385+01:00And two and half years after this blog was written...And two and half years after this blog was written m2e connectors are still completely borked.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8124028403626039195.post-9816549902568112622012-06-05T06:03:54.766+02:002012-06-05T06:03:54.766+02:00I agree with you totally.
I'm so tempted to j...I agree with you totally.<br /><br />I'm so tempted to jump to Netbeans, but I can't as the JSF/SEAM supporting JBoss Tools is eclipse based and it is a very nice to have.<br /><br />But having no proper maven support after this many years is a huge minus for eclipse.Chintohttps://www.blogger.com/profile/03918297740813741100noreply@blogger.comtag:blogger.com,1999:blog-8124028403626039195.post-89484399561570466662012-04-29T15:07:29.943+02:002012-04-29T15:07:29.943+02:00m2e is one reason I jumped over to RubyMine. No ...m2e is one reason I jumped over to RubyMine. No more Java hassle, no more Maven hassle, no more broken promises from the maintainers of m2e. They've been promising to fix this for years.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8124028403626039195.post-14185576146665765822011-12-29T22:40:54.501+01:002011-12-29T22:40:54.501+01:00Another one word answer to this - IntelliJ....Another one word answer to this - IntelliJ....Mark Pollackhttps://www.blogger.com/profile/03475995335411875143noreply@blogger.comtag:blogger.com,1999:blog-8124028403626039195.post-15100304589107199922011-12-03T21:32:23.068+01:002011-12-03T21:32:23.068+01:00I'm the same "anonymous" as previous...I'm the same "anonymous" as previous post : here is a confirmation of my understanding : http://wiki.eclipse.org/M2E_plugin_execution_not_coveredAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-8124028403626039195.post-20885188339446814802011-10-21T15:45:04.753+02:002011-10-21T15:45:04.753+02:00Thanks for writing this. I'd just spent sever...Thanks for writing this. I'd just spent several months evaluating Maven when Indigo came out. I was still uncertain about it. When I figured out just how dumb this was, Indigo made up my mind: no Maven for me - not if I can help it. Not that it's Maven's fault, per se - but I don't care whose fault it is. A serious dope-slap is in order for the m2e folks.Ed Staubhttps://www.blogger.com/profile/17857527820125368004noreply@blogger.comtag:blogger.com,1999:blog-8124028403626039195.post-8606168497101164782011-10-20T13:21:56.459+02:002011-10-20T13:21:56.459+02:00I've spent a day trying M2E both without and w...I've spent a day trying M2E both without and with the JAXB connector, with Indigo. It is 100% useless. We have dozens of projects with jaxb and web services source generation. Even with the jaxb connector I cannot repeatably get the generated sources to go on the classpath, so that the Java builder sees them. The only way is to manually run a Maven compile, then every time you do a clean you start again.<br />Our projects build all day, every day from the command line, but the Eclipse situation is worse than hopeless. There's no prospect of pursuading the team to switch from Ant to Maven, entirely because of the Eclipse nightmare.<br />All of this was after adding an ass-ton of verbosity to the pom to deal with the lifecycle mapping thing.LordMhttps://www.blogger.com/profile/07578743529459836478noreply@blogger.comtag:blogger.com,1999:blog-8124028403626039195.post-77731092594198737802011-09-27T23:47:21.229+02:002011-09-27T23:47:21.229+02:00I've tried to raise many of the same concerns ...I've tried to raise many of the same concerns on the m2e-users list. Although I believe the m2e developers are listening, fundamentally the decision has been made and sadly the policy line is: it's not going to be reversed. I'm still just baffled by this decision.<br /><br />For me, points 2 and 3 of your final summary invalidate the whole connector concept. If plugins behave badly, fix them. There's just no need to demand a whole new integration layer between Maven and Eclipse and inconvenience the world and his dog in the process.Joenoreply@blogger.comtag:blogger.com,1999:blog-8124028403626039195.post-15104848690934440652011-08-29T10:33:29.740+02:002011-08-29T10:33:29.740+02:00What the fork?! Installed NetBeans 7, checking out...What the fork?! Installed NetBeans 7, checking out project ... Wait, you're telling me, it already has a Subversion connector, built-in?<br /><br />Let Netbeans scan for projects? Yes.<br />What? You've found all generated source packages of the Maven plugin, without any fail? What are you, a miracle?<br /><br />Why do I even bother with Eclipse?<br /><br />Can't jump ship now, two days before vacation and leaving three busy guys behind. But ... tempting it is :)Anonymoushttps://www.blogger.com/profile/09877884281633211285noreply@blogger.comtag:blogger.com,1999:blog-8124028403626039195.post-5635062592799190962011-08-28T11:18:18.380+02:002011-08-28T11:18:18.380+02:00netbeans in general relies more heavily on maven t...netbeans in general relies more heavily on maven tiself to do the build. There is no netbeans-only build/project infrastucture, only the compiler sometimes outputs changed class files. For source generating maven plugin, it assumes them all to reside in target/generated-sources/FOO where FOO is typically the plugin name and in most cases it's the default location for the generated sources to appear.<br />In general NetBeans project philosophy is radically different from Eclipse one's..mkleinthttps://www.blogger.com/profile/10220831615555095510noreply@blogger.comtag:blogger.com,1999:blog-8124028403626039195.post-20971776520370234542011-08-28T10:23:15.413+02:002011-08-28T10:23:15.413+02:00I can only tell that the NetBeans plugin has no id...I can only tell that the NetBeans plugin has no idea of connectors, them beeing Eclipse plugins.Jochen Wiedmannhttps://www.blogger.com/profile/09855969156780632315noreply@blogger.comtag:blogger.com,1999:blog-8124028403626039195.post-32697495126333010892011-08-28T10:15:26.106+02:002011-08-28T10:15:26.106+02:00And I thought it was just me. My team is half on E...And I thought it was just me. My team is half on Eclipse 3.7 (Indigo) and half on 3.6 - and yes, the 3.7 problems tab is filled with "lifecycle configuration" complaints from m2e.<br />It reminds me that for a long time the Maven community suffered from ill-written POMs and crappy bundles of libraries even in the most important repositories. Then Sonatype came along and cleaned up the mess, with enormous effort, with enormous effect on the usability of Maven as a whole.<br />So, there was definitely hope Sonatype would do the same for the m2e plugin, when they took responsibility (in what appeared as an unfriendly overtake). <br />In retrospect, the announcement of merging the plugin into Eclipse should've been a warning sign. Who knows what committee deemed it reasonable to impose a "lifecycle configuration tax" on any Maven plugin ever written?<br />What now? How's it going with NetBeans? Does it suffer from the same - or more counter-productive other problems? Or would it welcome my (server-) project with arms wide open?Anonymoushttps://www.blogger.com/profile/09877884281633211285noreply@blogger.com