as explained in [1] or in [3], these namespaces are not only namespace conventions, but they are 2 different ways of deploying the tasks: - either add a typedef in each Ant build file with a reference to maven-ant-tasks.jar: "urn:maven-artifact-ant" namespace - or copy maven-ant-tasks.jar to Ant's lib directory, then the typedef is automagically available: "antlib:org.apache.maven.artifact.ant" namespace
Then both need to stay in the installation doc [1]: which to use depends on user needs. Maven Ant Tasks unit tests in [3] need to use "urn:maven-artifact-ant" to be able to the version being built in target/. But IMHO, most end-users are using "antlib:org.apache.maven.artifact.ant": copying tasks to Ant's lib directory is the easiest way to use them. Is there really any other place in the docs where these namespaces are referred to? Regards, Hervé [3] http://svn.apache.org/viewvc/maven/ant-tasks/branches/maven-ant-tasks-2.0.x/sample.build.xml?view=markup Le vendredi 01 mai 2009, Paul Gier a écrit : > There are two different xml namespaces used in the docs and examples of the > maven ant tasks [1]. They are "urn:maven-artifact-ant" and > "antlib:org.apache.maven.artifact.ant". The second one seems to better > match the example on the ant site [2]. > > Anyone have preferences one way or the other? If not, I will try to > standardize the docs using "antlib:org.apache.maven.artifact.ant". > > [1] http://maven.apache.org/ant-tasks/installation.html > [2] http://ant.apache.org/manual/CoreTypes/antlib.html > > --------------------------------------------------------------------- > 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]
