"Geir Magnusson Jr." wrote: > So it wouldn't be right to base JJAR fetches of those jars - except when you > specify the non-released latest. (JJAR lets you choose which version of a > jar you want...)
And some of the things I've been trying to build lately wanted the non-released latest. I would say that, if Sam wants to set it up, that GUMP could break out the JARs for a nighly build, and post them alongside the ZIPs and TARs in the folders that we already have. Meanwhile, when we make future releases, we might want to post the product's JAR alongside the ZIPS and/or TARs, so that there will be something for JJAR or whatever to fetch. Even without a gizmo, being able to download the JARs seperately, just by hyperlink, is becoming more and more important as the products start making better use of each other. Vincent and I are working on a very simple package, which with unit tests, ending needing eight Jakarta JARs. So to assemble everything, a user has to download about 20mb instead of like 800kb. A gizmo would be nice, but I'll happily settle for not having to delete 80% of what I'm downloading. I'm *not* trying to launch CJAN or JJAR here, but just confirm that distributing naked JARs is acceptable, and that we should encourage Jakarta products to do this as a standard practice. -- Ted Husted, Husted dot Com, Fairport NY USA. -- Building Java web applications with Struts. -- Tel +1 585 737-3463. -- Web http://www.husted.com/struts/ -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
