You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by bu...@apache.org on 2002/10/04 04:09:13 UTC
DO NOT REPLY [Bug 13271] New: -
ejbjar's dtd location attribute is not relative to basedir
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13271>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13271
ejbjar's dtd location attribute is not relative to basedir
Summary: ejbjar's dtd location attribute is not relative to
basedir
Product: Ant
Version: 1.5.1
Platform: All
OS/Version: Windows NT/2K
Status: NEW
Severity: Normal
Priority: Other
Component: Optional Tasks
AssignedTo: ant-dev@jakarta.apache.org
ReportedBy: colinml1@exis.com
Most ant tasks treat relative paths as relative to basedir, not the current user
directory, whatever that may be.
When using ejbjar however, and using the dtd attribute to specify a local
location of a dtd file, the 'location' attribute appears to be taken relative to
the current directory, not basedir. That is, if ant is run out of the project
root directory, then everything works. But if the project is called from another
ant project (and basedir is properly set to the root of the child project), the
dtd files can no longer be found, and the remote versions are attempted to be
loaded. I have verified that basedir is correct, since all other relative paths
still work (as specified to javac, mkdir, etc.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>