- This topic has 11 replies, 2 voices, and was last updated 16 years, 1 month ago by
.
-
Posts
-
I’ve been having some problems with 6.5 recently, but after looking at the timeline and weighing other considerations I thought to go to 6.6 rather than re-installing 6.5 yet again. The timeline says its to be released in October, which this is the last day of, any news? As for what problems I’m having, for some reason 6.5 refuses to work through our proxy anymore, gives a “407 proxy authentication required”, yes I’ve got it set up authenticate, the browsers all work through the proxy, and I’ve checked with our network security and they say that they aren’t doing any filtering by client. I’ve checked with 3 MyEclipse users and 3 straight Eclipse (Ganymede) users, and the MyEclipse users are all experiencing the same thing, but not the Ganymede users, so I was going to start with the new MyEclipse, a new workspace, and see if that made any difference. So, is 6.6 coming out today or not??
thx
MikeSo, is 6.6 coming out today or not??
MyEclipse 6.6 is currently slated for Tuesday, 11/4.
What features were you using when you ran into the proxy issue.
Any of the updates,quick update fails immediately. I can’t get upgrades nor can I install new plugins.
What feature were you trying to upgrade and which plugin are you unable to install? Can you go to MyEclipse > Installation Summary > Installation Details and paste the information here for me.
Many of the update functions won’t work, including the Quick Update that runs each time I start. I tried with a couple of JVMs I have on my system, but 1.5X and 1.6X. The new plugin I was trying to install was the TestNG plugin. The information you requested follows:
*** Date:
Monday, November 3, 2008 7:17:22 AM MST** System properties:
OS=WindowsXP
OS version=5.1
Java version=1.5.0_11*** MyEclipse details:
MyEclipse Enterprise Workbench
Version: 6.5.1 GA
Build id: 6.5.1-GA-20080715*** Eclipse details:
MyEclipse Enterprise WorkbenchVersion: 6.5.1 GA
Build id: 6.5.1-GA-20080715Eclipse Platform
Version: 3.3.3.r33x_r20080129-_19UEl7Ezk_gXF1kouft
Build id: M20080221-1800Eclipse Java Development Tools
Version: 3.3.2.r33x_r20080129-7o7jE7_EDhYDiyVEnjb1pFd7ZGD7
Build id: M20080221-1800Eclipse Plug-in Development Environment
Version: 3.3.3.r33x_r20080129-7N7M5DQVIA_6oJsEFkEL
Build id: M20080221-1800Eclipse Project SDK
Version: 3.3.3.r33x_r20080129-7M7J7LB-u3aphGW6o3_VmiVfGXWO
Build id: M20080221-1800Eclipse RCP
Version: 3.3.3.r33x_r20080129-8y8eE9UEUWI6qujeED0xT7bc
Build id: M20080221-1800Eclipse Graphical Editing Framework
Version: 3.3.2.v20080129
Build id: 20080221-1602Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-showsplash
-launcher
C:\Program Files\MyEclipse 6.5\eclipse\eclipse.exe
-name
Eclipse
–launcher.library
C:\Program Files\MyEclipse 6.5\eclipse\plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.3.R33x_v20080118\eclipse_1023.dll
-startup
C:\Program Files\MyEclipse 6.5\eclipse\plugins\org.eclipse.equinox.launcher_1.0.1.R33x_v20080118.jar
-exitdata
105c_68
-clean
-vm
C:\bea10\jdk150_11\bin\javaw.exeTestNG is not certified to run with MyEclipse. I guess that the reason why you ran into those errors.
No, it isn’t. It comes up no matter what plugin I try to install, it comes up during the MyEclipse quick update, and it comes up when I try to just do a general overall update installed software.
Ok, I started MyEclipse this morning and checked the error log, I’m showing a “Network connection problems encountered during search.” message in plugin com.tikal.eclipse.updatemanager.quickset. Unfortunately no stack trace is available for it. So, 6.6 today? 😉
Quick update here, if all projects are closed, the quick update seems to work fine….but I seldom have no projects open. These are Maven projects, if that might make a difference, and yes, I’ve got the M2Eclipse “patch” for 6.5, in my primary environment the things you have done to Maven support rendered MyEclipse useless.
I checked with the other developers on my team that are having the same problem did not install the Maven “patch”
