If I run the code:
import javafx.application.Application;
import javafx.collections.FXCollections;
import javafx.collections.ObservableList;
import javafx.scene.Scene;
import javafx.scene.control.ListView;
import javafx.scene.layout.AnchorPane;
import javafx.stage.Stage;
public class JavaApplication37 extends Application {
public static void main(String[] args) {
System.out.println("was in main");
Application.launch(args);
}
@Override
public void start(Stage primaryStage) throws Exception {
System.out.println("was in start");
AnchorPane ap = new AnchorPane();
final ListView lv = new ListView();
final ObservableList lst = FXCollections.observableArrayList();
lv.setItems(lst);
ap.getChildren().add(lv);
Scene scene = new Scene(ap, 100, 100);
primaryStage.setScene(scene);
primaryStage.show();
}
}
I see an output:
was in main
was in start
using JDK 8b71,
and I see output:
was in start
using JDK 8b73.
Also, it broken launching of our tests.
In common case it brakes backward compatibility.
Possibly, it somehow related to patches about JavaFX launch from jars.
import javafx.application.Application;
import javafx.collections.FXCollections;
import javafx.collections.ObservableList;
import javafx.scene.Scene;
import javafx.scene.control.ListView;
import javafx.scene.layout.AnchorPane;
import javafx.stage.Stage;
public class JavaApplication37 extends Application {
public static void main(String[] args) {
System.out.println("was in main");
Application.launch(args);
}
@Override
public void start(Stage primaryStage) throws Exception {
System.out.println("was in start");
AnchorPane ap = new AnchorPane();
final ListView lv = new ListView();
final ObservableList lst = FXCollections.observableArrayList();
lv.setItems(lst);
ap.getChildren().add(lv);
Scene scene = new Scene(ap, 100, 100);
primaryStage.setScene(scene);
primaryStage.show();
}
}
I see an output:
was in main
was in start
using JDK 8b71,
and I see output:
was in start
using JDK 8b73.
Also, it broken launching of our tests.
In common case it brakes backward compatibility.
Possibly, it somehow related to patches about JavaFX launch from jars.