So lets make the lib-dir another directory (${repository.dir}???) and put our own stuff in there as well. You already introduced depot.update.dir or something, this directory can be used, at least when it exists.
what do you think?
BTW, not all antlets are published (especially the apache one). Can you please publish them, so that the build is working? Right now, I have to build all antlets myself and then I have to publish them on my local machine, etc. Very annoying :-(
Markus
Nick Chalko wrote:
I have a sample of using Update for builds
http://svn.apache.org/repos/asf/incubator/depot/trunk/update/src/sample/build.xml
Markus M. May wrote:
Hello,
since Depot is a repository Updater we should try to introduce the repository already in the build-files of update? What do you think? How can we do this?
Markus
[EMAIL PROTECTED] wrote:
Author: nickchalko Date: Tue Apr 27 09:22:34 2004 New Revision: 10313
Modified: incubator/depot/trunk/common/build.xml Log: Lib dir is optional
Modified: incubator/depot/trunk/common/build.xml
==============================================================================
--- incubator/depot/trunk/common/build.xml (original)
+++ incubator/depot/trunk/common/build.xml Tue Apr 27 09:22:34 2004
@@ -40,8 +40,8 @@
<path id="depot-common.classpath">
- <fileset dir="lib">
- <include name="*.jar" />
+ <fileset dir=".">
+ <include name="lib/*.jar" />
</fileset>
</path>
