Issue while upgrading the GrEclipse plug-in

I upgraded my GrEclipse plug-in today to a newer version. The upgrade URL is given in this page. Since it was an upgrade, I click on Help -> Check for updates in Eclipse. Immediately I got the following error:

Cannot complete the install because of a conflicting dependency.
  Software being installed: Groovy-Eclipse Feature 2.0.0.xx-20091211-1000-e35 (org.codehaus.groovy.eclipse.feature.feature.group 2.0.0.xx-20091211-1000-e35)
  Only one of the following can be installed at once:
    JDT Core patch for Groovy-Eclipse plugin 2.0.0.xx-20091017-2200-e35 (org.codehaus.groovy.jdt.patch.feature.jar 2.0.0.xx-20091017-2200-e35)
    JDT Core patch for Groovy-Eclipse plugin 2.0.0.xx-20091211-1000-e35 (org.codehaus.groovy.jdt.patch.feature.jar 2.0.0.xx-20091211-1000-e35)
... and a lot more ...
To recover from the error, I just uninstalled the version of JDT that was conflicting. To do this, click on Help -> Install New Software and click on the "What is already installed?" link at the bottom of the dialog. You can easily locate the old JDT and uninstall it.

Comments

Andrew Eisenberg said…
Hi,

There was a problem with M1 in that if you installed it with the wrong options, you could not do a "Check for updates", This has been fixed in M2, but you must uninstall first. See the FAQ:

http://tinyurl.com/n2t292

Also, there is an Eclipse bug open for it:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=292783
12/15/2009 08:08:00 AM
Snarkiest said…
Hi nice reaading your blog
11/29/2023 11:39:00 PM
Post a Comment

Popular posts from this blog

Gotchas with DBCP

I had to make use of DB connection pool in one of the applications that I was implementing. Since I am new to Java, everyone in the team was suggesting why don't you make use of Commons DBCP. Being a fan of reuse, I decided to make use of DBCP and started reading about the parameters that are exposed so that I can customize DBCP to fit my needs. While reading through the available configuration parameters , I was thinking, "I don't need to check the connection to be bad on every borrow or return. It is sufficient if I check for being bad only when the connection is sitting idle in the pool." So I set the testWhileIdle to be true and set the validationQuery to be "SELECT 1 FROM DUAL". I was thinking that the configuration that I had was the optimal for the situation in hand. But one thing I overlooked was, the default value for the testOnBorrow is true. So the moment you set the validationQuery to be any non-null value, every connection you borrow from the po
Read more

A note on Java's Calendar set() method

Remember that the Calendar's internal fields include year, month, date, hour, minutes, seconds, milliseconds and time zone. Whenever you are calling a set() method with multiple fields, like set(year, month, date), it will not affect the rest of the fields. Remember that there is no set() method with multiple fields available to set the milliseconds. If you would like to set the milliseconds, you must use set(Calendar.MILLISECOND, value). Likewise, if you are planning to set all the fields, its a good idea to reset all the fields using clear() method. This will clear milliseconds as well. Most of the times, millisecond field may not be of interest to you. But if you are going to use the UTC milliseconds, by calling getTimeInMillis(), then make sure you set the right values for milliseconds as well.
Read more

The mysterious ORA-03111 error

Recently one of the applications that I developed started throwing exceptions, that had the following message: SQL state [72000]; error code [1013]; ORA-03111: break received on communication channel When I googled around, I couldn't come across anything useful. Sadly enough most of the sites just showed the documentation for that error, without any explanation from anyone experiencing that issues. So here you go, with the best possible explanation that I could come up with. My application sets two things on the connection that is throwing this exception: It sets the fetchSize to be 2500 rows It sets the query timeout to be 10 seconds The database server and the application are separated over a long latency network (actually there is a NetEm box that emulates the long latency between these two boxes) which has a latency characteristic of 50+/-5 milliseconds. This is the whole setup. It is important to understand how the timeout is handled by the Oracle client (in my case JDBC clien
Read more