I'm reporting this bug for the string taglib, but I have a feeling the issue may be rampant through taglibs other than standard, which seems to have done a better job. There seem to be a number of problems with the source and release control for this project. (1) There are no source distributions available other than nightly builds. So the only way to recreate a particular release, or even find the software it's based on, is to checkout from cvs. YOU SHOULD CREATE A SOURCE DISTRO TO GO WITH YOUR BINARY DISTROS, AND POST IT. Standard does this appropriately. (2) Even within cvs, you don't seem to have properly tagged the release. For instance, I see a tag string-1-1_POSTRELEASE, but no string-1-1. I have no idea whether this is a tag for the 1.1 release, or something that came afterwards ("post") the release. YOU SHOULD CLEARLY TAG EACH SOURCE RELEASE WITHIN CVS. (3) But when I jump off the cliff and grab that unknown release tagged string-1-1_POSTRELEASE, it is not buildable. It relies on several files at the root above it (common.xml, etc) which were not tagged with the release. So while I can grab something off head that may work, I don't know what should have been used to build the release. ALL FILES NEEDED TO BUILD THE RELEASE SHOULD BE TAGGED/ RELEASED WITH THE RELEASE. Sorry for the shouting. I'm frustrated in trying to build your code. Please cleanup your release process. -jdb
I want to clarify what has been fixed here, which relates to the summary of your report <quote>Please cleanup your release process.</quote>; IMO, we have done that. It is extremely unfortunate that some (many) releases are missing the corresponding source distros and I believe I can safely speak for the entire Jakarta Taglibs team in saying we sincerely apologize for this significant oversight. The last release we've had was the RDC 1.0.0, for which you will find all of the items you indicate in your report, a source distro which contains all build related artifacts (including the ones external to the taglib source per se), as well as a SVN tag rdc-100. I have also changed the build scripts so the act of cutting a release produces a source distro in addition to the binary one, so this should be less of an issue in the future. We will be very careful regardless.
Thanks...!