
|
If you were logged in you would be able to see more operations.
|
|
|
|
Can we make the packaging an optional step in run configuration?
The current approach with the new run configuration has the following issues
1. Before we launch, every time the packager kicks in and packages it into jnlp before running the app. This slows down development cycle where we code, run, see the output & then code again!
2. If the Eclipse project has a mix of J2SE code (1.6) & JavaFX code, then the packager is not able to proceed as it takes rt.jar from JavaFx bin which is 1.5 compatibility. Consequently we are not even able to launch the app (which was working with 1.3.4 v of the plugin which used a simple javafx to launch the app from eclipse)
Hope that you will consider this in future releases of the plug-in. This has become a showstopper for us and forcing us to use 1.3.4
|
|
Description
|
Can we make the packaging an optional step in run configuration?
The current approach with the new run configuration has the following issues
1. Before we launch, every time the packager kicks in and packages it into jnlp before running the app. This slows down development cycle where we code, run, see the output & then code again!
2. If the Eclipse project has a mix of J2SE code (1.6) & JavaFX code, then the packager is not able to proceed as it takes rt.jar from JavaFx bin which is 1.5 compatibility. Consequently we are not even able to launch the app (which was working with 1.3.4 v of the plugin which used a simple javafx to launch the app from eclipse)
Hope that you will consider this in future releases of the plug-in. This has become a showstopper for us and forcing us to use 1.3.4
|
Show » |
Sort Order:
|