Hi Thomas! > The result can be seen here: > > http://people.apache.org/~tn/commons/site/ > > The updated project can be found here: > > https://github.com/netomi/commons-site
I liked it! +1 :o) I think being able to see the latest version and its release date will be very useful for users and for developers of commons. Another thing I would like, but I'm not sure if that's doable or a good idea, is to have a list of known projects using the libraries. Like somewhere saying that Jenkins is using Jelly, Hadoop is using Math, CLI, Compress, HttpClient, etc, and so it goes. WDYT? Thanks! Bruno P. Kinoshita http://kinoshita.eti.br http://tupilabs.com ----- Original Message ----- > From: Thomas Neidhart <thomas.neidh...@gmail.com> > To: Commons Developers List <dev@commons.apache.org> > Cc: > Sent: Friday, November 1, 2013 9:36 PM > Subject: [site] Include latest release version / date for components > > Hi, > > I can remember that a while ago there was the suggestion to include the > latest release version + release date for each commons component on the > main page. > > The idea was really appealing to me, and I did an update of the > commons-site to include this information. > > The result can be seen here: > > http://people.apache.org/~tn/commons/site/ > > The updated project can be found here: > > https://github.com/netomi/commons-site > > What did I do? > > - create a script conf/parse-latest-release.py that parses the doap > file for each component at > http://svn.apache.org/repos/asf/commons/proper/ > - the script generates a properties file containing the parsed information > - use the properties-maven-plugin to load the properties during the > maven build > - move the index.xml to index.xml.vm to enable velocity filtering > and include for each component the respective properties > > The solution is quite simple, and the properties file can be manually > edited if necessary. > > So WDYT? > > btw. transaction is still listed as proper component, although already > moved to dormant in svn. > > Thomas > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
