I am attempting to test Ant 1.6 on my company's buildfiles. We have been using namespaces (without declaring them) but it now seems that they won't work at all. I have found that when I have the namespace in front of a task name, I get an error saying that the namespace is not declared. If I then declare the namespace I get an error saying that the task class can't be found. Is the namespace URI supposed to be pointing to something specific?

Thanks,

Kevin LaVergne

Here is the error that I get (I have done everything that it says in the error before sending this email):

BUILD FAILED
C:\views\klavergn_synergy_1.0\Public\buildfiles\build-settings.ent:397: Could not create task or type of type: http://www.parago.com/ant/tasks/clearcase:latestBaseline.


Ant could not find the task or a class this task relies upon.

This is common and has a number of causes; the usual
solutions are to read the manual pages then download and
install needed JAR files, or fix the build file:
- You have misspelt 'http://www.parago.com/ant/tasks/clearcase:latestBaseline'.
Fix: check your spelling.
- The task needs an external JAR file to execute
and this is not found at the right place in the classpath.
Fix: check the documentation for dependencies.
Fix: declare the task.
- The task is an Ant optional task and optional.jar is absent
Fix: look for optional.jar in ANT_HOME/lib, download if needed
- The task was not built into optional.jar as dependent
libraries were not found at build time.
Fix: look in the JAR to verify, then rebuild with the needed
libraries, or download a release version from apache.org
- The build file was written for a later version of Ant
Fix: upgrade to at least the latest release version of Ant
- The task is not an Ant core or optional task
and needs to be declared using <taskdef>.


Remember that for JAR files to be visible to Ant tasks implemented
in ANT_HOME/lib, the files must be in the same directory or on the
classpath

Please neither file bug reports on this problem, nor email the
Ant mailing lists, until all of these causes have been explored,
as this is not an Ant bug.


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to