ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nico Seessle" <>
Subject Re: Setting basedir seems broken now
Date Fri, 08 Sep 2000 06:53:19 GMT
Setting basedir seems broken nowFor me CVS is showing the same souce as stated below... AND
I'm getting the same errors. I will check this at work at other Operating Systems - maybe
this is a bug (different behaviour) with W2K? I one submitted a patch to which
tried to resolve the same problem. Maybe it did not get commited because it worked on other
Systems? (Or was it the change made at the same time to avoid mysterious VJ++ Warnings :-)

  ----- Original Message ----- 
  From: Jose Alberto Fernandez 
  To: '' 
  Sent: Friday, September 08, 2000 12:53 AM
  Subject: RE: Setting basedir seems broken now

  The latest CVS seem to have very different code. 
    -----Original Message-----
    From: []
    Sent: Wednesday, September 06, 2000 1:07 PM
    Subject: RE: Setting basedir seems broken now

    I had a problem similar to this, and I was able to resolve it by referencing the parent
directory.  So long as you can guarantee that you will always run the buildfile from c:\qdsdev\bin
(probably through a batch file), you might be able to use this:
    <project name="qds" default="apps" basedir="..">
    I can't guarantee that it will work, but I think your base directory will probably become
C:\qdsdev because now...
    baseD = "C:\qdsdev\bin\.."
    ...which should resolve to "C:\qdsdev"
    I hope this helps.
    --Chris Povirk
      -----Original Message-----
      From: Gardner, David []
      Sent: Thursday, September 07, 2000 2:50 PM
      To: ''
      Subject: RE: Setting basedir seems broken now

      After a bit more probing...  I'm not sure what is _supposed_ to be happening, but I
can tell you what _is_ happening
      The ProjectHelper class contains the code which sets the basedir.  In my case, since
I'm not setting an environment variable, the code that gets executed is (line 240):
              project.setBasedir((new File(buildFileParent, baseDir)).getAbsolutePath());

      And in my case, 
              buildFileParent = "C:\qdsdev\bin" (the directory where I'm running ant)
              baseDir = "c:\qdsdev" (from the build.xml file)
      Now, getAbsolutePath() returns "C:\qdsdev\bin\c:\qdsdev" which is simply the buildFileParent
and baseDir concatenated. 
      Then, project.setBasedir() executes the following code:
              setBaseDir(new File(new File(baseD).getCanonicalPath()));
              (baseD = "C:\qdsdev\bin\c:\qdsdev")
      at which time getCanonicalPath throws an IOException
      Again, I don't really know what the intention of the author was here so I'm not going
to propose a fix.  Maybe this helps explain the problem though.
      David Gardner
        -----Original Message-----
        From: Gardner, David []
        Sent: Thursday, September 07, 2000 11:41 AM
        To: ''
        Subject: Setting basedir seems broken now

        I just grabbed the latest (9/7/00) nightly build and I'm having a problem with setting
the basedir.  I have the following line in my build.xml:

          <project name="qds" default="apps" basedir="c:\qdsdev"> 

        which was working with earlier releases.  However, now I'm getting the following error

          build.xml:7: Can't set basedir null due to The filename, directory name, or volume
label syntax is incorrect 

        I've tried numerous forms for the basedir however I get this error any time I have
a colon in the name.  And when I don't have a colon the path is always interpreted as relative
which is not the desired functionality.

        Any suggestions? 

        David Gardner 

        P.S. Running under Windows 2000. 

        -----Original Message----- 
        From: Stefan Bodewig [] 
        Sent: Thursday, September 07, 2000 10:43 AM 
        Subject: Re: output from the javac built in task 

        >>>>> "JT" == Jørn Tage Tyskerud <>

         JT> Is there a way to get feedback per file (although the file 
         JT> contains no errors) when using the javac build in task. 

        Invoke Ant with the -verbose switch. You will get much more 
        information than you ever wanted to see - including which files 
        <javac> compiles. 


View raw message