Skip to main content



      Home
Home » Eclipse Projects » Buckminster dev » [buckminster-dev] Does it matter to "Buckminster" which VM is used for "c
[buckminster-dev] Does it matter to "Buckminster" which VM is used for "c [message #1690746] Mon, 30 March 2015 22:07 Go to next message
Eclipse UserFriend
<font size=3 face="sans-serif">Buckminster team, can one of you comment
on </font>
<br>
<br><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=463510"><font size=3 color=blue><b><u>Bug&nbsp;463510</u></b></font></a><font size=3>
- Should we use Java 7 in the infrastructure signing service? (Is currently
Java 6). </font>
<br>
<br><font size=3 face="sans-serif">If I recall, Buckminster does it's own
&quot;repack&quot; and &quot;pack&quot; so perhaps it does not matter much
which VM is used for central signing service ... that is, do you always
specify &quot;-nopack&quot; to central service? Or, only for things like
&quot;features&quot; and &quot;source bundles&quot; but otherwise do you
let the central service do the &quot;repack&quot;? </font>
<br>
<br><font size=3 face="sans-serif">Also, do you recognize &quot;eclipse.inf&quot;
options in a bundle? That is, do you recognize </font>
<br><font size=3>jarprocessor.exclude.pack </font><font size=3 face="sans-serif">=true</font>
<br><font size=3 face="sans-serif">and skip (re) packing that bundle? </font>
<br>
<br><font size=3 face="sans-serif">I'm trying to help those that have trouble
getting pack200 to &quot;work right&quot; and therefore turn it off for
all their bundles. </font><font size=3><br>
</font><font size=3 face="sans-serif"><br>
Thanks for any comments and confirmation. </font>
<br>
<br>
Re: [buckminster-dev] Does it matter to &quot;Buckminster&quot; which VM is used for &qu [message #1690764 is a reply to message #1690746] Tue, 31 March 2015 02:55 Go to previous message
Eclipse UserFriend
Hi David,

It's correct that Buckminster does it's own pack and repack instead of using an external executable but we still execute
the same underlying code. I.e. running Buckminster with Java 6 or Java 7 will make a difference. Buckminster's pack
logic isn't mandatory though. It must be enabled by passing the property site.pack200=true to the build.

Buckminster will recognize the eclipse.inf and the jarprocessor.exclude.pack directive. See the following link for a
full list of options that the jarprocessor will recognize:

http://git.eclipse.org/c/buckminster/buckminster.git/tree/org.eclipse.buckminster.jarprocessor/src/org/eclipse/buckminster/jarprocessor/JarInfo.java

- thomas

On 2015-03-31 04:07, David M Williams wrote:
> Buckminster team, can one of you comment on
>
> *_Bug 463510_* <https://bugs.eclipse.org/bugs/show_bug.cgi?id=463510>- Should we use Java 7 in the infrastructure
> signing service? (Is currently Java 6).
>
> If I recall, Buckminster does it's own "repack" and "pack" so perhaps it does not matter much which VM is used for
> central signing service ... that is, do you always specify "-nopack" to central service? Or, only for things like
> "features" and "source bundles" but otherwise do you let the central service do the "repack"?
>
> Also, do you recognize "eclipse.inf" options in a bundle? That is, do you recognize
> jarprocessor.exclude.pack =true
> and skip (re) packing that bundle?
>
> I'm trying to help those that have trouble getting pack200 to "work right" and therefore turn it off for all their bundles.
>
> Thanks for any comments and confirmation.
>
Previous Topic:[buckminster-dev] External Buckminster update site restored
Next Topic:Fwd: Re: is git.auto.fetch implemented at all?
Goto Forum:
  


Current Time: Sat Jul 05 12:31:39 EDT 2025

Powered by FUDForum. Page generated in 0.05405 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top