On Sun, Mar 15, 2009 at 4:30 AM, Benjamin Bentmann
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
e/contents?
>>
>
> I really wish using ${project.version} in the site url pattern was a more
> common practice.
> --
> View this message in context:
> http://www.nabble.com/-maven-shade-plugin--Typo-in-examples-tp22518921p22523546.html
>
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:
http://www.nabble.com/-maven-shade-
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
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
fixed in svn and site deployed.
Don't hesitate to open a Jira issue and attach a patch if you find other
fixes.
Thank you
Hervé
Le dimanche 15 mars 2009, Paul a écrit :
> I was shading multiple jars needing services declarations and have been
> facing a typo issue, more precisely a "missing s"
I was shading multiple jars needing services declarations and have been facing
a typo issue, more precisely a "missing s" issue :)
In the maven site, the example named "" has a typo,:
ServiceResourceTransformer should be replaced by ServicesResourceTransformer.
/Paul
--