Hervé BOUTEMY wrote:
[...] site deployed.
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
I once got pretty upset as a user when I struggled with a non-functional
plugin feature documented on a plugin site just to find that the site
described unreleased stuff. While this particular problem doesn't apply
Hehe, I tried using the prepare-package phase a few days ago; it
didn't work
Benjamin Bentmann wrote:
Do we have some guideline for the deployed plugin site and its
state/contents?
I really wish using ${project.version} in the site url pattern was a more
common practice.
--
View this message in context:
until somebody puts it in the parent pom's URL and your project does
not override but has a different version
On 15/03/2009, lukewpatterson lukewpatter...@gmail.com wrote:
Benjamin Bentmann wrote:
Do we have some guideline for the deployed plugin site and its
state/contents?
I really
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
