> ok, I have my answer: the "1.7" specification version happened since Doxia 
> Sitetools 1.7.2: 1.7.1 did have 1.7.1 specification version (see details in 
> [1])
> 
> then this skin works perfectly with Maven Site Plugin 3.5.1 (as tested though 
> ITs...)
> 
> notice: perhaps we should create some documentation in m-site-p pages to show 
> which version of Doxia and Doxia Sitetools is used by which version of m-site-
> p, since such questions will happen
> any better idea than a FAW entry?

We can simply list to the dependencies report, can't we?

Michael

> Hervé
> 
> [1] https://issues.apache.org/jira/browse/DOXIASITETOOLS-171
> 
> Le mardi 8 novembre 2016, 03:17:12 CET Hervé BOUTEMY a écrit :
> > yes, nice team job, both at testing, reporting, analyzing and bugfixing
> > 
> > IIUC, that means that this skin is not usable until Maven Site Plugin 3.6 is
> > released, isn't it?
> > 
> > Regards,
> > 
> > Hervé
> > 
> > Le lundi 7 novembre 2016, 15:57:22 CET jieryn a écrit :
> > > Yaay! :) Nice job
> > > 
> > > On Mon, Nov 7, 2016 at 3:11 PM, Michael Osipov <micha...@apache.org> 
> wrote:
> > > > Am 2016-11-07 um 20:39 schrieb jieryn:
> > > >> https://github.com/jieryn/fluido-fail
> > > > 
> > > > Thanks, that was fast. I am able to reproduce the issue and found
> > > > quickly
> > > > the issue. It is *not* the skin.
> > > > 
> > > > Here it is: https://issues.apache.org/jira/browse/DOXIASITETOOLS-171
> > > > 
> > > > Thank you for testing, great work.
> > > > 
> > > > Michael
> > > > 
> > > >> On Mon, Nov 7, 2016 at 2:24 PM, Michael Osipov <micha...@apache.org>
> > > >> 
> > > >> wrote:
> > > >>> Am 2016-11-07 um 17:41 schrieb jieryn:
> > > >>>> I'm trying to test out the skin, thanks for making those updates!
> > > >>>> 
> > > >>>> I'm hitting a migration issue that I do not find a description/
> > > >>>> resolution on the site:
> > > >>>> 
> > > >>>> Caused by: org.apache.maven.doxia.siterenderer.RendererException:
> > > >>>> Cannot use skin: has 1.7.1 Doxia Sitetools prerequisite, but current
> > > >>>> is 1.7
> > > >>>> 
> > > >>>> 
> > > >>>> 
> > > >>>> Java 8, Maven 3.4.0-SNAPSHOT, m-site-p:3.6
> > > >>> 
> > > >>> This is strange becuase MSITE 3.6 which is now in vote by Hervé used
> > > >>> Doxia
> > > >>> Sitetools 1.7.3.
> > > >>> 
> > > >>> Can you create a small sample project for me to verify? You may work
> > > >>> around
> > > >>> by adding Sitetools dependency directly to maven-site-plugin.
> > > >>> 
> > > >>> Michael
> > > >>> 
> > > >>>> On Sun, Nov 6, 2016 at 7:10 AM, Michael Osipov <micha...@apache.org>
> > > >>>> 
> > > >>>> wrote:
> > > >>>>> Hi,
> > > >>>>> 
> > > >>>>> We solved 7 issues:
> > > >>>>> 
> > > >>>>> 
> > > >>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=123
> > > >>>>> 17
> > > >>>>> 926&version=12335711
> > > >>>>> 
> > > >>>>> There are still a couple of issues left in JIRA:
> > > >>>>> 
> > > >>>>> 
> > > >>>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSKINS%20
> > > >>>>> AN
> > > >>>>> D%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20%22Fluid
> > > >>>>> o%
> > > >>>>> 20Skin%22%20ORDER%20BY%20priority%20DESC
> > > >>>>> 
> > > >>>>> Staging repo:
> > > >>>>> https://repository.apache.org/content/repositories/maven-1296/
> > > >>>>> 
> > > >>>>> 
> > > >>>>> https://repository.apache.org/content/repositories/maven-1296/org/ap
> > > >>>>> ac
> > > >>>>> he/maven/skins/maven-fluido-skin/1.6/maven-fluido-skin-1.6-source-re
> > > >>>>> le
> > > >>>>> ase.zip
> > > >>>>> 
> > > >>>>> Source release checksum(s):
> > > >>>>> maven-fluido-skin-1.6-source-release.zip sha1:
> > > >>>>> e1e9877b1dbaa11c8f46735abf57d3d5ee9b3116
> > > >>>>> 
> > > >>>>> Staging site:
> > > >>>>> 
> > > >>>>> 
> > > >>>>> https://maven.apache.org/components/skins-archives/maven-fluido-skin
> > > >>>>> -L
> > > >>>>> ATEST/
> > > >>>>> 
> > > >>>>> Guide to testing staged releases:
> > > >>>>> http://maven.apache.org/guides/development/guide-testing-releases.ht
> > > >>>>> ml
> > > >>>>> 
> > > >>>>> Vote open for 72 hours.
> > > >>>>> 
> > > >>>>> [ ] +1
> > > >>>>> [ ] +0
> > > >>>>> [ ] -1
> > > >>>>> 
> > > >>>>> --------------------------------------------------------------------
> > > >>>>> -
> > > >>>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > >>>>> For additional commands, e-mail: dev-h...@maven.apache.org
> > > >>>> 
> > > >>>> ---------------------------------------------------------------------
> > > >>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > >>>> For additional commands, e-mail: dev-h...@maven.apache.org
> > > >>> 
> > > >>> ---------------------------------------------------------------------
> > > >>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > >>> For additional commands, e-mail: dev-h...@maven.apache.org
> > > >> 
> > > >> ---------------------------------------------------------------------
> > > >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > >> For additional commands, e-mail: dev-h...@maven.apache.org
> > > > 
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > > For additional commands, e-mail: dev-h...@maven.apache.org
> > > 
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > For additional commands, e-mail: dev-h...@maven.apache.org
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Reply via email to