|
Sort Order:
Ahh yes.
This has not been tested at all on Windows. Solution is simple and will be in the next snapshot build. Apologies for the delayed snapshot build - hectic week at work :)
Just stumbled on this issue and thought I'd share. When using the SNAPSHOT version of the plugin, some of the commands don't actually work. For instance, running "glassfish:deploy" on a non-running instance (in Windows) does not start the instance like it does in Linux. However, once the domain is manually started, running "glassfish:deploy" does deploy the application.
Doesn't seem related to this issue. Could you post a new bug please with config.
I now have a large Windows development team using the SNAPSHOT prior to the upcoming release. They have not observed this issue, so I suspect a configuration problem which may be due to inadequate doco rather than code. Thanks, Dave I also observed this issue on the 2.1 and 2.2-SNAPSHOT versions of the plugin. Running "glassfish:deploy" give me this error:
IOException: Cannot run program "C:\Program Files\glassfishv3-prelude\bin\asadmin": CreateProcess error=193, %1 is not a valid Win32 application There seems to be a missing ".bat" extension to the "asadmin" command. Thanks. I don't think this issue is fixed in version 2.2-SNAPSHOT as I just tested it. However a simple workaround is deleting the asadmin shell file (glassfishdir/bin/asadmin) and keeping the .bat.
|
||||||||||||||||||||||||||||||||||||||||||
Bug
Closed
Major
Asadmin command line needs .bat extension
mvn glassfish:start-domain
I get the following error:
[INFO] Unable to create domain "domain1". IOException: Cannot run program "D:\bin\sailfin/bin/asadmin": CreateProcess error=2, The system cannot find the file specified
Note: domain1 does in fact exist prior to running the command.