My guess is a find/replace for 1.0.0 to move from 1.0.0 to the 1.1.0
version of the book. This mistakenly changed the trunk/pom.xml to 1.1.0
instead of it staying in at 1.0.0. The commit that made this change is here:

r1837102 | lmccay | 2018-07-30 21:10:29 -0400 (Mon, 30 Jul 2018) | 1 line
Changed paths:
   M /knox/trunk/pom.xml

updated site version to 1.1.0

I don't think the pom.xml version actually matters as long as it matches.

Kevin Risden


On Tue, Oct 9, 2018 at 9:17 AM Lars Francke <[email protected]> wrote:

> Okay, thanks Kevin. That confirms my suspicion.
>
> @Philip: I don't know where you're getting that from. Could you try
> deleting the folder and try again? Are you using some kind of Maven mirror
> repository?
>
> I'm now fairly certain that this is a bug so I'll file an issue.
>
> On Tue, Oct 9, 2018 at 3:12 PM
> Kevin Risden
> <[email protected]>
> wrote:
>
> > New laptop just checked out knox-site and ran into the same error you
> did.
> > On my old laptop I have the gateway-site/1.0.0 folder.
> >
> > Kevin Risden
> >
> >
> > On Tue, Oct 9, 2018 at 9:02 AM Lars Francke <[email protected]>
> > wrote:
> >
> > > Thanks for checking. Are you sure that you don't have gateway-site in
> > your
> > > Maven cache locally?
> > >
> > > Should be in
> > ~/.m2/repository/org/apache/hadoop/gateway/gateway-site/1.0.0
> > >
> > > On Tue, Oct 9, 2018 at 2:42 PM Phil Zampino <[email protected]>
> wrote:
> > >
> > > > I just updated, and it built fine for me using 'ant generate'.
> > > >
> > > > On Tue, Oct 9, 2018 at 7:18 AM Lars Francke <[email protected]>
> > > > wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > I've tried to build the site using the Ant task but it fails almost
> > > > > immediately with the error message:
> > > > >
> > > > > [ERROR] [ERROR] Some problems were encountered while processing the
> > > POMs:
> > > > > [FATAL] Non-resolvable parent POM for
> > > > > org.apache.hadoop.gateway:markbook:[unknown-version]: Failure to
> find
> > > > > org.apache.hadoop.gateway:gateway-site:pom:1.0.0 in
> > > > > https://repo.maven.apache.org/maven2 was cached in the local
> > > repository,
> > > > > resolution will not be reattempted until the update interval of
> > central
> > > > has
> > > > > elapsed or updates are forced and 'parent.relativePath' points at
> > wrong
> > > > > local POM @ line 23, column 13
> > > > >
> > > > > And sure enough that version 1.0.0 doesn't exist in any repository.
> > The
> > > > > parent itself exists in the same repository but is at version
> 1.1.0.
> > > > >
> > > > > Am I missing something? I assume it works for you because you have
> > > > version
> > > > > 1.0.0 cached somewhere but shouldn't this really be updated to
> 1.1.0?
> > > > >
> > > > > Cheers,
> > > > > Lars
> > > > >
> > > >
> > >
> >
>

Reply via email to