I've also seen this problem. Last year the question about JDK version compatibility came up on the mailing list -- it turned out that it wasn't really clear even internally. (I think we documented this somewhere as JDK 1.3 for runtime, 1.4 for compiling). But I bet a lot of this is oral documentation or just assumed.
WILL On 9/12/06, Daniel F. Savarese <[EMAIL PROTECTED]> wrote:
In message <[EMAIL PROTECTED]>, "Yoav Shapira" writes: >(e.g. build.properties). I'm hesitant to have a separate web page >just to list dependencies unless that page is auto-generated (as is I agree. I'm sure there's a way to autogenerate a master table for all the mavenized projects, but since I'm not volunteering to do it, I'm not going to suggest it. I haven't seen anyone listing their JDK requirements in the maven dependency report. Could we then just ask mavenized projects to add their minimum JDK requirement to the dependencies report (I've never tried entering a 'fake' entry and ant projects to add the info to their docs if they don't already have it? These situations are always weird for me since I'm not the one experiencing the actual issue, yet have been asked to raise it. However, I think it's a reasonable reminder that despite all the progress Jakarta has made, users still have problems navigating our documentation. daniel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Forio Business Simulations Will Glass-Husain [EMAIL PROTECTED] www.forio.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
