Last week, David Holmes had to do a temporary addition to refs.allowed
(used by the dependency analyzer in the profiles build) in order to get
profiles over the line (a last minute glitch caused by closed code). The
temporary addition can now be removed so I'd like to get that done
before it
Alan:
Last week, David Holmes had to do a temporary addition to refs.allowed
(used by the dependency analyzer in the profiles build) in order to
get profiles over the line (a last minute glitch caused by closed
code). The temporary addition can now be removed so I'd like to get
that done befo
Looks fine to me.
-Chris.
On 25/02/2013 14:54, Alan Bateman wrote:
Last week, David Holmes had to do a temporary addition to refs.allowed
(used by the dependency analyzer in the profiles build) in order to get
profiles over the line (a last minute glitch caused by closed code). The
temporary a
The current clone of jfx is crashing when running the HelloButton demo.
Upgrading from 7u9 to 7u15 didn't help. Using the jfxrt.jar from 7u15
works OK, but not the one built from the cloned repo. -Pete
# EXCEPTION_ACCESS_VIOLATION (0xc005)
# Problematic frame:
# V [jvm.dll+0xfb0a1]
j co
On Feb 23, 2013, at 12:12 PM, Alan Bateman wrote:
> On 23/02/2013 18:06, Martin Buchholz wrote:
>> I am actually encountering this in openjdk7 with the old build system.
>> I can repro the problem in openjdk8 with the old build system, but not the
>> new one.
>>
>> I don't know if you consider
p.s. It fails on Win but not Mac.
On 2/25/13 11:01 AM, Pete Brunet wrote:
> The current clone of jfx is crashing when running the HelloButton demo.
> Upgrading from 7u9 to 7u15 didn't help. Using the jfxrt.jar from 7u15
> works OK, but not the one built from the cloned repo. -Pete
>
> # EXCEPTI
Fair enough. It was a bump between old and new build systems, just
wanted to note it.
-s
On 2/24/13 4:05 PM, David Holmes wrote:
On 24/02/2013 4:38 AM, Steven R. Loomis wrote:
For reason or reasons unknown (probably related to the old build
system), I had this in my environment:
_JAVA_OPT
On Feb 24, 2013, at 2:54 PM, David Holmes wrote:
> On 23/02/2013 1:55 PM, Christian Thalinger wrote:
>> I talked to a lot of people about this today. What we really want is to not
>> run tests when we build. Mikael and I were looking into how we could do
>> that without gamma and there is a
Another p.s. - the build/repo info...
ant -Dhudson.jfx.job.name=8.0-controls-scrum sdk-no-docs
On 2/25/13 11:26 AM, Pete Brunet wrote:
> p.s. It fails on Win but not Mac.
>
> On 2/25/13 11:01 AM, Pete Brunet wrote:
>> The current clone of jfx is crashing when running the HelloButton demo.
>> Upg
Hi Pete:
p.s. It fails on Win but not Mac.
I did some searching on https://jbs.oracle.com/bugs/browse/JDK, but did
not find an open bug report. Maybe I am looking in the wrong bug
tracking system.
Do you have any contacts in the JavaFX teams? If so, please reach out
to them. I'm not su
Kelly,
Thanks. I think we agree.
I think we have consensus that my change is an improvement and should be
committed.
Can I haz approval?
I'm not brave enough to try to change the default for all mapfiles,
although I would support Kelly or anyone else who tries.
Martin
On Mon, Feb 25, 2013 at 9
> Using the jfxrt.jar from 7u15 works OK, but not the one built from
the cloned repo.
I don't know what Pete cloned .. but JavaFX is a mixture of native and
Java, just like
JDK and you can't mix and match the jar and the native any more than you
could
mix rt.jar from 7u13 and native libs from
Thanks Phil, That might be a useful hint. If I use the jfxrt.jar from
7u15 there are no problems but if I use the jfxrt.jar built from the jfx
controls scrum repo it fails. I am going to try building from the jfx
graphics repo. I don't know much about the jfx build and related
dependencies but K
On Sun, Feb 24, 2013 at 12:19 AM, Dmitry Samersoff <
dmitry.samers...@oracle.com> wrote:
>
> 2. Not all versions of test support == as equation. It's better to use
> single one. and I would prefer to have quotes around xmacosx and
> xwindows just for consistency. i.e.
>
> if test "x$OPENJDK_TARGET
I'm willing to let someone else on build-dev take over this change, or I
can implement some clear policy.
It seems reasonable to do:
windows => cl
solaris => cc gcc
anything else => gcc cc
With environment variables to allow experimental use of insane^Wunsupported
compilers.
Do we have consensus
Make sure the cache you're pulling from is from the matching hudson builds. If
controls is out of sync with master, then it's very likely to break and by
default the cache is populated with artifacts from master, not the scrum you're
working in.
For example if you pulled from 8.0-controls-scru
# Run the makefile with an arbitraty SPEC
On 02/25/13 14:53, Jonathan Gibbons wrote:
# Run the makefile with an arbitraty SPEC
Thanks, Jon
I filed JDK-8008944 "build-infra: clean up typos" so we don't lose track
of these. Feel free to add any more you come across.
Tim
On 26/02/2013 4:42 AM, Christian Thalinger wrote:
On Feb 24, 2013, at 2:54 PM, David Holmes wrote:
On 23/02/2013 1:55 PM, Christian Thalinger wrote:
I talked to a lot of people about this today. What we really want is to not
run tests when we build. Mikael and I were looking into how we cou
19 matches
Mail list logo
