Document the dirname/windows "feature". If this cannot be resolved,
it would be good to document the behavior. Can the following be
considered for the Ant user manual?
http://ant.apache.org/manual/CoreTasks/jar.html
Note that if the basedir value has space character(s) appended to it,
then some
At 16:30 2006-01-16, you wrote:
I have a copy of DirectoryScanner. I do not see any calls to trim
in that code.
I will prepare a patch that quotes the directory name in question.
This might help others that get the error. I do know think it would
be safe to modify the file name, I would not wa
I already committed to HEAD the change to quote the
directory name in the log message. The problem is
with Windows. e.g. see
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/fileio/fs/naming_a_file.asp
-Matt
--- glenn opdycke-hansen <[EMAIL PROTECTED]> wrote:
> I have a copy of
I have a copy of DirectoryScanner. I do not see any calls to trim in that code.
I will prepare a patch that quotes the directory name in question.
This might help others that get the error. I do know think it would
be safe to modify the file name, I would not want to break something
else.
-
It sounds like either Ant Core or Java is performing a "trim" in one
path of execution that is not being performed on the other. (On a
second read, sounds like java.io.File is ignoring the trailing blank
while DirectoryScanner thinks it is significant).
I don't have this source in front of me
Yes, I was running on windows. We build on windows and deploy to unix.
I just tested it on aix 5.2 and got the following msgs
[echo] jar destfile="output/out2.jar"
[echo] basedir="jar-root "
BUILD FAILED
/app/tibcoems/deployment/ant-jar-filespec-prob/build-basedir-space.xml:67:
/app/
Are you running on windows? Testing on windows I do
see the same problem, but it appears to me that
directories with trailing spaces are clipped at the OS
level. Nothing we can do here... if you or anyone else
has a nice idea of where in the manual we could make
mention of this little tidbit that'
Ant script to recreate problem is attached.
jar.root.dir.exists=${jar.root.dir.exists}
jar.root.dir.dir1.exists=${jar.root.dir.dir1.exists}
jar destfile="${out.dir}/${out1.jar}"
basedir="${jar.root.dir}"
jar.root.dir.space.exists=${jar.root.dir.space.exists}
--- glenn opdycke-hansen <[EMAIL PROTECTED]> wrote:
> I did make a modification to DirectoryScanner.java.
> The additional output confirms that File.exists()
> thinks that the
> directory with an extra space exists. The change
> that could help is
> to quote the directory name so the space is mor
I did make a modification to DirectoryScanner.java.
The additional output confirms that File.exists() thinks that the
directory with an extra space exists. The change that could help is
to quote the directory name so the space is more promentent. See
below:
[jar] go-get abs path abspath="C
This is going to be a challenge to patch.
The error is
BUILD FAILED
C:\src\ant-jar-filespec-prob\build-basedir-space.xml:58: IO error
scanning directory C:\src\ant-jar-filespec-prob\jar-root
at
org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1038)
at
org.apache
If you are going to submit a bug report I would advise you to submit a
patch along with it.
--
Jeffrey E. Care ([EMAIL PROTECTED])
WebSphere v7 Release Engineer
WebSphere Build Tooling Lead (Project Mantis)
glenn opdycke-hansen <[EMAIL PROTECTED]> wrote on 01/16/2006 08:27:38 AM:
> We have se
We have seen a cryptic error message from the jar task. If the
basedir directory does not exist, ant writes the following message
BUILD FAILED
C:\src\ant-jar-filespec-prob\build.xml:49:
C:\src\ant-jar-filespec-prob\bad-base-dir-not-exists not found.
Total time: 0 seconds
However if the basedir
13 matches
Mail list logo
