JBDS 2.1 Mac OSX 10.6.2 Update Fails

[mdesignz]

Upgraded from JBDS 2.0 to 2.1. Now JDBS anounces that updates are available, but when it attempts to update the following error results:

An error occured while collecting items to be installed. No repository found containing org.springframework.orm/osgi.bundle/2.5.6.A

This error occurs even if I deselect all of the Spring crud, or even try to update a single item like SVN. Any suggestions?

[mareshkau]

Install just new JBDS instead of update. It's can help.

[mdesignz]

Exactly. I just did that, and everything seems to work. Thanks for the reply.

[maxandersen]

mdesignz - please report this in jira with what steps you did.

We have verified that JBDS 2.0 to 2.1 update is possible via the updatesite so if you see the opposite we want to know why.

Installing jbds fully is not what we want to force users to do.

[jeff87]

I had a similar experience as well on my Mac. If I recall I had issues with my JBoss 5.1.0.GA server starting up after running the update. Uninstalled and a new install fixed it. All has been well for me until yesterday. Now I'm getting a list of available updates that appears to list about 100+ components and none of them can be completed due to the message:

"Cannot complete the request. See the details.
Cannot find a solution satisfying the following requirements org.eclipse.ui.ide.application [1.0.101.M20090826-0800]."

[mdesignz]

That's similar to what I was seeing. I think the only thing that comes close to fixing this is to blow away the current install, and re-run the jar.

Are you able to change any of the JBoss 5.1 server settings? When I try, JBDS complains that I have the wrong port numbers specified. This has been ongoing since JBDS 2.0.

[jeff87]

Yes I am able to change my jboss settings. The only complaint I get is that it complains about the temp folder not existing if it's not there. Go create the temp folder and JBDS seems happy. Although it does seem to take quite a bit longer for my jboss server to start up through JBDS than if I just execute run.sh from a command line.

[maxandersen]

Guys, this thread is about the updatesite, you seem to be talking about JBoss AS startup issues ?

About the JBDS updatesite please create bug report with details on what version of JBDS you use, what updatesite you are using and attach files with any logging/error messages you have.

I need that info to help and fix it - thanks.

About AS, create different or use other existing thread about the subject. Thanks!

[dgolovin]

yes, it is possible, but it needs to be prepared. The only requirement is to disable all update sites that could contains updates for next major Eclipse version (for instance 3.5.0). Eclipse Update between major versions is not supported so you cannot update for example Eclipse 3.4. to 3.5.

To update from JBDS 2.1.0 to 2.1.1 you need to disable all update sites except update site for JBDS 2.1.1 and then try to do update.

That's the only way I was able to do update from 2.1.0 to 2.1.1

It might be the same for update from 2.0.0 to 2.1.0.