Bug 335064

Description Akara Sucharitakul 2011-01-21 17:18:37 EST

Build Identifier: STS 2.5.1.RELEASE, build 201011111000

The bundle classpath container successfully references the bundles in a remote repository (via cache in workspace). This allows us to develop bundles referencing those bundles in the remote repository. However, source jar files dropped into the remote repository cannot be attached preventing developers from seeing the source files we often need for debugging. In contrast, source jar files dropped in a local repository gets resolved and attached automatically in STS. But for a large project, this means the required bundles have to be explicitly copied into the developers' system to allow source level debugging.

I'm using Virgo 2.1.

Reproducible: Always

Steps to Reproduce:
1. On a separate system, configure Virgo to run a remote/hosted repository and drop application bundles and associated source bundles into the hosted directory.
2. On the developer system, configure Virgo to use that remote repository.
3. On STS, create a bundle project or a dynamic web project and convert to OSGi bundle and enable the classpath container.
4. In your project, edit the manifest and add Import-Package to reference a package in one of the bundles in the remote repo. That bundle jar should show up in the bundle classpath container.
5. Navigate to a class in the bundle, Eclipse will show the class structure and ask you to attach the source.

The expected behavior is the source code showing up as we navigate to the class (as it happens if the bundle and source bundle were in a local repository).

Please contact me (the submitter) if and when you need sample configuration files and sample code to setup test environment.