There are two interesting items here: In this specific case, the main BU page is published from the git master branch which tracks version 2.x of the code. This branch is also used to generate the site which documents both 2.x and 1.x.
1.x just was released again, so the simplest way to document it was to update git master and publish the site. I did not publish the site from the 1.x branch which would have blown away the 2.x information. The second item of interest is that the code and site are both tightly coupled in a branch as a Maven build. This is the KISS solution, but has drawbacks as exemplified by the issue filed by this user. There is also the general issue that it would be nice to publish a site for the latest published version and the snapshot version. Plus the more for components that currently supports more than one major release lines, for example, BeanUtils. There is so simple way to do that, where simple means running a single Maven command line to publish the site. HTH, Gary On Mon, Mar 10, 2025, 19:28 Niall Pemberton <niall.pember...@gmail.com> wrote: > The Beanutils Download Page has a broken link to version 2.0.0-M2, which > has NOT been released yet (last release was 2.0.0-M1). > > https://commons.apache.org/proper/commons-beanutils/download_beanutils.cgi > > Also dependency page is showing M2 SNAPSHOT as the version > > https://commons.apache.org/proper/commons-beanutils/dependency-info.html > > Which was raised by a user in the following ticket: > https://issues.apache.org/jira/browse/BEANUTILS-575 > > Niall >
