ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 39359] New: - Problems with OSD-5 filespecs and return codes on OpenVMS
Date Wed, 19 Apr 2006 20:16:08 GMT
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=39359>.
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=39359

           Summary: Problems with OSD-5 filespecs and return codes on
                    OpenVMS
           Product: Ant
           Version: 1.7Alpha (nightly)
          Platform: HP
        OS/Version: OpenVMS
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Core tasks
        AssignedTo: dev@ant.apache.org
        ReportedBy: meg.garrison@hp.com


We're currently looking into some problems with filespecs and return codes on 
OpenVMS.  These are two areas where OpenVMS is very different from Unix-like 
operating systems.  

Filespecs on OpenVMS have a different format than standard Unix filespecs.  A 
conversion routine to convert between the Unix-style and OpenVMS-style formats 
is already in FileUtils.java, but it is out of date since it assumes (older) 
ODS-2 style OpenVMS filespecs, and the current format is ODS-5 style.  We 
propose to update this routine to support the conversion of ODS-5 style 
OpenVMS filespecs to/from Unix-style filespecs.

In addition, OpenVMS normally returns a 1 for success from functions and 
system calls, for failures it returns a value which is a predefined error code 
> 1.  However, Java assumes that the return value is the number of errors 
encountered, which means that 0 is successful.  We're proposing changes to 
Execute.java to control which return style is used (conditionally on OpenVMS 
systems) by checking the value of a logical name on OpenVMS (like an 
environment variable).

Also in Execute.java, some changes to the way certain DCL commands are built 
will enable tasks like <exec/> to work properly.  At this time, if the 
argument to <exec/> is an image represented by a Unix-style filespec, the 
<exec/> will fail. 

As an example, a test suite that reproduces these problems is 

Test: org.apache.tools.ant.taskdefs.SignJarTest
[test-junit] Tests run: 32, Failures: 2, Errors: 19, Time elapsed: 284.826 sec 

With your permission we will post the entire test results (from OpenVMS) 
before and after and the patches here to this bug report.

-- 
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: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message