STS + Subversion?

[kmbarlow]

Hiyas...

I got all excited to try the new STS tools, got them installed, added subversion, and... crash!

Upon restart, the IDE would simply just keep recycling the splash screen. I tried both 2.0.2 and 2.1.0 and got the same problem...

Any ideas?

Thanks.

Keith

[Christian Dupuis]

Hi Keith,

there seems to be a problem with Subversive or the Eclipse SVN Team Provider Project.

After installatation and before starting please edit the bundles.info file in your sts/configuration/org.eclipse.equinox.simpleconfigurator directory. Remove the following two lines and restart:

...
org.eclipse.equinox.weaving.aspectj,1.0.0.200902241436,file:plugins/org.eclipse.equinox.weaving.aspectj_1.0.0.200902241436.jar,4,false
...
org.eclipse.equinox.weaving.hook,1.0.0.200902121956,file:plugins/org.eclipse.equinox.weaving.hook_1.0.0.200902121956.jar,4,false
...

There seems to be an incompatibility between the Equinox Weaving that STS ships and the one that gets installed when installing the team provider.

BTW. Subclipse works with no problem.

Let's get to the bottom of this. Thanks for your help. Sorry for the inconvenience.

Christian

[Andrew Eisenberg]

Hi Keith,

I don't know exactly what is going on, but it is likely something to do with AJDT's weaving service. Sometimes it gets confused when multiple versions are being installed at once.

If Christian's suggestion doesn't help, you can try the following.

If you are not using AspectJ or AJDT, then you can safely disable it. Here's how:

1. open up the file sts-2.1.0.M1/configuration/config.ini
2. remove the line that says osgi.framework.extensions=org.eclipse.equinox.weav ing.hook
3. on the line that starts osgi.bundles, remove the section that looks like
reference\:file\:org.eclipse.equinox.weaving.hook_ 1.0.0.XXXXXXX.jar@4
(where XXXXXXX is a timestamp)
4. Instead of deleting, you can comment the text out, so that it is easy to undo later.

Now restart. This should be able to get STS running again. AJDT and AspectJ will still be available, but you will be missing some of the more advanced features (such as Aspect-aware content assist and searching).

If you want to enable the weaving service (so these more advanced features are available to you), you should do the following:

1. Open up the Plugin Registry view
2. Search for the bundle org.eclipse.equinox.weaving.aspectj
3. Right click on the bundle and make sure that "Show advanced operations" is *checked*
4. "Start" the most recent version of that bundle
5. "Stop" all other versions
6. now search for the org.aspectj.weaver bundle
7. "Stop" and "Disable" *all* versions of that bundle. Instead of using that bundle, you should be using the com.springsource.org.aspectj.weaver bundle instead (this version is already in a good state, so no need to start it).
8. Now go to Preferences->JDT Weaving and click enable. Follow the prompts and restart.

(please note that this is just a manual way of doing what happens automatically when you click Preferences->JDT Weaving->Enable, but doing it this way ensures that everything happens in the right order)

Please let me know if this works for you and try to remember what you have done so that we can fix this problem in the future.

[kmbarlow]

Thanks for the quick and detailed response...

I followed your directions and I think it works just fine but I am not sure how to validate:

There were 1 thing I thought I should mention:

1.) When I disabled the org.eclipse.equinox.weaving.aspectj - I got all kinds of alarms and pop-ups. I am not sure what any of them were but after "Ok" ing all of them I was asked to reset the view and nothing crashed... I presumed this was fine since nothing crashed and I was able to complete the directions.

Other than that... I was able to re-enable the JDT Weaving and boot eclipse.

if that is the sign of success then - the procedure works!

Thanks.

Keith

[Andrew Eisenberg]

Glad to see that it works and thanks for letting us know.

The reason why you saw those errors is likely that the bundle you stopped was being used for something already and by shutting it down, the other bundles that depended on it suddenly couldn't create new objects that come from that bundle.

On restart, a different version of the bundle is used instead (the correct version), and the exceptions do not reappear.

[kmbarlow]

They did not reappear indeed...

Thanks!

Keith

[Andrew Eisenberg]

Also, see https://issuetracker.springsource.com/browse/STS-91 and https://bugs.eclipse.org/bugs/show_bug.cgi?id=275972 for more information on what is going on here. The root cause is an equinox bug that is fixed in Eclipse 3.5.

[RaduTanasa]

Using the dropins feature might help. It worked for me. Checkout the groovy plugin related problem - it's the same fix: http://forum.springsource.org/showth...359#post242359