- This topic has 183 replies, 92 voices, and was last updated 16 years, 6 months ago by
.
-
Posts
-
@msquared wrote:
Now on the MyEclipse side of things, a 10-line change (which has no effect when M2Eclipse is not used) must be made in the deployment phase to look for this new scope attribute and filter out certain JARS.
Excellent! As I see it, this is the only feature which is currently blocking to use ME together with maven. All other problems are or can be solved individually. Dear ME support: Can you *please* make this change ASAP? If at all possible, include this in 6.0! It’s such a small change and really, I’m sick of the snide comments of my co-workers that use IDEA.
@digulla wrote:
Excellent! As I see it, this is the only feature which is currently blocking to use ME together with maven. All other problems are or can be solved individually. Dear ME support: Can you *please* make this change ASAP? If at all possible, include this in 6.0! It’s such a small change and really, I’m sick of the snide comments of my co-workers that use IDEA.
This Maven thread has the most Views and Posts of any thread in the forum (excluding the Facelets and Spring+Hibernate threads.. both of which MyEclipse now supports). I would say that makes Maven the most popular unsupported feature.
It is disappointing that MyEclipse would ignore a simple (and free) 10-line change that could enable an important element of Maven support. At least things are moving much faster in the WTP deployer http://docs.codehaus.org/display/M2ECLIPSE/Integration+with+WTP?showComments=false so maybe that will cause MyEclipse to consider doing more?
I would say that makes Maven the most popular unsupported feature.
I’ve been wondering about this as well. Some ME guy told me that they have two maven developers on the team and “they take maven very seriously” and stuff.
Still, in two years, nothing happened and that in the face of the fact that only a few small changes would make our lives much less painful. I agree, these fixes wouldn’t solve the issues perfect but hey, something that can be made to work is better than nothing at all!
Much more complex stuff (like a JSP editor with a preview mode) have been implemented (and who uses JSPs anymore, anyway? It’s dead technology! Or at least something that ought to be dead.) So I really fail to see why a couple of small features, which should take less than a week to implement with all the hints and help we’ve given, are still being ignored after two years!
Sorry, guys, this sucks 🙁
+1
And also it would be great if you support the Multiple Module Project with “Flat Project Layout”…
http://maven.apache.org/guides/mini/guide-ide-eclipse.html#Multiple%20Module%20ProjectRight now with the Maven plugin, MyEclipse only deploys jars of the current project, but not the ones defined by the dependant module 🙁
Hello support-rkalla??? Have you seen this post?
Has anyone from support read this thread in the last six months???
+1
I just spent a whole bunch of time converting an existing ant project over to maven (while learning maven in the process) and then come to figure out that it doesn’t really work w/ my favorite ide. sigh.
@grpapenhausen wrote:
+1
I just spent a whole bunch of time converting an existing ant project over to maven (while learning maven in the process) and then come to figure out that it doesn’t really work w/ my favorite ide. sigh.
Actually it (maven) does work in your ide (eclipse) either by using mvn eclipse:eclipse or the M2Eclipse maven plugin.
There are really just 2 problems
1) a critical MyEclipse feature (web deployment) does NOT work properly
2) MyEclipse developers on here show zero commitment to maven support (last posting from them was a terse “we have no maven support” over 6 months ago…not a word since that)If maven is important to you, consider WTP2 (instead of MyEclipse) since WTP actually DOES show some commitment to adding maven support:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=128851Since ME is based on WTP, this will eventually make it’s way to here but the way this issue has been handled is not very satisfactory.
I’ve had a private chat with one of the support members and he says that they are considering it and it’s an issue that comes up for every release. Alas, the feature seems to be too complex. When I argued how simple the change we need actually is, I got no reply anymore.
Plus, a webforum is no way to track bugs/feature requests. That’s something I would expect from a garage company. Plus I’d like to see some commitment (like a list of features which are planned for the next release and their status plus a way to give feedback for that) but apparently, Genuitec loves to surprise their customers.
I’ve started a new thread asking whether a forum is the right way to track bugs. If you agree or disagree, please leave your message there.
Guys 6.0 is finally out the door, which means 6.1 planning meetings will start probably next week. I am going to pitch Maven2 until I’m blue in the face.
I privately confirmed with one manager this morning that the work has been stymied by technical requirements that aren’t meant yet that are taking longer than thought to get into place so the “Maven 2 Support” can get finished.
So I *know* work has gotten done and is planned in that vein, but I also know that at the end of the day you guys just want support for it. So I’ll keep doing what I can.
Riyad,
Thank you. Please keep us posted of any new developments and don’t hesitate to ask when you (or one of your developers) needs help or information. Sometimes, an insurmountable problem has already been solved by someone else 🙂
@support-rkalla wrote:
Guys 6.0 is finally out the door, which means 6.1 planning meetings will start probably next week. I am going to pitch Maven2 until I’m blue in the face.
That’s great.
Maven2 integration is actually the ONLY showstopper preventing us using ME in our projects,
– and the reason that we didn’t extend most of our ME licenses the last year or so..A new ME 6.1 with good Maven2 integration definitely will result in our team switching back to ME!
@keb wrote:
@support-rkalla wrote:
Guys 6.0 is finally out the door, which means 6.1 planning meetings will start probably next week. I am going to pitch Maven2 until I’m blue in the face.
That’s great.
Maven2 integration is actually the ONLY showstopper preventing us using ME in our projects,
– and the reason that we didn’t extend most of our ME licenses the last year or so..A new ME 6.1 with good Maven2 integration definitely will result in our team switching back to ME!
For us the same – we won’t buy ME until Maven2 Support is done.
:P.
