Plus link to the javadoc and the release notes please. And maybe the license.
It's going to look like an xdoc page :) Hen On Sun, Mar 9, 2008 at 6:04 PM, James Carman <[EMAIL PROTECTED]> wrote: > Perhaps there could be a maven plugin report for this? It could be > configured in the pom? > > <configuration> > <releases> > <release> > <name>1.0</name> > <date>01/01/1970</date> > <minimumJavaVersion>1.2</minimumJavaVersion> > </release> > </release> > </configuration> > > > > > On 3/9/08, Henri Yandell <[EMAIL PROTECTED]> wrote: > > On Sun, Mar 9, 2008 at 11:25 AM, Dennis Lundberg <[EMAIL PROTECTED]> wrote: > > > > > > At this point in time it seems that automating this comes with a few > > > hazards, that needs to be fixed. Until that is done I propose that we > > > advertise this manually in one of the site files. > > > > > > I'll go as far as to say automating is impossible. It'll only work if > > you make the bad assumption of site==documentation. > > > > ie) The site should say what the JDK version is for _all_ releases. > > > > Add it manually to: > > > > http://commons.apache.org/lang/release-history.html > > > > etc. > > > > Hen > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
