Jens,
I had cut this version down from my build.xml file as it was using the junit
features and I did not have time to do all the automation (junit, p4,
build,etc) I would like for our 1st release, so I just tired to do this in
an other file and will re-integrate later.
So, it would look like this?
<path id="${CLASSPATH}">
</path>
<echo message="syncing"/>
<p4Sync force="yes" view="//cpdev//main/src/..." />
thx
-mez
----- Original Message -----
From: "Jens v.P." <[EMAIL PROTECTED]>
To: "Ant Users List" <[EMAIL PROTECTED]>
Sent: Thursday, December 20, 2001 9:08 AM
Subject: Re[2]: Perforce Optional Tasks
> Hello Marcus,
>
> it's as Andrew expected: you have defined classpath outside a task
> element, where ant interprets it as a task ittself. Classpath can only
> be defined inside some task (like javac, java, javadoc...).
>
> If you want to define classpath and use it several times, just replace
> your <classpath> with <path id="classpath"> and use references in
> further tasks. But in fact, I don't see where you're using classpath
> again... Why did you define classpath where you've defined it?
>
> Jens
>
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
