| From PDE/Build to publish [message #606493] |
Sat, 21 August 2010 20:45  |
 Stephan Herrmann
Messages: 1853
Registered: July 2009 |
Senior Member |
|
|
Hi,
I just started to document the Object Teams build http://wiki.eclipse.org/OTBuilding
and it shows that we have a growing list of tasks (currently 10)
to be performed after PDE/Build has done its job.
I wonder whether this is actually the state-of-the-union or
whether PDE/Build intends to cover some of these steps, too.
Specifically, I'm working on pack200 and found no easier way
than invoking this from a shell script after the build. But apparently
I'm still doing something wrong: although I have a beautiful set of
pack.gz files, updating still seem to use the big .jars.
Do I need to tell the publisher to use the .pack.gz files? How?
Aside from the pack200 issue, our build (which has been migrated
all the way from 3.0 IIRC) works fine, I'm just wondering whether
doing more and more things outside PDE/Build is actually the trend.
And of course I wouldn't mind, if over time the number of required
workarounds would decrease, rather than keep going up, see these bugs:
* Subversive: https://bugs.eclipse.org/bugs/show_bug.cgi?id=301045 - Smarter handling of "trunk" in Subversive Fetch Factory
* PDE/UI + P2: https://bugs.eclipse.org/bugs/show_bug.cgi?id=304156 - Support version range in definition of patch feature
* P2: https://bugs.eclipse.org/bugs/show_bug.cgi?id=251888#c11 - [generator] [publisher] Meta data generator cannot handle existing meta data
- conclusion here is that cumulative metadata and categories don't play well together
And finally there's: https://bugs.eclipse.org/bugs/show_bug.cgi?id=310132 - [publisher] Publisher app + ant task should support statsURI option and generating required metadata for tracking download stats
Each of these is responsible for a little ugly workaround in the build.
best,
Stephan
|
|
|
|
Powered by
FUDForum. Page generated in 0.02271 seconds
] 
Search
Help
Register
Login
Home
