Hi,
maybe I misunderstood you but if I use:
...
<property name="myclasspath" refid="cp"/>
<target name="repository-files">
<echo message="${myclasspath}"/>
<mkdir dir="./build"/>
<taskdef name="ojbdoclet"
classname="xdoclet.modules.ojb.OjbDocletTask" classpathref="cp"/>
<mkdir dir="./build"/>
<ojbdoclet destdir="./build">
<fileset dir="./src"/>
<ojbrepository destinationFile="repository_user.xml"/>
<torqueschema databaseName="testojb"
destinationFile="project_schema.xml"/>
</ojbdoclet>
</target>
..
It echoes me that the jars are in the path
Regards,
Markus
> I don't mean the CLASSPATH on the shell but the cp variable you use in the
> ant build file. In the <taskdef> you have an attribute classpathref which
> basically states the id of the path construct in the build file which
> defines the classpath to search in for libraries (this includes the
> xdoclet ojb module). So for the taskdef to find the module it must be in
> this path. Since Ant does not automatically use the CLASSPATH environment
> variable you will have to add it manually to the path construct in the way
> I showed in my previous e-mail (using an environment property and the
> "env." construct).
> Have you tried Ant's -v option? It will show you which classes Ant cannot
> find.
>
> Tom
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
