[jdom-interest] collections

[Jason Hunter]

Hmm, I don't really like the idea of fully qualifying all collections
classes in the src when the only gain is that it lets you build for JDK
1.1 under JDK 1.2 or later.  It seems reasonable if you want a custom
JDK 1.1 build from CVS you can get such a compiler.

Mike, I presume you're hitting this because you have an applet client
and so you don't naturally have a JDK 1.1 compiler sitting around, but
since we provide a JDK 1.1 JAR in each beta, even this is only an issue
for someone who wants the latest in CVS for JDK 1.1.  The price the
other way is that we have to remember to use FQCN's in the code which
isn't very natural.

Perhaps adding your cool little script to a FAQ entry would suffice?

-jh-

Michael Salmon wrote:
> 
> hi folks,
>     there is a problem with build.xml for the collections target. the first
> ten or so replacements are useless since there are no references (except in
> samples/) to any of the tokens to be replaced, eg. Collection is used
> instead of java.util.Collection. For this build.xml to work as designed
> the classnames must be absolute. This was not noticed because I assume
> the people building it and testing it were compiling with only java 1.1
> apis in their CLASSPATH so the only thing that was doing the trick was
> adding import com.sun.java.util.collections.* to the build CP.
> Since I think it is useful to be able to build jdom for 1.1 without running
> 1.1, attached is a patch to fix this. Basically it changes all refs to
> a collection class to the full path java.util.$collectionClass. I added
> one token replacement in build.xml also. Now you can build jdom for 1.1
> for real. though you'd have to be a lunatic like myself to want to.
> 
> ms-
> 
>   ------------------------------------------------------------------------
> 
>    jdom-collect.diffName: jdom-collect.diff
>                     Type: Plain Text (text/plain)