1) CLASSPATH Repository
Nick and I implemented a ClasspathRepository in Ruper days of old, the
thinking being -- to allow updates to be sensitive to a [say] Gump context,
and use Gumped jars (in Gump builds) in preference to downloading. I was
considering this for Depot, but it dawned on me this w
I'd cut-n-paste the antlet code from version (it had a property for the
repo, and also a new location) but still this fail. I then noticed an
explicit BUILD FAILED
> Target `test' does not exist in this project.
Ought be gone now.
regards
Adam
> Very usefull, information. It should really help us tune, our verison
> class.
> Perhaps have an option that only list errors.
Yup, but you know me. Start verbose, and trim back once the data is
understood. Got to get it working well first.
BTW: I've asked Gump to run this with/without VFS/Ht
ump/depot/update]
CLASSPATH :
/usr/java/j2sdk1.4.2_04/lib/tools.jar:/data3/gump/depot/update/build/depot-update/junit/classes:/data3/gump/depot/update/dist/depot-update-gump-20040502.jar:/data3/gump/ant/dist/lib/ant-stylebook.jar:/data3/gump/ant/dist/lib/ant-jmf.jar:/data3/gump/ant/dist/lib/ant-swing.ja
Very usefull, information. It should really help us tune, our verison
class.
Perhaps have an option that only list errors.
R,
Nick
Adam R. B. Jack wrote:
This simple tool trolls repositiries, determine groups, then mines those
groups displaying the artefact specifiers it finds in order.
In order
