On Sun, Mar 15, 2009 at 4:30 AM, Benjamin Bentmann <benjamin.bentm...@udo.edu> wrote:
> Do we have some guideline for the deployed plugin site and its > state/contents? For instance, the site is now saying "Version: > 1.3-SNAPSHOT", its "Source Repository" report points to trunk instead of > maven-shade-plugin-1.2 and the source XRef report contains code from trunk, > i.e. the site is no longer in sync with the latest plugin release. I initially advocated publishing the latest docs, and we did it briefly, but as you noted it was too confusing. So the /plugins/maven-whatever-plugin website is intended to match the latest release. In addition, "versioned" docs are published at /plugins/maven-whatever-plugin-X.Y. I think this is done with the staging site url, the (config is in the plugins parent pom.) This works for snapshots, too, so if you're publishing the latest snapshot docs, they should go to -X.Y-SNAPSHOT url until a release happens and it's time to update the main site. One possible improvement would be to always publish the "versioned" docs, and make /plugins/maven-whatever-plugin a symlink to the the correct version. However that puts more work on the release manager to actually log into people.a.o and fix the link. We had a long discussion about this at the time, and the current setup was the least disruptive. (It doesn't affect all the links out there to /plugins/..., doesn't require the RM to do much extra work, and does provide historical "versioned" docs for the plugins.) -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
