Am 2016-02-24 um 02:47 schrieb Hervé BOUTEMY:
Hi Michael,

nice work
I have one surprising result:
https://maven.apache.org/skins-archives/maven-fluido-skin-LATEST/sidebar/index.html

is it a bug in the test, or in the skin?

Neither nor. The reason for this is what I have described with a downgrade to Sitetools < 1.7. The IT chain still uses MSITE < 3.5 thus all request-bounded Velocity tools do not work. This is inherits the head from a parent and the rendering fails.

This is minor issue which will resolve as soon as we upgrade all parents to MSITE 3.5 and Fluido 1.5. I will update all ITs accordingly.

Not a showstopper for me.

Michael

Le mardi 23 février 2016 22:38:04 Michael Osipov a écrit :
Hi,

We solved 9 issues:
https://issues.apache.org/jira/browse/MSKINS/fixforversion/12332294

There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSKINS%20AND%20re
solution%20%3D%20Unresolved%20AND%20component%20%3D%20%22Fluido%20Skin%22%20
ORDER%20BY%20priority%20DESC

Staging repo:
https://repository.apache.org/content/repositories/maven-1253/
https://repository.apache.org/content/repositories/maven-1253/org/apache/mav
en/skins/maven-fluido-skin/1.5/maven-fluido-skin-1.5-source-release.zip

Source release checksum(s):
maven-fluido-skin-1.5-source-release.zip sha1:
3511dfdf2936c7ad6b248e83b5c4e6544700d4f6

Staging site:
https://maven.apache.org/components/skins-archives/maven-fluido-skin-LATEST/

Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html

Vote open for 72 hours.

[ ] +1
[ ] +0
[ ] -1

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]





---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to