[pde-build-dev] Problems with the Packager

["Kirby Bohling" <computerslicer23@xxxxxxxxxxx>]

I am using the Eclipse 3.2.2 baseBuilder to do my packaging.  For the most 
part I do a process that is very similar to Eclipse's.  I take my source, 
build it into a binaries.  Then I run the packagers and start to have it 
build all of the various artifacts I'm interested in.

When I use the packager, I intentionally leave all of the map files empty.  
I don't download anything.  Everything I need already exists on the 
filesystem somewhere.  I use the trick described in bug # 143854 to have 
multiple features directories.  I leave 
${tempDirectory}/${featurePaths}/features empty.  I point all the rest of 
the feature paths towards the places where the already downloaded files are 
unzipped.  I downloaded all of them when building the binaries I want to 
package.  It was nearly doubling my build time to re-download and unzip the 
files, along with wasting a tremendous amount space.  (As an aside, it'd be 
really nice if featurePaths and pluginsPath used the same delimiter, I have 
to maintain identical lists, one comma delimited and one semi-colon 
delimited due to the difference).

So in the packager.propertiers I have something like this:

featuresPath= eclipse, \
${platformDir}/eclipse-${eclipseVersion}/eclipse, \
${platformDir}/myStuff-${myVersion}/eclipse, \
# ... Probably 5 other libraries from Eclipse (GEF, Orbit plug-ins, equinox 
plug-ins).

All that works great.  Everything builds, everything works.  It's great, 
until I try and use the packaging.properties configuration to include files 
in the root.  That doesn't appear to respect absolute paths (the only docs 
on that I've been able to find refer you to the root=rootfiles config from 
build.properties in a feature, and they document that they respect absolute 
paths, I'd happily use absolute paths as I could compute them during the 
build).

I have something like:
root=startup.jar, .eclipseproduct
root.win32.win32.x86=eclipse.exe

It fails to build, despite the fact that the startup.jar and .eclipseproduct 
exist in many of the features.  So I have the build system arrange for them 
to end up in the "${tempDirectory}/eclipse" directory (where I believe the 
packager's unzipper would have put everything if I understand it correctly). 
 That isn't good enough.

When I have the build system copy them to the 
"${tempDirectory}/win32.win32.x86/eclipse" then it works (presumable, this 
would happen for each platform once I try and make this a mult-platform 
process).  I can't seem to find where the "packaging.properties" file is 
read and processed (it might be in one of the eclipse specific ant tasks, I 
haven't looked there yet).  Is it part of the unzipper process that would 
have put those files into the proper locations?  Just wondered if I missed 
something small.

Thanks,
  Kirby

_________________________________________________________________
Like the way Microsoft Office Outlook works? You’ll love Windows Live 
Hotmail. 
http://imagine-windowslive.com/hotmail/?locale=en-us&ocid=TXT_TAGHM_migration_HM_mini_outlook_0507