Hi Pete,
If you specify the skin like this:
<skin>
<groupId>org.apache.maven.skins</groupId>
<artifactId>maven-stylus-skin</artifactId>
</skin>
It will always use the latest version, which will match the main site
(though if it changes it won't be updated on the individual sites until
they are redeployed - but that's fine for now).
However, I do think adjusting the mojo archetype to include the normal
site descriptor and template docs is a good idea(in accordance with the
standard we came up with) - please create an issue for later so it isn't
forgotten. I wouldn't put maven plugin specific stuff in there, though.
HTH,
Brett
On 3/08/2006 1:08 PM, Pete Marvin King wrote:
Hello All,
There's a discussion on the list on making the standard maven plugin's
site skin uniform the the maven site.
There's a suggestion in MNG1212, the site skin can be pack in a jar. But
I'm wondering who will be responsible for
maintaining the plugin site skins? if there are changes in the maven
site skins then all plugin site skins needs to be
updated. is the plugin maintainer responsible for this? or whoever
changes the maven site skin?
I'm also proposing we make an archetype for the standard maven plugins
based on the mojo archetype, with
the current maven site skin being configured in the site descriptor. wdyt?
cheers,
pete marvin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Apache Maven - http://maven.apache.org/
Better Builds with Maven - http://library.mergere.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
