| Re: [orbit-dev] Am I misunderstanding source bundles? |
> Are you using these bundles in a PDE target? If so ... not sure what could
> be wrong, and I'm sure there's several things that could be ... but that
> would be the most surprising case, since that's the intended use of the
> Orbit bundles.
Not sure what you mean here. I'm using the bundles as dependencies in our own projects in ACTF. To take a concrete example, let's use org.apache.commons.jxpath since I bundled that one myself and I know that includes a source bundle, org.apache.commons.jxpath.source. Both of these plugins are in my eclipse installation and the former is a dependency for several plugins in our project. During a debug session, I expected that, once I stepped into jxpath code, I'd start seeing the source files in the source bundle but I get the .class file editor and the source not found message.
When I go to Window>Preferences>PDE>Target and select the source location tab, I am only permitted to enter a directory. I exploded the source bundle and pointed to that directory and still no luck. Shouldn't need to do that, but thought I'd try it anyway.
> Are you using these bundles checked out from cvs, directly into your
> workspace? If so, there is an issue I only recently became aware of. It
> has to do with "exporting" the right folders, so they have the right
> entries in the .classpath file. (hence this is an Eclipse workspace
> specific issue ... not relevant with running against a target). Details
> are in bug 248189
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=248189
No but I did import the source bundle into my workspace and got lots of errors since all of the binary dependencies were not present. Also, this version of jxpath reqiures only JDK 1.4.2 so identifiers like 'enum' are flagged as errors and I didn't bother trying to fix all of those!
> If that's not obviously it, you might debug by reading all the steps of
> putting a code and source into Orbit bundles and see if you can detect any
> discrepancies or omitted steps, and open a bug if found.
> http://wiki.eclipse.org/Orbit_Bundle_Checklist#Create_a_Source_Bundle
> http://wiki.eclipse.org/Adding_Bundles_to_Orbit
Went through this and didn't see anything obvious that I might have done wrong in packaging the source bundle.
It's just very strange - I thought that the presence of source bundles would have made attaching source much easier and its turning out not to be very intuitive. Is there another team to which I should be speaking as well?
--> Mike Squillace
IBM Human Ability and Accessibility Center
Accessibility Tools Framework (ACTF) co-technical lead
http://www.eclipse.org/actf
W:512.823.7423
M:512.970.0066
External: http://www.ibm.com/able
Internal: http://w3.ibm.com/able
David M Williams/Raleigh/IBM@IBMUS
Sent by: orbit-dev-bounces@xxxxxxxxxxx 11/01/2008 05:04 PM
|
|
