Date: Thu, 22 Jan 2009 17:38:50 +0100 From: Herve Quiroz <hq@FreeBSD.org> To: andy.lavr@gmail.com Cc: java@FreeBSD.org Subject: Re: New patch ant.sh.in for FreeBSD ports devel/apache-ant Message-ID: <4978A11A.1040408@FreeBSD.org> In-Reply-To: <49784E41.7070006@reactor-xg.kiev.ua> References: <49749D98.4080402@reactor-xg.kiev.ua> <49779F59.6050209@FreeBSD.org> <49784E41.7070006@reactor-xg.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
Andrei V. Lavreniyuk wrote:
> I test, if
>
> ---------------
> CLASSPATH=$ANT_LIB:$CLASSPATH;export CLASSPATH
>
> exec "${JAVACMD}" ${ANT_OPTS} -classpath "${LOCALCLASSPATH}"
> -Dant.home="${DATADIR}" org.apache.tools.ant.launch.Launcher ${ANT_ARGS}
> -lib "${CLASSPATH}" "$@"
> --------------
>
> then following ports
>
> - java/java-checkstyle
> - textproc/ant-xinclude-task
> - java/xdoclet (JAR contains an Ant task)
> - www/extsm
> - www/jetspeed
>
> build an installed fine.
Problem is not only to install them but to run the applications. For
example, checkstyle will install fine but then any project which
references the task will break. That's why it is difficult to test. And
that's why I don't think any port test build will improve things.
>> I'll do more tests with the patch applied and see if any "critical" port
>> fails to build.
By "critical" I mean things like xerces-j, xalan and saxon that are
currently included in ANT_LIB, but should not be. Everything related to
XML can cause problems because of the JAXP classpath factory discovery
process.
I'll probably find some time to test those ports tonight.
Herve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4978A11A.1040408>