2012/2/17 Bill Barker <billbar...@apache.org>:
>(...)
> validate-eoln:
>
> BUILD FAILED
> /srv/gump/public/workspace/tomcat-trunk/build.xml:489: taskdef class
> org.apache.tomcat.buildutil.CheckEol cannot be found
> using the classloader
> AntClassLoader[/usr/lib/jvm/java-6-openjdk/lib/tools.jar:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/packages/eclipse/plugins/org.eclipse.jdt.core_3.4.2/jdtcore.jar:/srv/gump/public/workspace/tomcat-trunk/tomcat-deps/tomcat-dbcp-17022012.jar:/srv/gump/public/workspace/apache-commons/daemon/dist/commons-daemon-17022012.jar]
I was trying to simplify the project definition for this new project
and unexpectedly broke it.
The reason is that the Task is defined by the following snippet, but
Ant ignored the "classpath" attribute.
<taskdef name="checkeol"
classname="org.apache.tomcat.buildutil.CheckEol"
classpath="${tomcat.classes}" />
The technical reason behind this is that the
/gump/metadata/workspace.xml file has the following definition, which
is effective for all projects [1]:
<property name="build.sysclasspath" value="only"/>
The effect of that property value is that Ant starts to ignore
classpath attributes, as documented in its manual [2]
[1] http://svn.apache.org/viewvc/gump/metadata/workspace.xml?view=markup#l39
[2] http://ant.apache.org/manual/sysclasspath.html
I did not expect that Ant had such a feature. I'll fix the broken build.
Best regards,
Konstantin Kolinko
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
