Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 353445

Summary:	Eclipse Virgo Tooling does not show bundles in repository/usr
Product:	[RT] Virgo	Reporter:	rshelley <ryan.shelley>
Component:	tooling	Assignee:	Project Inbox <virgo-inbox>
Status:	CLOSED INVALID	QA Contact:
Severity:	normal
Priority:	P3	CC:	eclipse, frieder.heugel, milesparker, mlippert, pasch
Version:	3.0.0.M06
Target Milestone:	---
Hardware:	Macintosh
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:
Bug Depends on:
Bug Blocks:	368783

Description rshelley

2011-07-29 16:39:09 EDT

http://www.eclipse.org/forums/index.php/t/219229/

I've added a bundle to the repository/usr, restarted Virgo, and verified that the bundle is loaded and Active in Virgo via the admin "OSGi State" page, however, the Virgo Tooling in Eclipse under the "Repository" tab of the Virgo Server doesn't show this bundle, even after refreshing the bundle list. This causes the project to not resolve the "Import-Bundle" header for the bundle in question, and the project sources show as missing a dependency unless I explicitly add the dependent JAR directly to the project. 

Screenshot of respository/usr:
http://screencast.com/t/gj3t4iGcAT

Screenshot of OSGi State:
http://screencast.com/t/FBSS4xN2

Screenshot of Virgo Tooling:
http://screencast.com/t/ax4aS6nBfbSy

On a slightly separate topic, but related, should bundles uploaded to Virgo via the admin or dropped into the pickup also be available in the Virgo Tooling "Repository" tab? I can find these bundles from the "Bundle Overview" tab, but not the "Repository" tab within Eclipse so they too can't be used to resolve dependencies.

This is on STS 2.7, Eclipse Virgo IDE 1.0.0.201106220519-M01, and Virgo 3.0.0.M06.

Comment 1 Chris Frost

2011-08-18 05:47:47 EDT

This will need to be looked in to but I can answer one question for now. The tooling only shows what is in the configured repositories. An artifact that has been deployed to Virgo may not have come from one of the repositories so won't show up in the tooling but as it's deployed and started it will show up on the Artifacts tab of the admin console.

Comment 2 Miles Parker

2012-03-20 15:26:17 EDT

(In reply to comment #1)
> This will need to be looked in to but I can answer one question for now. The
> tooling only shows what is in the configured repositories. An artifact that has
> been deployed to Virgo may not have come from one of the repositories so won't
> show up in the tooling but as it's deployed and started it will show up on the
> Artifacts tab of the admin console.

We could look into supporting that as appropriate. I'm not sure that it *would* be appropriate to use the ones defined by pickup though. That seems to me like it should be a one-way trip, i.e. I can't think of a scneario where projects really should be depending on what is simply in the pickup dir.

I think the more general case could be supported by configuring those repositories on the Runtime side if we handle bug 333958?

Comment 3 Miles Parker

2012-03-20 15:28:19 EDT

Was this supposed to have been closed as invalid, or did I just do that accidently? If the latter, please reopen.

Comment 4 Helmut

2012-08-23 05:40:59 EDT

I tested it and using   

 - Eclipse Virgo Tools	1.0.0.201207051634-SNAPSHOT (not the current Milestone M5)
 - Virgo Tomcat Server 3.5.0.RELEASE

solved the problem.

Comment 5 Miles Parker

2012-08-23 13:11:19 EDT

Great, thanks for following up Helmut.