sebb wrote: > On 8 January 2012 16:43, Jörg Schaible <joerg.schai...@gmx.de> wrote: >> sebb wrote:
[snip] >> The main point for the profile was to suppress the failures of the >> buildnumber plugin automatically when building from the source tarball. > > With RC4, that can be achieved by defining buildNumber.skip=true. Fine. >> Actually the usage of the plugin means, that the release is not really >> repeatable (missing entries in the manifest) > > If you follow that logic to its conclusion, the buildNumber plugin is > effectively unusable. > >> unless checked out directly from the tag ... :-/ > > Which is what should *always* be done. > Releases should always be built from a clean checkout. > If not, they are not guaranteed repeatable, regardless of the use of > the buildNumber plugin. > There has recently been at least one Commons RC which was not built > from a clean checkout, and that caused the tag to differ from the > archives. > > The point of the manifest entry is to show what tag and revision was > used to build the release. > If the information happens to be missing, we are no worse off than > before, but if it is present, it can be potentially useful. Makes sense after all. Cheers, Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
