This forum is now a read-only archive. All commenting, posting, registration services have been turned off. Those needing community support and/or wanting to ask questions should refer to the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor.

AnnouncementAnnouncement Module

Collapse

No announcement yet.

Tooling: Searching for bundles/libs in repo doesn't workPage Title Module

Tooling: Searching for bundles/libs in repo doesn't work

Jul 31st, 2008, 07:31 AM

Hi,

searching for bundles and libraries in the server "Bundle Rpository Browser" doesn't work for me. When I enter - for example - "org.hibernate.*" and click on "Search" both checkboxes "Bundles" and "Libraries" appear in the result list. But no bundles or libraries are displayed their. And neither Eclipse' "Error Log" nor the ".log"-file show any (helpful) messages.

I'm using the Spring IDE from the weekly update site (2.1.0.v200807302100) and the S2 Tool Suite 1.0.0.v200807252158.

Comment

1. I removed both the repository-directy and the repository.zip file from the workspace>/.metadata/.plugins/com.springsource.platform.ide.server.core folder.
- The "Last update"-notice in the Bundle Repository Browser displayed an old date (something in July, coming from the Tooling plug-ins?)

2. I executed "Update local bundle and library repository index"
- The "Last update"-notice in the Bundle Repository Browser still showed the old date
- The com.springsource.platform.ide.server.core-folder doesn't contained neither a repository-directory nor a repository.zip

3. I restarted Eclipse
- The "Last update"-notice in the Bundle Repository Browser has been updated to August, 1st (correct!)
- The search function works !

there was indeed a bug in file handling on Windows (can't delete a file if it is still in use). This has been fixed in the latest nightly build. Thanks for reporting this.

If you wipe out the folder STS will restore the repository index from a bundled copy in your install. That is why 3. worked for you. With the latest nightly you should be able to update using the link on the repository browser page.