On Thu, Mar 6, 2008 at 11:29 AM, Dennis Lundberg <[EMAIL PROTECTED]> wrote: > sebb wrote: > > On 05/03/2008, Niall Pemberton <[EMAIL PROTECTED]> wrote: > >> I just re-published all the component sites and notice that (by > >> mistake) it had used a patched copy of the > >> maven-project-info-reports-plugin that I have in my local repo > >> (sorry!). Anyway I submitted a patch to maven to include the Java > >> version on the dependencies page. The feedback I got was they prefer > >> it on the project summary page - so I submitted a patch for that as > >> well. > >> > >> Logging is an example of using different source/target versions: > >> http://commons.apache.org/logging/dependencies.html > >> http://commons.apache.org/logging/project-summary.html > > > > The version on the latter page shows 1.1.2-SNAPSHOT. > > Surely it should be 1.1.1 - which is the current version? > > This is what happens when you re-publish the site for a Maven 2 project, > post release. We should establish a policy (if there isn't one already) > regarding when, who and how it is allowed to re-publish a component's site.
Any committer; any time; whatever the process is :) Problem is the bad content, not the policy on site building. We should fix the content. Sites are not related to builds, that's confused maven for ages because it confuses sites with documentation. Not very practical; but: * package all the valuable reports for a release in one directory; that means the ones with content rather than the code quality ones. No one gives a crap about the quality of 1.0 etc. * Build a site around those versioned report directories. * Have a development report directory which is hooked to snapshot. Hen --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
