Multiple drives (bug 750579) ( was RE: A few questions about the 1.0.0-beta5 release

RuperDependTask was taking a property, converting it to a File, converting
that to a VFS FileObject, then (when needed) trying to go back to File or
String. (I'd hoped I was saving code, but was causing this to be a mess.)

RuperDependTask now gets a File (or String) when I need one, no FileObject
stage. I've tested this with my G:\F: combination. Could you try it with
your set-up?

I've checked the ruper fix into the library in centipede. Care to download
these latest centipede from CVS and try it?

regards,

Adam
-----Original Message-----
From: [email protected]
[mailto:[email protected]]On Behalf Of Adam
Jack
Sent: Saturday, June 07, 2003 11:10 AM
To: [email protected]
Subject: RE: A few questions about the 1.0.0-beta5 release


Joshua

I think the error is in RuperDependTask here:

    private String getJarsDirString() throws Exception {
        return getJarsDir().getName().getPath();
    }

Unfortunately the FileObject.FileName.getPath() seems to start with "/" not
"drive:/", so the drive is being lost (in favour of that which the build
file is on.)

That said, I can fix it, but then what do we do? Nick, what is procedure
from here? Joshua, are you game to work with us from centipede from CVS, or
what? What are your plans?

BTW: Tried running centipede from P: ? ;-)

regards

Adam
-----Original Message-----
From: [email protected]
[mailto:[email protected]]On Behalf Of Nick
Chalko
Sent: Saturday, June 07, 2003 8:57 AM
To: [email protected]
Subject: Re: A few questions about the 1.0.0-beta5 release


I think Adam may have also run into this.
Please open a bug at
http://sourceforge.net/tracker/?group_id=36516&atid=423515  so we can
track it.

R,
Nick

Joshua Davis wrote:

> 1) Can this release build multiple jar files from multiple source code
> directories?  If so, can someone point me to an example?
>
> 2) I've encountered a problem on the Windoze platform when Centipede
> is installed on a different drive than the project.  This is a
> show-stopper for me because my team uses ClearCase, and the source
> code is not on the same 'drive letter' as the shared Centipede
> installation.  Anyway, I'd offer to help fix this error, but I need to
> know where (and how) to look for the cause.
>
> Here is the error message:
>
> Searching for centibuild.xml ...
> Buildfile: P:\dev\hello-world\centibuild.xml
> Initializing Centipede...
> ...Centipede started.
> No project specified. Defaulting to first project:  helloworld
> Dependency sequence for project `helloworld' is *NONE*
>
> ... snip ...
>
> compile-src:
> Compiling project core with Java 1.4, debug on, optimize off,
> deprecation on
>
> copy-exported-jars:
> Created dir: P:\dev\hello-world\build\helloworld\work\java\dist-bin\lib
>
> BUILD FAILED
>
file:///P:/dev/hello-world/build/work/temp/krysalis-template-helloworld.getd
epend.xml:26:
> P:\java\krysalis-centipede-1.0.0-beta5\tools\jars not found.
>
> Total time: 9 seconds
>
> In this case, the sources are in p:\dev\hello-world, and the
> 'centibuild.xml' file was simply copied from the minimal template.
> CENTIPEDE_HOME is set to C:\java\krysalis-centipede-1.0.0-beta5.





-------------------------------------------------------
This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.
_______________________________________________
krysalis-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/krysalis-users



-------------------------------------------------------
This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.