Open BadgerOnABike opened 4 days ago
@BadgerOnABike I suspect this is NOT a problem with the jar file but the install environment, pointing to a need for a better installer as opposed to hunting for problems inside the code.... I think.
To assist in sorting out what may need to be done within the installer. Or is the suggestion that the way the system is trying to talk to java isn't a proper call? I guess I'm asking if this solve is even in our control.
To assist in sorting out what may need to be done within the installer. Or is the suggestion that the way the system is trying to talk to java isn't a proper call? I guess I'm asking if this solve is even in our control.
I think that that is coming from the default behaviour to use C:\Program Files\Yada yada, (note the spaces) which I am guessing it does not like and it may want the c:\Progra~1\Yada~1 the 8.3 safe path.
@BadgerOnABike that last bit should look like C:\Progra~1\Yada~1
This is coming from the redapp shortcut
yes, i think we blame the installer (making the shortcut) and perhpas use a better install script?
Message Body
Currently the release of REDapp does not launch via the jar by double clicking. A user needs to activate the jar file from
cmd
withjava -jar REDapp.jar
to have it launch.The users that would expect double clicking to work likely would not go down the path of trying to hit the utility via
cmd
.