i have a patch that uses commons-resources for i18n downstream in james but the component has never had a release and is now inactive. this is a bit of a shame since (in my experience) it is reasonably widely used.
some work would be needed to prepare it for a release. the build would need upgrading and all the headers replacing. the dependencies are old and most likely also need upgrading. but the total effort shouldn't be excessive. i'm willing to drive this forward. opinions? anyone else interested? - robert --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
