-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P2
-
Affects Version/s: 8u40
-
Component/s: deploy
-
Environment:
OEL 32-bit
When I'm not specifying CLASSPATH parameter and the jars are linked in MANIFEST.MF, the application is not started with message "Segmentation fault (core dumped)".
build.xml: <attached>
App1.cfg:
app.mainjar=testFxAppWithUtil.jar
app.version=1.0
app.mainclass=testapp/App1
app.classpath=$PACKAGEDIR/Util.jar
app.preferences.id=testapp
Jars: <attached>
If I remove "app.classpath=...", the application starts to work perfectly without any classpath issues (for example, no ClassNotFoundException )
Workaround is to set CLASSPATH when bundling.
build.xml: <attached>
App1.cfg:
app.mainjar=testFxAppWithUtil.jar
app.version=1.0
app.mainclass=testapp/App1
app.classpath=$PACKAGEDIR/Util.jar
app.preferences.id=testapp
Jars: <attached>
If I remove "app.classpath=...", the application starts to work perfectly without any classpath issues (for example, no ClassNotFoundException )
Workaround is to set CLASSPATH when bundling.
- relates to
-
JDK-8093250 [Bundlers] passing JVM options is broken
-
- Closed
-