DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4429>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4429

Unwanted classpath re-ordering.

           Summary: Unwanted classpath re-ordering.
           Product: Ant
           Version: 1.3
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Other
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


This became apparent when I was compiling code that refered to the nodeset
()/nodelist() of  org.apache.xpath.objects.XObject.

This class exists in j2ee.jar, xalan.jar, xerces.jar..
Knowing this I explicitly specify the following in my build.xml: 

<path id="build.path">
   <pathelement location="classes"/>
       <fileset dir="3rdparty/lib">
           <include name="xalan.jar"/>
           <include name="xerces.jar"/>
           <include name="j2ee.jar"/>
       </fileset>
</path>

and my <javac> is:

<javac srcdir="${src}" destdir="${build}" includes="*/" 
classpathref="build.path" />


Now, I get symbol unresolved errors my references to XObject.nodeset()/nodelist
() methods because the classpath ends up being: 
3rdparty/j2ee.jar;3rdparty/xalan.jar;3rdparty/xerces.jar  when I <echo message> 
the build.path (when using a <parameter name="temp" value="build.path"/>)


Moving around the set of <include name=....>'s  does not appear to change the 
classpath.

Reply via email to