On Thu, Oct 28, 2010 at 2:54 PM, Ron Wheeler <[email protected]> wrote: > It is hard to get enthusiastic about maintaining old software that has been > replaced by better stuff that is free.
maven-eclipse-plugin works roughly 100% of the time here, but the m2eclipse plugin fails miserably with our maven project setup. And yes we tried the latest version. It always results in having to download and install vanilla eclipse. > Get Eclipse/STS and you have a much more current supported set of code and > everything that you need to develop with Maven. Meh. sounds like having a commercial stake in the project. I happen to like commandline mvn eclipse:eclipse without having to bloat my eclipse installation with unnecessary plugins—eclipse has trouble enough keeping up with the size of our projects. > You can also get training and commercial level support if you want it. > Why would anyone want to invest in older technology? Why is it older? Because you don't like command line tools? Happening to like command line tools make someone a dinosaur? Is the maven-eclipse-plugin old because it is not given any resources by sonatype which happens to maintain the m2eclipse plugin? Why bother with building a release for maven at all? Doesn't m2eclipse supplant that too? Martijn --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
