I think your logic is sound. We need to stick with 1.6 until 1.7 is mainstream on the platforms we support, including Macs. Its worthwhile to be sure Kepler and Ptolemy II both compile and run properly under 1.7 now, so that if people want to use it, they can. But lets not require it at this point.<div>
<br></div><div>Matt<br><br><div class="gmail_quote">On Tue, Jul 10, 2012 at 1:27 PM, Christopher Brooks <span dir="ltr"><<a href="mailto:cxh@eecs.berkeley.edu" target="_blank">cxh@eecs.berkeley.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dear Christoph Daniel,<br>
Ptolemy II currently requires Java 1.6.<br>
At a minimum, $PTII/ptdb uses javax.swing.GroupLayout somewhere.<br>
<br>
The problem with requiring Java 1.7 is that Mac OS 10.7.4 has Java 1.6 installed as the default:<br>
<br>
bash-3.2$ java -version<br>
java version "1.6.0_33"<br>
Java(TM) SE Runtime Environment (build 1.6.0_33-b03-424-11M3720)<br>
Java HotSpot(TM) 64-Bit Server VM (build 20.8-b03-424, mixed mode)<br>
bash-3.2$ which java<br>
/System/Library/Java/<u></u>JavaVirtualMachines/1.6.0.jdk/<u></u>Contents/Home/bin/java<br>
<br>
There is a Java 1.7 prerelease for the Mac available at:<br>
<br>
<a href="http://jdk7.java.net/macportpreview/" target="_blank">http://jdk7.java.net/<u></u>macportpreview/</a><br>
<br>
So, until Java 1.7 is the default under Mac OS X, then we should probably stick to 1.6.<br>
<br>
This could change because Apple is no longer supporting Java, so Java 1.6 is probably the last Apple Java release.<br>
<br>
However, Java 1.7 for Mac OS X is still in pre-release, so I'd prefer not to add another step to the installation process.<br>
<br>
However, if Eclipse 3.8 requires Java 1.7, then we may be forced to require Java 1.7.<br>
<br>
Waiting until September to make a decision is probably best.<br>
<br>
Comments? I'm cc'ing kepler-dev, which includes many Mac users.<br>
<br>
<br>
_Christopher<br>
<br>
<br>
<br>
On 7/9/12 7:24 AM, Christoph Daniel Schulze wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Dear Christopher,<br>
<br>
the KIELER team is currently in the process of planning the switch to<br>
Eclipse 3.8 and, later, Eclipse 4.2. As part of that, we're also<br>
reconsidering to raise our Java compliance level from 1.5 to 1.7. Of<br>
course, we need to be sure that this change won't break anything for our<br>
partners.<br>
<br>
Would the Ptolemy project be fine with its KIELER components using Java<br>
1.7 features? This of course wouldn't become an issue until our visit in<br>
September, during which I plan to further improve the layout algorithms<br>
and its integration into Ptolemy.<br>
<br>
Kind regards,<br>
Christoph Daniel<br>
<br>
</blockquote>
<br>
-- <br>
Christopher Brooks, PMP University of California<br>
CHESS Executive Director US Mail: 337 Cory Hall<br>
Programmer/Analyst CHESS/Ptolemy/Trust Berkeley, CA 94720-1774<br>
ph: <a href="tel:510.643.9841" value="+15106439841" target="_blank">510.643.9841</a> (Office: 545Q Cory)<br>
home: (F-Tu) <a href="tel:707.665.0131" value="+17076650131" target="_blank">707.665.0131</a> cell: <a href="tel:707.332.0670" value="+17073320670" target="_blank">707.332.0670</a><br>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
Kepler-dev mailing list<br>
<a href="mailto:Kepler-dev@kepler-project.org" target="_blank">Kepler-dev@kepler-project.org</a><br>
<a href="http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev" target="_blank">http://lists.nceas.ucsb.edu/<u></u>kepler/mailman/listinfo/<u></u>kepler-dev</a><br>
</blockquote></div><br></div>