Geir Magnusson Jr. wrote: > > Sam, stay with us :) I didn't write that. I *know* GUMP ignores jars, and > it does it's job well. I think it *should* ignore the jars.
Count the number of ">"'s. ;-) I was quoting you quoting Stefano. >> Once the project interdepencies problem is fixed, I expect the only >> remaining impediment to a automatic fetcher of jars would be the Sun Binary >> Code License. > >I don't see much of a project interdependency problem either. JJAR can walk >the chain... OK, how do *YOU* solve the problem that Tomcat 4.0 includes a version of Tyrex which won't work with log4j 1.2? Or that the next release of batik won't work with the current release of fop? My assertion is that until we get more projects doing proper deprecation of interfaces, the set of consistent versions of an arbitrary set of projects will typically be the empty set except for those specific configurations built by a human release manager (and many times these seem to include non-release versions). > So indeed its the licence, but Craig will fix that for us... :) That would be real cool. But, I wouldn't hold my breath... - Sam Ruby P.S. The quote above with ">>" prefix was by me. ;-) -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
