it works if I use <magmic:exists ... /> (my own custom Condition) instead of the isset but it doesn't like the built-in conditions.
Is there a namespace for the default tasks? current: or ant: or something?
You need to check out the new beta of Ant-1.6.2. In 1.6.0 and 1.6.1, if you use a namespace, you have to use that namespace for all subelements. With 1.6.2..., well, here's what they wrote in the release notes...
"Nested elements for namespaced tasks and types may belong to the Ant default namespace as well as the task's or type's namespace."
http://cvs.apache.org/dist/ant/v1.6.2beta1/
Jake
-- Jeffrey Bacon [EMAIL PROTECTED] Creative Developer http://www.magmic.com
Alexey N. Solofnenko wrote:Please try it without namespace. It works on my system. There were few emails saying that namespace processing is broken. I still do not understand how it works in ANT, so I never use it.
- Alexey.
Jeffrey Bacon wrote:
Am I missing something stupid here? I can use my own condition but when I use isset I get:
build.xml:343: Class net.sf.antcontrib.logic.IfTask doesn't support the nested "isset" element.
<contrib:if>
<isset property="com.magmic-libs-built" />
<contrib:then>
<contrib:var name="build_classpath" value="${build_classpath};${basedir}/${temp.dir}/com.magmic.jar" />
</contrib:then>
</contrib:if>--------------------------------------------------------------------- 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]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
