[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [babel-dev] Re: Build process, p2 metadata
|
On 06/02/2009 10:27 AM, Gabe O'Brien wrote:
Sean,
Here is the bug where I have been tracking my woes of generating the
P2 metadata.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=274025
Oh okay, my name's all over that one! I didn't connect it because Kit
mentioned that "the p2 metadata generated by Gabe did not include any
features". I guess he meant categories.(?)
I've just added a comment there - you might need to use "-site site.xml"
When I tested my p2 generator patch (which doesn't modify the output,
just the speed), I used a command-line similar to the example in
http://wiki.eclipse.org/Equinox_p2_Metadata_Generator and the Babel
categories came out okay. (I applied the xsl massage from
https://bugs.eclipse.org/bugs/show_bug.cgi?id=256430 and installed from
a local p2 update site, so I would have noticed if the categories
weren't there.)
Aha, I just found the exact arguments, via my Launch menu.
Program to Run:
org.eclipse.equinox.p2.metadata.generator.EclipseGenerator
Program arguments:
-os ${target.os} -ws ${target.ws} -arch ${target.arch} -nl ${target.nl}
-updateSite /home/sflaniga/Download/eclipse-nls/work/eclipse/
-metadataRepositoryName "Babel language packs update site"
-reusePack200Files
VM arguments:
-Xmx256m
Hmmm. I guess you don't need "-site" after all. Still it's quite
different from the command-line you used. I used -updateSite ("the path
of a traditional update site") whereas you had -source ("a folder
containing plugins and folders"). Perhaps -updateSite uses the site.xml
but -source ignores it unless you use -site as well.
I should just Use the Source. Describing the interaction between the
Generator's CLI arguments obviously requires a programming language anyway.
--
Sean Flanigan
Senior Software Engineer
Engineering - Internationalisation
Red Hat
