[
http://jira.codehaus.org/browse/MSITE-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137816#action_137816
]
Arnaud Heritier commented on MSITE-256:
---------------------------------------
We are now using 2.0-beta-6 [1] with a custom skin [2] and it's working [3]
But we upgraded our hudson [4]
I think it was a side effect in hudson, even if I don't really understand how
it could happen
[1] https://forge.octo.com/svn/mtg/mtg-parent/trunk/pom.xml
[2] https://forge.octo.com/svn/mtg/mtg-site-skin/trunk/
[3] http://forge.octo.com/maven/sites/mtg/index.html
[4] https://forge.octo.com/hudson/job/MTG%20-%20site/
> Skin not applied in 2.0-beta-6-SNAPSHOT
> ---------------------------------------
>
> Key: MSITE-256
> URL: http://jira.codehaus.org/browse/MSITE-256
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-6
> Reporter: Arnaud Heritier
> Attachments: screenshot-1.jpg, screenshot-2.jpg
>
>
> The current SNAPSHOT of the maven-site-plugin breaks something in the skin
> resolution.
> You can reproduce it by building the web site of this project :
> http://forge.octo.com/svn/mtg/trunk/grails-maven-plugin
> There's a custom skin used in it.
> If you use the version 2.0-beta-5 for the site plugin in the parent pom you
> have the site correctly skinned.
> Not with the 2.0-beta-6-SNAPSHOT
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
