On 2001.08.21 21:07:53 -0400 Jason Dillon wrote:
> What xml jars did you have to update? Where did you update them?
I'll get back to you on that- mostly remove parser.jar and include
xalan/xerces from previous manual build.
>
> > XSLTransform, in ant.jar, uses several classes from Optional.jar, so
> > build.sh also has to include optional.jar on the local classpath.
>
> By adding optional.jar to the system classpath, all support jars will
> also
> have to be on the local classpath, which means that users will either
> have
> to use a custom ant, which contains all the correct bits in $ANT_HOME/lib
> or
> they will have to install the required versions of those jars into their
> $ANT_HOME/lib or the build system will not work.
Well, after making search set ANT_HOME instead of ANT, so the result is
useful, I put this at the end of build.sh and the manual builds more or
less
echo ant_home is $ANT_HOME
#kill preexisting classpath, we want our just found ant.
CLASSPATH=
#for manual only, include optional.jar on classpath- lousy ant style
task
#design has XSLProcess in ant.jar and loaded classes in optional.jar!!!
CLASSPATH=$ANT_HOME/lib/ext/optional.jar
export ANT ANT_HOME CLASSPATH
exec $ANT $ANT_OPTIONS "$@"
}
##
## Bootstrap
##
main "$@"
the "ant" script takes care of adding ant.jar to the classpath.
I'm a little confused. Are you intentionally including an ant distro in
jboss yet having the build.sh scripts not find it? It seems to me that the
jboss build system, since it includes a copy of ant, should use that copy
by default, and find it properly.
david jencks
ps.
here's my change to search:
search() {
search="$*"
for d in $search; do
ANT_HOME="`pwd`/$d"
ANT="$ANT_HOME/bin/ant"
if [ -x "$ANT" ]; then
# found one
#this is return value of function!
echo $ANT_HOME
break
fi
done
}
Returning ANT_HOME lets ANT_HOME be set, and ANT can be defined from it.
Returning ANT, as in cvs, seems to be useless -- ANT_HOME is never set, so
the ANT just set can't be found. At any rate this seemed to be what was
happening on my system.
>
> This is a rather huge problem with Ant 1.3 and how it loads classes. The
> easiest thing todo is insist that all users use the
> tools/apache/ant/bin/ant* to start the build (via build.* scripts) or
> they
> can update there own ANT_HOME to include all of the jars from
> tools/apache/ant/lib into their $ANT_HOME/lib.
>
> I origionally had things setup to use a version of ant with the correct
> libs, but reverted to the current style to allow people to run any
> standard
> ant dist directly.
>
> Unfortunatly the optional.jar makes this whole thing a huge mess. I do
> not
> have a good fix for this at the moment. Does anyone know if 1.4 fixes
> this
> crappy class loading problem?
>
> > The xml processor files in tools... are out of date versions.
>
> True, but they are from the ant 1.3 dist, so if we expect users to run a
> vanilla ant and get it to work, we have to use these.
>
> > Since mine works with ant 1.3 should I commit? or should we be forward
> > looking?
>
> I think we need to get an answer about how 1.4 might fix this and allow
> users to still use `ant` directly, or if that requirement is causing more
> problems than it solves.
>
> --jason
>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
>
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development