DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=33864>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=33864

           Summary: exec task documentation for vmlauncher="false" is
                    misleading ...
           Product: Ant
           Version: 1.6.2
          Platform: PC
        OS/Version: Solaris
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Documentation
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


The Ant 1.6.2 documentation for the vmlauncher attribute of the <exec> task
says:

"Run command using the Java VM's execution facilities where available. If set 
to false the underlying OS's shell, either directly or through the antRun 
scripts, will be used. Under some operating systems, this gives access to 
facilities not normally available through the VM including, under Windows, 
being able to execute scripts, rather than their associated interpreter. If 
you want to specify the name of the executable as a relative path to the 
directory given by the dir attribute, it may become necessary to set 
vmlauncher to false as well."

This implies that setting vmlauncher="false" will allow a relative pathname
in the executable attribute.  However, bug #3129 which is marked as "RESOLVED
WON'T FIX", clearly indicates that, on at least some platforms, an absolute
path is required in the executable attribute.  For me, with vmlauncher="false",
a relative path for executable="" is fine on RH Linux, but I'm required to use 
an absolute path in the executable="" attribute on Solaris 8/9.

I would suggest that either a Solaris-specific warning be included (similar to
the OS-specific warnings for Cygwin/OpenVMS/Redhat S390) or, maybe better yet,
the "trick" of using <property name="executable-full-path" 
location="../relative/path/to/executable"/> be included in the examples
as a way of insuring that <exec executable="${executable-full-path}" ... />
will work properly.

Thanks for your consideration,

John Shott

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to