- This topic has 12 replies, 3 voices, and was last updated 21 years, 3 months ago by
.
-
Posts
-
Just installed MyEclipse. In either the Java or MyEclipse perspectives when I right click on a directory and select the “Team” menu item all it shows is “Apply Patch”. My CVS perspective is working properly and I’ve verified the CVS connection.
Do I have to install some patch in order to use CVS?
Do I have to install some patch in order to use CVS?
No, MyEclipse does absolutely nothing with the Team functions at all. This is most likely an installation problem. What is your platform, Eclipse version and build id (Help > About Eclipse Platform)? Was this a clean Eclipse installation, or have you installed other plugins into it? What is your MyEclipse version? What JDK are you running?
–Scott
MyEclipse SupportHere’s the build info:
Version: 2.1.1
Build id: 200306271545
MyEclipse v 2.5.0 enterprise workbenchI’m running on Win2000 with JDK 1.4.2. It was a clean install and I have no other plugins. (I also still have the previous Eclipse 2.1 installation on the machine too and it doesn’t have any problem with the Team function.)
The Team preferences seem OK in MyEclipse. The CVS perspective seems fine too. Maybe this is a 2.1.1 issue, but I can’t start up 2.1.1 without the MyEclipse plugins now.
but I can’t start up 2.1.1 without the MyEclipse plugins now.
Not without installing MyEclipse, but you can do that easily enough by running our uninstaller. Would you try this and see if the Team functions in Eclipse itself are there once you’ve uninstalled MyEclipse?
Also, could you have inadvertanly installed one of the smaller Platform or JDT only builds of 2.1.1, instead of the full one? How may plugins in the Eclipse plugins directory do you have that are named org.eclipse.pde.*? There should be 7.
Is your 2.1 installation of Eclipse also running on JDK 1.4.2? The reason I ask is that this distribution is so new that there may be issues with it. I believe someone posted an issue with the Eclipse debugger functionality working properly with this release, for example.
–Scott
MyEclipse SupportHi,
FWIW, I’m also running MyEclipse under JDK 1.4.2, and I haven’t noticed any problems like this. I just verified that I get the normal items in the Team menu, and I was able to do a “Synchronize With Repository” without problems. (The repository was cvs.apache.org if it makes a difference.)
— Laura
Laura,
FWIW, I’m also running MyEclipse under JDK 1.4.2, and I haven’t noticed any problems like this.
It’s worth quite a bit, actually. Please let us know if you notice any exceptions thrown when launching servers for debugging or anything along those lines too. If we don’t hear anything, we’ll assume all is well with JDK 1.4.2. Thanks for taking the time to let us know.
–Scott
MyEclipse Support“Also, could you have inadvertanly installed one of the smaller Platform or JDT only builds of 2.1.1, instead of the full one? How may plugins in the Eclipse plugins directory do you have that are named org.eclipse.pde.*? There should be 7.”
“Is your 2.1 installation of Eclipse also running on JDK 1.4.2? The reason I ask is that this distribution is so new that there may be issues with it. I believe someone posted an issue with the Eclipse debugger functionality working properly with this release, for example.”
All 7 org.eclipse.pde.* plugins are there. My 2.1 installation of eclipse has been running on 1.4.2 since that JDK was released.
This appears to be a problem with the 2.1.1 release of Eclipse. I installed it on another machine without adding MyEclipse and the Team menu item shows “Apply Patch”.
You may want to advise your customers to avoid 2.1.1 until eclipse gets that thing fixed. It’s completely broken right now as far as Team functionality is concerned.
@lwerner wrote:
Hi,
FWIW, I’m also running MyEclipse under JDK 1.4.2, and I haven’t noticed any problems like this. I just verified that I get the normal items in the Team menu, and I was able to do a “Synchronize With Repository” without problems. (The repository was cvs.apache.org if it makes a difference.)
— Laura
What version and build of Eclipse are you running? Version 2.1 doesn’t have any problems. It’s this version that has the problem
Version: 2.1.1
Build id: 200306271545@scott wrote:
Is your 2.1 installation of Eclipse also running on JDK 1.4.2? The reason I ask is that this distribution is so new that there may be issues with it. I believe someone posted an issue with the Eclipse debugger functionality working properly with this release, for example.
The issues with the debugger is a deal killer for me. I’ve been using the old Easie debugger plug-in with 2.1 and JDK 1.4.2 for several weeks now and at this point in our development schedule the last thing I need is an upgrade that breaks my tools. I’ll stick with old reliable – Eclipse 2.1 with the Easie plug-in – and give you guys and Eclipse some more time to sort things out with 2.1.1 and JDK 1.4.2.
You may want to advise your customers to avoid 2.1.1 until eclipse gets that thing fixed. It’s completely broken right now as far as Team functionality is concerned.
The problem you’re experiencing isn’t caused by just using Eclipse 2.1.1, but rather a combination of it and JDK 1.4.2. I’ve got a 2.1.1 installation that I use for testing, but with JDK 1.4.1_03. I just checked my projects and they show the usual two options for unshared projects: Apply Patch… and Share Project…
This is why I never download a Sun JDK before the first service release. 1.4.0, and 1.4.1 were both buggy at initial release. I have no reason to believe their practices have improved.
There is probably something that is causing the Team plugin to shutdown on startup. You might check the log file for a clue. It’s at <workspace>/.metadata/.log.
–Scott
MyEclipse SupportThe issues with the debugger is a deal killer for me.
Definately a problem. The issue is basically that Sun puts out a spec of what should happen and Eclipse is the first to implement it and show them that their new enhancements don’t work. At least that’s what happened with JDK 1.4.0.
I’ve been using the old Easie debugger plug-in with 2.1 and JDK 1.4.2 for several weeks now and at this point in our development schedule the last thing I need is an upgrade that breaks my tools. I’ll stick with old reliable – Eclipse 2.1 with the Easie plug-in.
Honestly, I’d never change a project team’s toolset while under the gun to deliver. If nothing else, it gives them one more excuse to not make it. 🙂 Glad to hear the EASIE plug-in is working so well for you. We had over 100K downloads of them so we know they were popular. The connectors in MyEclipse are basically the same code, but enhanced a bit for new features and deployment support.
Give you guys and Eclipse some more time to sort things out with 2.1.1 and JDK 1.4.2.
I’d call these two in combination an experimental combination, mainly because of JDK 1.4.2. Our consultants run Eclipse 2.1.1 or 2.1.0 and JDK 1.4.1 and everything works like a dream.
To mitigate project risk while you try out our products, I’d suggest a completely fresh Eclipse installation running with JDK 1.4.1. That way you can try bringing over a project and get comfortable with the new configuration without risking any deliverables on your current project.
–Scott
MyEclipse SupportOur Eclipse guru found the problem, and it isn’t due to JDK 1.4.2.
When I installed Eclipse 2.1.1/MyEclipse I imported an existing project from a workspace that I share between 2.1 and 2.1.1. Apparently the Import function doesn’t recognize a project that is under CVS control. We have an Eclipse guru here, Dave, who said that the right way to handle this is to set the -data flag to the shared workspace when Eclipse 2.1.1 is started up:
-data C:\eclipseworkspace
Now everything works. The only glitch is that I can’t run 2.1 and 2.1.1 at the same time, but there’s no reason to do this now that the Team functionality is working in 2.1.1.
Another of our developers had the same problem when he installed 2.1.1. The source code files were already under CVS control (he’d checked them out with WinCVS). When he created a new project using the new project wizzard for existing files Eclipse would only show “Apply Patch” under the Team menu. Dave, the Eclipse guru, came to the rescue again. He had him do a “Check out into” from the CVS perspective for the files that had already been checked out through WinCVS. This actually did nothing since the files were up to date in CVS, but it got Eclipse to recognize that those files were under CVS control.
Bottom Line: The way Eclipse handles Projects is maddening. They need to document how to do basic things with Projects. Their on-line help is worthless when it comes to understanding how to handle Projects. Why doesn’t the Import function work properly?
I first tried Eclipse last summer, but gave up on it because their on-line help and tutorials made working with Projects seem ridiculous. Once Dave explained to me how to ignore all the stupid things their wizzards do and how to really work with Projects in Eclipse (which is almost totally undocumented) I loved working with it.
Sorry for the false alarm, but maybe others will find this experience useful.
We have an Eclipse guru here, Dave, who said that the right way to handle this is to set the -data flag to the shared workspace when Eclipse 2.1.1 is started up:
-data C:\eclipseworkspace
<problem elided/>
Dave, the Eclipse guru, came to the rescue again.
Your Eclipse Guru is perfectly correct. He obviously has gained his Guru title by merit, rather than by default. 😉
Bottom Line: The way Eclipse handles Projects is maddening.
I’d suggest one of the fine Eclipse books that are now coming to market over the online documentation. There’s a review of “Eclipse In Action” posted on this site, off the News and Updates page. It will save you a ton of aggravation.
Sorry for the false alarm, but maybe others will find this experience useful.
To paraphrase Hillary: If it saves only one child, isn’t it worth it. 😉
Glad you’re up and running! By the way, keep Dave!
–Scott
MyEclipse Support
