[Paolo Denti]

…
When every installation was a breeze (now we have a full forum complaining)
When everything working in eclipse, was working in myeclipse too (now maven in myeclipse is a nightmare)
When every myeclipse new version came out right after a new eclipse release (now, eclipse 3.5 final is almost coming out and we are still waiting for a compatible 3.4.2 myeclipse)
When pulse did not exist (now it is a pain in the ass)
When everything working on windows was working on os x too

Nowadays i am keeping two installations: one with eclipse+myeclipse for old projects manteinance and one simple eclipse for new projects: I am really discouraged.

[gary.heithold]

I second that notion/motion.

[Loyal Water]

paolo_denti,
If you can give us some more details about the issue that you are facing, we can help you resolve them.

Also, the 7.1.1 installer which was released last week has a patch that resolved the pulse issues our users were facing. Have you tried 7.1.1?

[Paolo Denti]

@support-nipun wrote:

paolo_denti,
If you can give us some more details about the issue that you are facing, we can help you resolve them.

Also, the 7.1.1 installer which was released last week has a patch that resolved the pulse issues our users were facing. Have you tried 7.1.1?

Hi Nipun,
sorry, maybe this is the not the right forum for my post because i am not asking for help. I was only exposing some personal general considerations about myeclipse (and eclipse too).
I have been using myeclipse for many years; myeclipse took me away from idea 4; i always loved myeclipse. Myeclipse has been one of the best dev tool i have ever used. i have been taking myeclipse to several developers and into companies.
Therefore, having been a long time user, i believe i am in the position to expose my current feelings about myeclipse.
And the feelings are bad. I have seen the general quality decreasing rapidly in the last maybe 2 years.
There are now always so many issues …
i told about installation: yes, i solved my problems but the general approach is bad: let’s say you are a new myeclipse buyer: you could die behind the installation; after hours/days you understand that 3.4.2 is not supported (you must admit that it is not very well stated … and also that you are in a huge delay about 3.4.2; 3.5 final is almost released); therefore you restart from scratch;
and let’s say that someone already told wisely suggested to avoid pulse, avoiding to waste some other hours, saying you to use the archived version.
ok, let’s start; let’s install everything. if you are on os x, the installation fails again for some strange dependencies that you will never be able to resolve. why ? because matisse cannot be installed on os x (nobody formally stated that … and the updater simply ignores it) and again several hours gone away …

or let’s say that you import an already existing maven project, this one for example, (http://learntechnology.net/examples/learntechnology-maven-jee.zip) in a 3.4.1 + 7.1.1.
you import the maven projects and you get eclipse/myeclipse errors … if you do the same under eclipse+m2eclipse you get everything correct … and so on.

but these are just examples … and the eclipse quality also went to hell (eclipse validation for example is pathetic)

i am here complaining about myeclipse problems in general; i am now in the mood of avoiding to cope again with all those kind of problems. the idea trial is on my mac now; netbeans is on my mac now; a pure eclipse 3.4.2 is on my mac now. nothing really satisfies me but, at the moment, the worst combination i have installed is eclipse+myeclipse. i will still be a myeclipse user; my subscription is expiring and i will be renewing again and again for the next years but that’s not the point; for the first time after many years i am really dissatisfied about eclipse/myeclipse

Paolo

[Riyad Kalla]

Paolo,

First let me thank you for being a MyEclipse user for so many years — we’ve worked hard to continually earn our customers business. At times there have been hickups and we’ve worked as fast as possible to correct those to minimize down time.

I’m sorry to hear about your displeasure with MyEclipse recently — we never want to hear that. Let me try and address some of the specific issues you brought up and see if any of that information helps.

Installation Problems
We definitely had a rough patch with MyEclipse installation issues in certain networked environments that we’ve since fixed all known issues too — are you still experiencing problems even with the latest MyEclipse 7.1.1 bundle on the website? I would be curious to know what was still going on to see if we have fixes in the pipeline for whatever issue you are running into.

Keeping in mind that there is no installer on the planet that will work on every setup (we saw this with our InstallAnywhere-based installers then later with our InstallShield-based installers), we now offer new “Manual Install” archives on the download page of Eclipse Classic + MyEclipse all pre-installed together for folks to use that want to install MyEclipse that way.

Eclipse 3.4.2
This is a hard situation to understand unless you’ve been on our side of the fence before. MyEclipse builds on and ships a large portion of the Tier-1 dependencies in the Eclipse ecosystem and a good number of Tier-2 dependencies. Because of this, even micro-changes that occur in a 3.4.1 > 3.4.2 release can actually break functionality in the product. Functionality is our #1 priority for customers, so we lock MyEclipse to exact patch release of Eclipse — we have to, we stopped leaving it “open ended” in the 3.x series after we saw 2 releases that got completely broken by a minor “patch release” of Eclipse (API breaks). Even though this isn’t suppose to happen, it does, and our commitment is to our users, so we have to provide the best experience we can.

With that being said, we are hard at work on MyEclipse 7.5 right now, which is built on Eclipse 3.4.2 and we’ll have a Milestone release out in May for you. Additionally, we are beginning work on MyEclipse 8.0 (based on Eclipse 3.5) that will have a Milestone out shortly after the final Eclipse 3.5 ships. That’s another policy we stopped after 4.x — which is starting work too early on a major Eclipse release and ending up with API breaks twice (once during Milestone integration and another during final GA release testing). For a small company that moves fast, it’s just too time consuming to introduce bubbles into our delivery pipeline like that — so we focus on feature development instead with that extra time instead of tracking down platform breaks multiple times.

Maven
MyEclipse integrates m2eclipse out of the box since the 6.5 release. You can actually go to Window > Prefs > MyEclipse > Maven4MyEclipse and check the box to enable all m2eclipse functionality to turn all of that on if you prefer to work with that instead of our integrated version. That allowed me to build the project you linked with the exception of a few errors that I didn’t look much further into, but it seemed like the right path of operation that you were probably wanting.

Overall I hope our 7.5 release and subsequent releases this year re-excite you in MyEclipse and we continue to provide the value that justifies the cost of the subscription to you. We will keep fighting to keep every customer we have.

[Author]

Posts