Review request : RT-37483 : [Embedded] null pointer exception in HelloListView
Daniel, Please review the proposed fix for https://javafx-jira.kenai.com/browse/RT-37483 Details in the jira. Thanks, Rafi
New alias for hg commit notifications?
It has been suggested that we create a new alias for Mercurial (hg) commit notifications -- perhaps openjfx-chan...@openjdk.java.net -- rather than sending all of them to the discussion alias. This will facilitate e-mail filtering as well as allow people to opt in or out of getting these notifications separately from being on the discussion alias. What do others think? -- Kevin
hg: openjfx/8u-dev/rt: RT-37668 FilteredList reports a size of zero until a Predicate is supplied.
Changeset: c367a3e860f2 Author:Martin Sladecek martin.slade...@oracle.com Date: 2014-06-24 15:35 +0200 URL: http://hg.openjdk.java.net/openjfx/8u-dev/rt/rev/c367a3e860f2 RT-37668 FilteredList reports a size of zero until a Predicate is supplied. ! modules/base/src/main/java/javafx/collections/transformation/FilteredList.java ! modules/base/src/test/java/javafx/collections/FilteredListTest.java
Re: New alias for hg commit notifications?
I don't see a down side to this other than people will have to subscribe to the new list get the notifications that they were seeing before (or could / should / can we see the new list?) Steve On 2014-06-24, 9:34 AM, Kevin Rushforth wrote: It has been suggested that we create a new alias for Mercurial (hg) commit notifications -- perhaps openjfx-chan...@openjdk.java.net -- rather than sending all of them to the discussion alias. This will facilitate e-mail filtering as well as allow people to opt in or out of getting these notifications separately from being on the discussion alias. What do others think? -- Kevin
Re: New alias for hg commit notifications?
+1 -- best regards, Anthony On 6/24/2014 5:34 PM, Kevin Rushforth wrote: It has been suggested that we create a new alias for Mercurial (hg) commit notifications -- perhaps openjfx-chan...@openjdk.java.net -- rather than sending all of them to the discussion alias. This will facilitate e-mail filtering as well as allow people to opt in or out of getting these notifications separately from being on the discussion alias. What do others think? -- Kevin
hg: openjfx/8u-dev/rt: RT-37594: Make lens build optional
Changeset: 1f068eb07b58 Author:ddhill Date: 2014-06-24 09:50 -0400 URL: http://hg.openjdk.java.net/openjfx/8u-dev/rt/rev/1f068eb07b58 RT-37594: Make lens build optional Reviewed-by: kcr ! build.gradle ! buildSrc/armv5sf.gradle ! buildSrc/armv6hf.gradle ! buildSrc/armv6sf.gradle ! buildSrc/armv7hf.gradle ! buildSrc/armv7sf.gradle ! buildSrc/x86egl.gradle
Re: New alias for hg commit notifications?
+1 I was filtering these anyway to a separate mail folder. Werner On 24.06.2014 15:34, Kevin Rushforth wrote: What do others think?
Re: New alias for hg commit notifications?
Sounds good. This would be consistent with the various jdk forests .. -phil. On 6/24/14 6:34 AM, Kevin Rushforth wrote: It has been suggested that we create a new alias for Mercurial (hg) commit notifications -- perhaps openjfx-chan...@openjdk.java.net -- rather than sending all of them to the discussion alias. This will facilitate e-mail filtering as well as allow people to opt in or out of getting these notifications separately from being on the discussion alias. What do others think? -- Kevin
review for Ensemble @conditionalFeature additions
Kevin, Lisa, et al. https://javafx-jira.kenai.com/browse/RT-37699 from the Jira: review at http://cr.openjdk.java.net/~ddhill/RT-37699/ http://cr.openjdk.java.net/%7Eddhill/RT-37699/ Note: it may be obvious but. apps/samples/Ensemble8/src/generated/java/ensemble/generated/Samples.java is generated, and needs to be done to include the new tags. -- David Hill david.h...@oracle.com Java Embedded Development There cannot be a crisis next week. My schedule is already full. -- Henry Kissinger (1923 - )
hg: openjfx/8u-dev/rt: 4 new changesets
Changeset: ec5229ab1cbe Author:lisa.se...@oracle.com Date: 2014-06-19 09:11 -0400 URL: http://hg.openjdk.java.net/openjfx/8u-dev/rt/rev/ec5229ab1cbe imported patch minimize Changeset: bc24edfe5b27 Author:lisa.se...@oracle.com Date: 2014-06-19 09:59 -0400 URL: http://hg.openjdk.java.net/openjfx/8u-dev/rt/rev/bc24edfe5b27 Automated merge with ssh://jfxsrc.us.oracle.com//javafx/8u/dev/jfx/rt Changeset: ab997a0b1aeb Author:lisa.se...@oracle.com Date: 2014-06-24 10:22 -0400 URL: http://hg.openjdk.java.net/openjfx/8u-dev/rt/rev/ab997a0b1aeb Automated merge with ssh://hg.openjdk.java.net/openjfx/8u-dev/rt Changeset: 5f21a4b78019 Author:lisa.se...@oracle.com Date: 2014-06-24 13:14 -0400 URL: http://hg.openjdk.java.net/openjfx/8u-dev/rt/rev/5f21a4b78019 [TEST-ONLY] Fix for RT-37377 [Monocle] Add unit test for modality Reviewed by dblaukopf + tests/system/src/test/java/com/sun/glass/ui/monocle/ModalDialogTest.java
[8u40] Review request for RT-37639: Gtk: dead keys don't work on European keyboard layouts
Hi Alexander, Steve, Please review the fix: https://javafx-jira.kenai.com/browse/RT-37639 -- best regards, Anthony
hg: openjfx/8u-dev/rt: [TEST-ONLY] Add missing import statements to fix broken test.
Changeset: 254ca5050243 Author:lisa.se...@oracle.com Date: 2014-06-24 13:43 -0400 URL: http://hg.openjdk.java.net/openjfx/8u-dev/rt/rev/254ca5050243 [TEST-ONLY] Add missing import statements to fix broken test. ! tests/system/src/test/java/com/sun/glass/ui/monocle/ModalDialogTest.java
hg: openjfx/8u-dev/rt: RT-37699: fix conditionalFeatures tags for Ensemble samples
Changeset: 17b9a338fedb Author:ddhill Date: 2014-06-24 14:03 -0400 URL: http://hg.openjdk.java.net/openjfx/8u-dev/rt/rev/17b9a338fedb RT-37699: fix conditionalFeatures tags for Ensemble samples Reviewed-by: kcr, kselle ! apps/samples/Ensemble8/src/generated/java/ensemble/generated/Samples.java ! apps/samples/Ensemble8/src/samples/java/ensemble/samples/charts/area/audio/AudioAreaChartApp.java ! apps/samples/Ensemble8/src/samples/java/ensemble/samples/charts/bar/audio/AudioBarChartApp.java ! apps/samples/Ensemble8/src/samples/java/ensemble/samples/language/swing/SwingInteropApp.java ! apps/samples/Ensemble8/src/samples/java/ensemble/samples/media/advancedmedia/AdvancedMediaApp.java ! apps/samples/Ensemble8/src/samples/java/ensemble/samples/media/alphamediaplayer/AlphaMediaPlayerApp.java ! apps/samples/Ensemble8/src/samples/java/ensemble/samples/media/audioclip/AudioClipApp.java ! apps/samples/Ensemble8/src/samples/java/ensemble/samples/media/overlaymediaplayer/OverlayMediaPlayerApp.java ! apps/samples/Ensemble8/src/samples/java/ensemble/samples/media/streamingmediaplayer/StreamingMediaPlayerApp.java
RE: JavaFX at JavaOne 2014
Yes, apologies for that link, please ignore it, I only read the first part of that article and should have vetted it more closely before relaying. I am academically curious about the concept of ART though, whether JavaFX works with it and if it is better to use a VM style runtime or AOT style variant when targeting deployment of JavaFX to mobile devices. I guessing the current JavaFX Android port would just work out of the box with ART because it is targeting the Dalvik runtime and as far as I understand ART will just take the Dalvik bytecode and compile it to the native device code when an app is installed on the device. -Original Message- From: Scott Palmer [mailto:swpal...@gmail.com] Sent: Monday, June 23, 2014 5:46 PM To: John Smith Cc: Herve Girod; Pedro Duque Vieira; OpenJFX Mailing List Subject: Re: JavaFX at JavaOne 2014 That first article was so wrong about nearly everything mentioned in it that it made me want to vomit. On Jun 23, 2014, at 2:31 PM, John Smith john_sm...@symantec.com wrote: I don't know much about Android, but does it have to be a VM, or could you use ART or an ART equivalent: http://www.extremetech.com/computing/170677-android-art-google-finally-moves-to-replace-dalvik-to-boost-performance-and-battery-life https://source.android.com/devices/tech/dalvik/art.html John
hg: openjfx/8u-dev/rt: 2 new changesets
Changeset: 6ade29ec8e2c Author:snorthov Date: 2014-06-24 15:08 -0400 URL: http://hg.openjdk.java.net/openjfx/8u-dev/rt/rev/6ade29ec8e2c INTELLIJ ONLY: fix project files to use tests instead of rt-tests ! .idea/modules.xml ! .idea/rt-closed.iml - .idea/rt-tests.iml + .idea/tests.iml Changeset: e656dca9963e Author:snorthov Date: 2014-06-24 15:08 -0400 URL: http://hg.openjdk.java.net/openjfx/8u-dev/rt/rev/e656dca9963e ECLIPSE ONLY: fix project files to use tests instead of rt-tests ! .project
hg: openjfx/8u-dev/rt: ECLIPSE ONLY: fix project files to use tests instead of rt-tests
Changeset: 55cd83185bb8 Author:snorthov Date: 2014-06-24 15:41 -0400 URL: http://hg.openjdk.java.net/openjfx/8u-dev/rt/rev/55cd83185bb8 ECLIPSE ONLY: fix project files to use tests instead of rt-tests ! tests/.project
hg: openjfx/8u-dev/rt: ECLIPSE ONLY: restore project file of rt
Changeset: 4fd65ab4dff8 Author:snorthov Date: 2014-06-24 15:43 -0400 URL: http://hg.openjdk.java.net/openjfx/8u-dev/rt/rev/4fd65ab4dff8 ECLIPSE ONLY: restore project file of rt ! .project
hg: openjfx/8u-dev/rt: RT-37530: [Accessibility] Support JAWS
Changeset: 059dc6af444f Author:Felipe Heidrich felipe.heidr...@oracle.com Date: 2014-06-24 13:59 -0700 URL: http://hg.openjdk.java.net/openjfx/8u-dev/rt/rev/059dc6af444f RT-37530: [Accessibility] Support JAWS ! modules/graphics/src/main/native-glass/win/ViewContainer.cpp
hg: openjfx/8u-dev/rt: RT-37609: [Accessibility, JAWS] Enhanced text support for JAWS
Changeset: 2785fc0430ae Author:Felipe Heidrich felipe.heidr...@oracle.com Date: 2014-06-24 14:14 -0700 URL: http://hg.openjdk.java.net/openjfx/8u-dev/rt/rev/2785fc0430ae RT-37609: [Accessibility, JAWS] Enhanced text support for JAWS ! modules/graphics/src/main/java/com/sun/glass/ui/win/WinAccessible.java ! modules/graphics/src/main/native-glass/win/GlassAccessible.cpp ! modules/graphics/src/main/native-glass/win/GlassAccessible.h
hg: openjfx/8u-dev/rt: RT-37662: [Accessibility] Define title, description, and help
Changeset: 83ec6c61e0d6 Author:Felipe Heidrich felipe.heidr...@oracle.com Date: 2014-06-24 14:37 -0700 URL: http://hg.openjdk.java.net/openjfx/8u-dev/rt/rev/83ec6c61e0d6 RT-37662: [Accessibility] Define title, description, and help Window changeset to use DESCRIPTION for UIA_LocalizedControlTypePropertyId ! modules/graphics/src/main/java/com/sun/glass/ui/win/WinAccessible.java
hg: openjfx/8u-dev/rt: [Accessibility] Define title, description, and help
Changeset: 40e76d7aedfc Author:Felipe Heidrich felipe.heidr...@oracle.com Date: 2014-06-24 15:08 -0700 URL: http://hg.openjdk.java.net/openjfx/8u-dev/rt/rev/40e76d7aedfc [Accessibility] Define title, description, and help Rename Attribute.TOOLTIP to HELP ! modules/controls/src/main/java/javafx/scene/control/Control.java ! modules/graphics/src/main/java/com/sun/glass/ui/mac/MacAccessible.java ! modules/graphics/src/main/java/com/sun/glass/ui/win/WinAccessible.java ! modules/graphics/src/main/java/javafx/scene/accessibility/Attribute.java
hg: openjfx/8u-dev/rt: RT-37610: [Accessibility, JAWS] Fix TableView
Changeset: 5b4987890bc9 Author:Felipe Heidrich felipe.heidr...@oracle.com Date: 2014-06-24 15:10 -0700 URL: http://hg.openjdk.java.net/openjfx/8u-dev/rt/rev/5b4987890bc9 RT-37610: [Accessibility, JAWS] Fix TableView ! modules/controls/src/main/java/javafx/scene/control/TableView.java
hg: openjfx/8u-dev/rt: RT-37662: [Accessibility] Define title, description, and help
Changeset: 741fdfc2447e Author:Felipe Heidrich felipe.heidr...@oracle.com Date: 2014-06-24 16:08 -0700 URL: http://hg.openjdk.java.net/openjfx/8u-dev/rt/rev/741fdfc2447e RT-37662: [Accessibility] Define title, description, and help Mac: Redifine DESCRIPTION to AXRoleDescription (as AXDescription) ! modules/graphics/src/main/java/com/sun/glass/ui/mac/MacAccessible.java
[8u40] Review Request (second iteration): (RT-36510) [CSS] Reduce CssMetaData boilerplate code
I am seeking feedback on
http://cr.openjdk.java.net/~dgrieve/RT-36510/webrev.00 which addresses
https://javafx-jira.kenai.com/browse/RT-36510.
This iteration reduces the boiler-plate to one line to create the
StyleableProperty and one method to return the CssMetaData list.
Example use:
public class MyButton extends Button {
public MyButton(String text) {
super(text);
getStyleClass().add(my-button);
}
public ObservableValueString fooProperty() { return
(ObservableValueString)foo; }
public String getFoo() { return foo.getValue(); }
public void setFoo(String value) { foo.setValue(value); }
private final StyleablePropertyString foo =
StyleablePropertyFactory.getInstance().createStyleableStringProperty(this,
foo, -my-foo, s - ((MyButton)s).foo);
public ObservableValueDouble offsetProperty() { return
(ObservableValueDouble)offset; }
public Double getOffset() { return offset.getValue().doubleValue(); }
public void setOffset(Double value) { offset.setValue(value); }
private final StyleablePropertyNumber offset =
StyleablePropertyFactory.getInstance().createStyleableNumberProperty(this,
offset, -my-offset, s - ((MyButton)s).offset);
public ObservableValueInteger countProperty() { return
(ObservableValueInteger)count; }
public Integer getCount() { return count.getValue().intValue(); }
public void setCount(Integer value) { count.setValue(value); }
private final StyleablePropertyNumber count =
StyleablePropertyFactory.getInstance().createStyleableNumberProperty(this,
count, -my-count, s - ((MyButton)s).count);
@Override
public ListCssMetaData? extends Styleable, ?
getControlCssMetaData() {
return StyleablePropertyFactory.getInstance().getCssMetaData(this);
}
}
Re: Testing accessibility / sample apps
Hi Jann, I have re-enabled all the accessibility code in hg.openjdk.java.net/openjfx/8u-dev/rt Notes: I have also released the fix for JAWS (RT-37530). But before testing text edits you will need to add a setting to JAWS, see https://javafx-jira.kenai.com/browse/RT-37609 You still need the -Djavafx.accessible.force=true on Windows 7, but very soon that will not be needed anymore, see: https://javafx-jira.kenai.com/browse/RT-37702 Internally we did virtually all our testing using Narrator and VoiceOver, which are the native screen readers on Windows and MacOSX respectively. I believe you will be the first to try JAWS and NVDA on Windows 7. Let me know how it goes. Regards Felipe On Jun 23, 2014, at 3:50 AM, Jann Schneider jann.schnei...@googlemail.com wrote: Hi Felipe, i tried with the latest available EA build, java -version tells me: java version 1.8.0_20-ea Java(TM) SE Runtime Environment (build 1.8.0_20-ea-b19) Java HotSpot(TM) Client VM (build 25.20-b19, mixed mode, sharing) Also i used Jaws 15 (-.0.9 i think) and as an alternative NVDA 14.2. Hum, not quite sure about the narrator tool: i guess thats the one that shipps with windows? Well i can try this too though i'm not really used to it :) Maybe it's better to just wait until the code is back and test with the current sources.. So we have the same base and know exactly what we expect for the tests. Regards Jann 2014-06-21 5:16 GMT+02:00, Felipe Heidrich felipe.heidr...@oracle.com: Hi Jann, That is great that you got to build JavaFX, it will make much easier to test patches and fixes going forward. That said, assuming that you downloaded jdk1.8.0_20 b19 or less, accessibility should have worked. What is the output of java -version ? Can you try Narrator ? I’ll put the code back early next week, either Monday or Tuesday. You can track the progress here: https://javafx-jira.kenai.com/browse/RT-37536 I’ll email the list when the code is out. Regards, Felipe On Jun 20, 2014, at 4:00 PM, Jann Schneider jann.schnei...@googlemail.com wrote: ok i just rebuild using the 32 bit jdk and this works! $ gradle clean sdk ... BUILD SUCCESSFUL :-) I think i've just installed the 32 bit C++ compilers only. Maybe i missed a setting in the installer of visual studio .. btw. i build with the VS 2010 express (as suggested at the wiki). So i'll wait until the accessibility portion is back in the repo and try with that included then. Thanks for your help so fahr! @Steve: could you please send a short message to the list if the accessibility sources are in the repo again? Regards Jann 2014-06-20 23:50 GMT+02:00, Jann Schneider jann.schnei...@googlemail.com: Yes looks like i have an issue with looking up cl.exe. This was the output when running with --stacktrace: * Exception is: org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':fxpackager:buildJavaPackager'. ... Caused by: org.gradle.api.GradleException: Could not call NativeCompileTask.compile() on task ':fxpackager:buildJavaPackager' ... Caused by: java.util.concurrent.ExecutionException: org.gradle.process.internal.ExecException: A problem occurred starting process 'command 'C:/Program Files (x86)/Microsoft Visual Studio 10.0/VC/BIN/amd64/cl.exe'' ... Caused by: java.io.IOException: Cannot run program C:/Program Files (x86)/Microsoft Visual Studio 10.0/VC/BIN/amd64/cl.exe (in directory D:\jann\sandbox\java\openjfx\modules\fxpackager): CreateProcess error=2, Das System kann die angegebene Datei nicht finden ... Caused by: java.io.IOException: CreateProcess error=2, Das System kann die angegebene Datei nicht finden (file not found) Actually cl.exe is located at: C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin - but it looks for ...bin/amd64/cl.exe I've also tried to run the build from the cygwin terminal and as well from the visual studio command prompt where i could call cl.exe directly .. Always the same result. Is there a parameter to specify where theVS compiler and stuff is located? btw. i checked that the %VS100COMNTools% variable is set properly. What else could i check? Thanks in advance :) Jann 2014-06-20 23:30 GMT+02:00, Kevin Rushforth kevin.rushfo...@oracle.com: * What went wrong: Execution failed for task ':fxpackager:buildJavaPackager'. Could not call NativeCompileTask.compile() on task ':fxpackager:buildJavaPackager' When I've seen this in the past it's been related to the compiler install. Do you have VS 2010 SP1 or something else? -- Kevin Jann Schneider wrote: Hi, Well on windows it's always a bit more difficult i guess :-) After setting up my build environment as described on the wiki i first tried $ gradle tasks This works as expected! When running $ gradle sdk or just gradle without any target i get the following error: FAILURE: Build failed with an exception. * What went wrong:
Re: Testing accessibility / sample apps
Hi Felipe! thanks, this are good News :-) Well yesterday i had some issues with the build bc the famous Windows updates Feature screwed things up .. however, i've recently fixed it so i'll try it today. Just another question concerning testing with the build from sources: i guess i can just run the example apps located in openjfx/apps/ ? What would be the proper way to invoke one of them and make sure the proper jfx is loaded? Do i have to add it to the boot cp? Or is it enough to just put it on the classpath? Regards Jann 2014-06-25 7:17 GMT+02:00, Felipe Heidrich felipe.heidr...@oracle.com: Hi Jann, I have re-enabled all the accessibility code in hg.openjdk.java.net/openjfx/8u-dev/rt Notes: I have also released the fix for JAWS (RT-37530). But before testing text edits you will need to add a setting to JAWS, see https://javafx-jira.kenai.com/browse/RT-37609 You still need the -Djavafx.accessible.force=true on Windows 7, but very soon that will not be needed anymore, see: https://javafx-jira.kenai.com/browse/RT-37702 Internally we did virtually all our testing using Narrator and VoiceOver, which are the native screen readers on Windows and MacOSX respectively. I believe you will be the first to try JAWS and NVDA on Windows 7. Let me know how it goes. Regards Felipe On Jun 23, 2014, at 3:50 AM, Jann Schneider jann.schnei...@googlemail.com wrote: Hi Felipe, i tried with the latest available EA build, java -version tells me: java version 1.8.0_20-ea Java(TM) SE Runtime Environment (build 1.8.0_20-ea-b19) Java HotSpot(TM) Client VM (build 25.20-b19, mixed mode, sharing) Also i used Jaws 15 (-.0.9 i think) and as an alternative NVDA 14.2. Hum, not quite sure about the narrator tool: i guess thats the one that shipps with windows? Well i can try this too though i'm not really used to it :) Maybe it's better to just wait until the code is back and test with the current sources.. So we have the same base and know exactly what we expect for the tests. Regards Jann 2014-06-21 5:16 GMT+02:00, Felipe Heidrich felipe.heidr...@oracle.com: Hi Jann, That is great that you got to build JavaFX, it will make much easier to test patches and fixes going forward. That said, assuming that you downloaded jdk1.8.0_20 b19 or less, accessibility should have worked. What is the output of java -version ? Can you try Narrator ? I’ll put the code back early next week, either Monday or Tuesday. You can track the progress here: https://javafx-jira.kenai.com/browse/RT-37536 I’ll email the list when the code is out. Regards, Felipe On Jun 20, 2014, at 4:00 PM, Jann Schneider jann.schnei...@googlemail.com wrote: ok i just rebuild using the 32 bit jdk and this works! $ gradle clean sdk ... BUILD SUCCESSFUL :-) I think i've just installed the 32 bit C++ compilers only. Maybe i missed a setting in the installer of visual studio .. btw. i build with the VS 2010 express (as suggested at the wiki). So i'll wait until the accessibility portion is back in the repo and try with that included then. Thanks for your help so fahr! @Steve: could you please send a short message to the list if the accessibility sources are in the repo again? Regards Jann 2014-06-20 23:50 GMT+02:00, Jann Schneider jann.schnei...@googlemail.com: Yes looks like i have an issue with looking up cl.exe. This was the output when running with --stacktrace: * Exception is: org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':fxpackager:buildJavaPackager'. ... Caused by: org.gradle.api.GradleException: Could not call NativeCompileTask.compile() on task ':fxpackager:buildJavaPackager' ... Caused by: java.util.concurrent.ExecutionException: org.gradle.process.internal.ExecException: A problem occurred starting process 'command 'C:/Program Files (x86)/Microsoft Visual Studio 10.0/VC/BIN/amd64/cl.exe'' ... Caused by: java.io.IOException: Cannot run program C:/Program Files (x86)/Microsoft Visual Studio 10.0/VC/BIN/amd64/cl.exe (in directory D:\jann\sandbox\java\openjfx\modules\fxpackager): CreateProcess error=2, Das System kann die angegebene Datei nicht finden ... Caused by: java.io.IOException: CreateProcess error=2, Das System kann die angegebene Datei nicht finden (file not found) Actually cl.exe is located at: C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin - but it looks for ...bin/amd64/cl.exe I've also tried to run the build from the cygwin terminal and as well from the visual studio command prompt where i could call cl.exe directly .. Always the same result. Is there a parameter to specify where theVS compiler and stuff is located? btw. i checked that the %VS100COMNTools% variable is set properly. What else could i check? Thanks in advance :) Jann 2014-06-20 23:30 GMT+02:00, Kevin Rushforth kevin.rushfo...@oracle.com: * What went wrong: Execution failed for task ':fxpackager:buildJavaPackager'. Could
Windows updates might damage the build
Hi all, I just wanted to share this info in case someone else runs into this Problems: Yesterday i got some updates on my Windows 7. Afterwards i wasn't able to build jfx anymore. Just got a linker error (lnk 1123). After googling around a bit for this stuff it turned out that there is an update for the update ;-) You'll just have to install the Service pack 1 for Visual Studio 2010 in order to make it work again. (you can get it via the MS download Center) After installing that patch the build works fine again. Regards Jann!
