-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ant-Task: Specifying classpath internally in the build script leads to Failed to parse error #78
Comments
Try something like <path id="phsch.path">
<fileset dir="../../../../target">
<include name="*-jar-with-dependencies.jar"/>
</fileset>
</path>
<taskdef name="schematron" classname="com.helger.schematron.ant.Schematron" classpathref="phsch.path" /> I am not an ANT expert :( |
Me neither. But anything I tried, didn't worked. With And something seems to work, because if I ommit the any classpath reference I get this (for sure):
There is an open stackoverflow question about a very similar error message. Comment from Micheal Kay was:
|
I can reproduce the error. It seems like a problem with created "JAR with dependencies". |
The reasons seems to be that |
This is fixed in the 5.2.0 release |
It's a pleasure to work with such a well-maintained open source project! It works perfect. |
A star on the project is always appreciated :) |
Hi,
In the documentation about declaring the ant task there is this paragraph:
At least in my case the "Alternative" does not work.
My ant script:
If I just call
cls && ant -f build.xml
I get this log:For some reasons it tries to use the Xalan? (
com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
)If I call the same script with
cls && ant -lib=lib1.0 -f build.xml
it works:This leads in my case to nasty nested ant calls in my ant build scripts, because we need a simple ant call on the commandline. It works with such workarounds, but the "Alternative" with the classpath attribute would make it really cool.
Background infos:
Apache Ant(TM) version 1.10.6 compiled on May 2 2019
1.8.0_211
The text was updated successfully, but these errors were encountered: