----- Original Message -----
From: "Curtis Yanko" <[EMAIL PROTECTED]>
Sent: Wednesday, August 06, 2003 2:02 PM
> Every time a developer adds a new project dependacy I need to manually
update my
> classpath for that project. This doesn't seem like any way to run a
railroad!
> especially since I've implemented Anthill to allow self-service builds
which
> works great until someone breaks te build script with one of these new
classpath
> dependencies.
>
Sorry to disappoint you, but build files cannot guess which jar files should
be in the classpath to compile or run an application. So you must tell all
your developers that they should let you know *** as soon as *** they
introduce new jar files dependencies, so that you can smoothly adapt the
build files.
Maybe you could write a cgi to add stuff to the classpath, and do some
automatic update of your path definition based on the entry into the cgi (or
jsp or servlet or ...).
This might sound like a bit far-fetched, but if there are often new
components added and if you want to make sure that developers can fix the
build file(s) when you are away from your desk, it might be worth
considering.
> We seem to build our classpath using the
> <path id="xyz">
> <pathelement location=${property.to.our.jarfile} />
> </path>
>
> We don't seem to be using <classpath> but that seems like the same thing
to me,
> just another path-like structure.
>
<path> is the way to declare paths that you can use as <classpath/>
elsewhere in your build file, so it is perfectly OK.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
