We're updating the issue view to help you get more done. 

Glassfish deployment fails on Windows when contextroot = /

Description

When deploying to a Glassfish container on Windows with a <deployable> whose <context> is set to "/", the asadmin command looks like this:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 [DEBUG] [talledLocalContainer] Execute:Java13CommandLauncher: Executing 'C:\Program Files (x86)\Java\jdk1.6.0_37\jre\bin\java.exe' with arguments: '-jar' 'C:\project\target\cargo\installs\glassfish-zip-3.1.2.2\glassfish3\glassfish\modules\admin-cli.jar' '--interactive=false' '--port' '4848' '--user' 'admin' '--passwordfile' 'C:\project\target\cargo\configurations\glassfish3x\password.properties' 'deploy' '--force' '--contextroot' '' 'C:\project\target\project-1.0-SNAPSHOT.war'

The command fails with the message "Command deploy requires an operand of type class java.io.File"; it appears Windows is ignoring the empty string. (Linux reports a similar command line but handles the empty string without a problem.)

I've worked around this by setting <context>/rootContext</context> (and stripping rootContext from tests that reuse the Maven property which is actually used in <context/>) but it would be nice to have <context>/</context> work out of the box.

Status

Assignee

Savas Ali Tokmen

Reporter

Peter Janes

Components

Fix versions

Priority

Minor