| No source with remote repository [message #649963] |
Fri, 21 January 2011 04:00  |
Akara Sucharitakul Messages: 8 Registered: January 2011 |
Junior Member |
|
|
I'm quite impressed with the bundle classpath container adding dependencies when editing the manifest. Think you guys did a great for OSGi development.
One snag is when provisioning bundles using the remote repository, the source provided with the bundles (in source jars) are no longer available for view/debugging. Such sources are available when the bundle and source are in a local repository. It seems the remote repository does not serve source files.
Unfortunately, when developing in a large group with changing bundles we depend on, the remote repo would have been perfect without this little snag. Did I miss out anything here that would enable source visibility/auto attachment when the bundles are in the remote repo?
I'm using Virgo 2.1.release and STS 2.5.1. Thanks.
[Updated on: Fri, 21 January 2011 04:02] Report message to a moderator
|
|
|
|
| Re: No source with remote repository [message #650137 is a reply to message #649982] |
Fri, 21 January 2011 16:29  |
Akara Sucharitakul Messages: 8 Registered: January 2011 |
Junior Member |
|
|
|
Thanks very much, Martin. I can see it as both a missing feature in the repository app (being able to serve the source) as well as the tooling - unless one has already implemented the feature and the other one has not. I'll open an enhancement report for this.
|
|
|
Powered by
FUDForum. Page generated in 0.01897 seconds