incubator-odf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dali Liu <wawal...@gmail.com>
Subject Re: Build failure downloading ODF 1.0 schema
Date Wed, 07 Nov 2012 01:34:28 GMT
I have meet this issue too, when I try start the build again, the build
process is going well.

2012/11/7 Rob Weir <robweir@apache.org>

> On Tue, Nov 6, 2012 at 11:46 AM, Rob Weir <robweir@apache.org> wrote:
> > On Tue, Nov 6, 2012 at 11:07 AM, Svante Schubert
> > <svante.schubert@gmail.com> wrote:
> >> Hi,
> >>
> >> this issue reminds me that it would be great if the files would be only
> >> downloaded once, for instance by making the files available to the Maven
> >> build system.
> >> If I remember it well, we had to remove these files due to unsolved
> >> license issues from the sources.
> >
> > I don't think there is an issue for putting these schemas on Maven
> > central repository if we want.  The issue was putting the schemas in
> > our Subversion repository.  Because the OASIS license did not permit
> > modification it was not considered to be an "open source" license, so
> > we could not include it.
> >
> > I think we asked OASIS once if they preferred to manage maven
> > submission of schemas themselves, to establish their own conventions
> > for coordinates, etc.  But we didn't get any response.
> >
>
> It appears that access is returned for those files.  I'm running a
> build now to confirm that there are no other issues.
>
> -Rob
>
>
> > -Rob
> >
> >> Perhaps someone has a more detailed idea how we are able to solve this,
> >> to speed up the build and drop the requirement to have Internet
> >> available for every build.
> >>
> >> Thanks,
> >> Svante
> >>
> >> On 06.11.2012 15:48, Rob Weir wrote:
> >>> [INFO] Error handling resource
> >>>
> >>> Embedded error: Failed to transfer file:
> >>>
> http://www.oasis-open.org/committees/download.php/12571/OpenDocument-schema-v1.0-os.rng
> .
> >>> Return code is: 500
> >>>
> >>>
> >>> I get this error when I build.  I also can reproduce it trying to
> >>> download the schema from OASIS through the browser.  This appears to
> >>> be an outage or configuration issue on their side.  I've reported the
> >>> issue to OASIS.
> >>>
> >>> -Rob
> >>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message