[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [orbit-dev] Am I misunderstanding source bundles?
|
Semi-automatic, I believe. As far as I know, the manifest.mf that is in
the source-bundle folder is used as is, with the "qualifier" being filled
in per the cvs tag that is in the map file ... all standard PDE build
stuff. And, since the code bundle and the source bundle are in the same
cvs module, once that module is tagged, then there would be two places in
the map file to update (one for code bundle, one for source bundle). As
far as I know, these two entries in map file must match, to make sense. I
believe they do, now, for jxpath.
I'm assuming they match if retrieved directly from the Orbit downloads?
That's how I got my version, which worked.
http://download.eclipse.org/tools/orbit/downloads/drops/S20081025033911/
If they match there, but not in your "build" then I'd guess something's
gone wrong with your build process. Perhaps the "sdk" version was created
at a different time than the "code" version ... and it just so happened
the cvs tag changed in between?
From:
Michael A Squillace/Austin/IBM@IBMUS
To:
Orbit Developer discussion <orbit-dev@xxxxxxxxxxx>
Date:
11/03/2008 11:04 AM
Subject:
Re: [orbit-dev] Am I misunderstanding source bundles?
The fact that the Open eclaration F3 didn't work made me suspicious so thx
for pointing out that route. It turns out that the version number in the
Eclipse-SourceBundle header does not match that of the plugin to which the
source corresponds. Is the Eclipse-SourceBundle header generated
autoamtically by Orbit releng? I simply don't recall when/how this header
is created.
--> 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/02/2008 09:20 PM
Please respond to
Orbit Developer discussion <orbit-dev@xxxxxxxxxxx>
To
Orbit Developer discussion <orbit-dev@xxxxxxxxxxx>
cc
Subject
Re: [orbit-dev] Am I misunderstanding source bundles?
I took a quick look at org.apache.commons.jxpath and it seems ok on the
surface.
I even tested it some. I put the plugin and it's corresponding source
bundle in my installation and tried using it. I know nothing about it, so
don't know how to make anything real, but created a new plugin project,
added org.apache.commons.jxpath in the manifest dependancies, and then
tried to write a Java class that used it. I could get content assist for
it's packages, and just picked some class random class ...
ContructorFuntion ... and when I pressed "F3" while on the class from
jxpath, I was given the source file version of that class.
I didn't pursue the debug case, since not sure of an easy thing to write
(ContructorFunction would not be it :) but would think it'd use the same
lookup mechanism.
Can you get the "F3" case to "find" the source you're expecting? If so,
maybe you've found a debug bug? If not, I'd guess it's your set-up,
somehow.
You might also try a similar experiment with some other bundle that has
source, just to confirm it's nothing specific to this particular one.
HTH
_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orbit-dev
_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orbit-dev