You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jena.apache.org by bu...@apache.org on 2017/05/08 20:38:14 UTC
buildbot success in on jena-site-staging
The Buildbot has detected a restored build on builder jena-site-staging while building . Full details are available at:
https://ci.apache.org/builders/jena-site-staging/builds/202
Buildbot URL: https://ci.apache.org/
Buildslave for this Build: bb-cms-slave
Build Reason: The AnyBranchScheduler scheduler named 'on-jena-site-commit' triggered this build
Build Source Stamp: [branch jena/site] 1794455
Blamelist: andy
Build succeeded!
Sincerely,
-The Buildbot
Re: buildbot success in on jena-site-staging
Posted by so...@gmail.com.
Ah, cool, I've added that to the release workflow on the wiki.
---
A. Soroka
Andy Seaborne wrote on 5/10/17 11:36 AM:
>
>
> On 10/05/17 15:59, ajs6f@apache.org wrote:
>> I had already closed this release with the right date and opened 3.4.0.
>> Is that what you mean?
>
> And close all the "resolved" - I've taken care of this.
>
> (33 issues)
>
> Andy
>
>>
>> ---
>> A. Soroka
>>
>> Andy Seaborne wrote on 5/10/17 4:23 AM:
>>> JIRA?
>>>
>>> On 09/05/17 14:45, ajs6f@apache.org wrote:
>>>> Okay, just catching up to this-- thanks very much Andy for stepping in!
>>>>
>>>>
>>>> I think all that is left for me to do is apply the final git tag and
>>>> send announcements (I'm not thinking to send an announcement to
>>>> semantic-web@w3.org, or should I?).
>>>>
>>>> That was quite a ride. In California, Osma and I talked about some ideas
>>>> to improve the documentation infrastructure and one of them was to
>>>> switch from SVN. I don't know what our options are within Apache infra
>>>> but anything that avoids these massive commits could be interesting. At
>>>> the time, we were actually more interested in making contribution easier
>>>> by not having two different VCSs in play.
>>>>
>>>>
>>>> ---
>>>> A. Soroka
>>>>
>>>> Andy Seaborne wrote on 5/9/17 4:34 AM:
>>>>> Done and the site published (including version numbers on the download
>>>>> page).
>>>>>
>>>>> I think it was down to bad luck - "svn: E185004: Unexpected end of
>>>>> svndiff input" is a timeout (e.g. INFRA-8846) and trying at the busy
>>>>> time pushed it over the
>>>>> edge. It does seem to be a message that occurs in more than one
>>>>> situation.
>>>>>
>>>>> Once it started working again, things were quite smooth until a large
>>>>> module, then a glitch, then smooth again. I wonder if some backend
>>>>> system was hitting an
>>>>> unusual spike or had got itself into a confused state.
>>>>>
>>>>> Right, after that interrupt, what else needs doing?
>>>>>
>>>>> Andy
>>>>>
>>>>> On 08/05/17 22:20, Andy Seaborne wrote:
>>>>>> Adam - IF I get everything uploaded and the buildbot is happy, shall I
>>>>>> attempt to publish the site as well?
>>>>>>
>>>>>> Andy
>>>>>>
>>>>>> On 08/05/17 22:04, Andy Seaborne wrote:
>>>>>>> I got svn errors trying to do all the modules at once ...
>>>>>>>
>>>>>>> svn: E000110: Commit failed (details follow):
>>>>>>> svn: E000110: Error running context: Connection timed out
>>>>>>>
>>>>>>> and even larger modules seems to trigger this.
>>>>>>>
>>>>>>> I can try some more and then again tomorrow AM (Europe time) when
>>>>>>> things
>>>>>>> are less loaded.
>>>>>>>
>>>>>>> Andy
>>>>>>>
>>>>>>> On 08/05/17 21:41, Andy Seaborne wrote:
>>>>>>>> I'm rebuilding it from my machine and svn copy in case that is the
>>>>>>>> confusion - I'm spitting it into a delete then an add as well in
>>>>>>>> case
>>>>>>>> doing both in one huge step. with replacements is the problem.
>>>>>>>>
>>>>>>>> Andy
>>>>>>>>
>>>>>>>> On 08/05/17 21:39, ajs6f@apache.org wrote:
>>>>>>>>> Andy, was that just you reverting the several mis-aimed commits I
>>>>>>>>> made
>>>>>>>>> today?
>>>>>>>>>
>>>>>>>>> ---
>>>>>>>>> A. Soroka
>>>>>>>>>
>>>>>>>>> buildbot@apache.org wrote on 5/8/17 4:38 PM:
>>>>>>>>>> The Buildbot has detected a restored build on builder
>>>>>>>>>> jena-site-staging while building . Full details are available at:
>>>>>>>>>> https://ci.apache.org/builders/jena-site-staging/builds/202
>>>>>>>>>>
>>>>>>>>>> Buildbot URL: https://ci.apache.org/
>>>>>>>>>>
>>>>>>>>>> Buildslave for this Build: bb-cms-slave
>>>>>>>>>>
>>>>>>>>>> Build Reason: The AnyBranchScheduler scheduler named
>>>>>>>>>> 'on-jena-site-commit' triggered this build
>>>>>>>>>> Build Source Stamp: [branch jena/site] 1794455
>>>>>>>>>> Blamelist: andy
>>>>>>>>>>
>>>>>>>>>> Build succeeded!
>>>>>>>>>>
>>>>>>>>>> Sincerely,
>>>>>>>>>> -The Buildbot
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
Re: buildbot success in on jena-site-staging
Posted by Andy Seaborne <an...@apache.org>.
On 10/05/17 15:59, ajs6f@apache.org wrote:
> I had already closed this release with the right date and opened 3.4.0.
> Is that what you mean?
And close all the "resolved" - I've taken care of this.
(33 issues)
Andy
>
> ---
> A. Soroka
>
> Andy Seaborne wrote on 5/10/17 4:23 AM:
>> JIRA?
>>
>> On 09/05/17 14:45, ajs6f@apache.org wrote:
>>> Okay, just catching up to this-- thanks very much Andy for stepping in!
>>>
>>>
>>> I think all that is left for me to do is apply the final git tag and
>>> send announcements (I'm not thinking to send an announcement to
>>> semantic-web@w3.org, or should I?).
>>>
>>> That was quite a ride. In California, Osma and I talked about some ideas
>>> to improve the documentation infrastructure and one of them was to
>>> switch from SVN. I don't know what our options are within Apache infra
>>> but anything that avoids these massive commits could be interesting. At
>>> the time, we were actually more interested in making contribution easier
>>> by not having two different VCSs in play.
>>>
>>>
>>> ---
>>> A. Soroka
>>>
>>> Andy Seaborne wrote on 5/9/17 4:34 AM:
>>>> Done and the site published (including version numbers on the download
>>>> page).
>>>>
>>>> I think it was down to bad luck - "svn: E185004: Unexpected end of
>>>> svndiff input" is a timeout (e.g. INFRA-8846) and trying at the busy
>>>> time pushed it over the
>>>> edge. It does seem to be a message that occurs in more than one
>>>> situation.
>>>>
>>>> Once it started working again, things were quite smooth until a large
>>>> module, then a glitch, then smooth again. I wonder if some backend
>>>> system was hitting an
>>>> unusual spike or had got itself into a confused state.
>>>>
>>>> Right, after that interrupt, what else needs doing?
>>>>
>>>> Andy
>>>>
>>>> On 08/05/17 22:20, Andy Seaborne wrote:
>>>>> Adam - IF I get everything uploaded and the buildbot is happy, shall I
>>>>> attempt to publish the site as well?
>>>>>
>>>>> Andy
>>>>>
>>>>> On 08/05/17 22:04, Andy Seaborne wrote:
>>>>>> I got svn errors trying to do all the modules at once ...
>>>>>>
>>>>>> svn: E000110: Commit failed (details follow):
>>>>>> svn: E000110: Error running context: Connection timed out
>>>>>>
>>>>>> and even larger modules seems to trigger this.
>>>>>>
>>>>>> I can try some more and then again tomorrow AM (Europe time) when
>>>>>> things
>>>>>> are less loaded.
>>>>>>
>>>>>> Andy
>>>>>>
>>>>>> On 08/05/17 21:41, Andy Seaborne wrote:
>>>>>>> I'm rebuilding it from my machine and svn copy in case that is the
>>>>>>> confusion - I'm spitting it into a delete then an add as well in
>>>>>>> case
>>>>>>> doing both in one huge step. with replacements is the problem.
>>>>>>>
>>>>>>> Andy
>>>>>>>
>>>>>>> On 08/05/17 21:39, ajs6f@apache.org wrote:
>>>>>>>> Andy, was that just you reverting the several mis-aimed commits I
>>>>>>>> made
>>>>>>>> today?
>>>>>>>>
>>>>>>>> ---
>>>>>>>> A. Soroka
>>>>>>>>
>>>>>>>> buildbot@apache.org wrote on 5/8/17 4:38 PM:
>>>>>>>>> The Buildbot has detected a restored build on builder
>>>>>>>>> jena-site-staging while building . Full details are available at:
>>>>>>>>> https://ci.apache.org/builders/jena-site-staging/builds/202
>>>>>>>>>
>>>>>>>>> Buildbot URL: https://ci.apache.org/
>>>>>>>>>
>>>>>>>>> Buildslave for this Build: bb-cms-slave
>>>>>>>>>
>>>>>>>>> Build Reason: The AnyBranchScheduler scheduler named
>>>>>>>>> 'on-jena-site-commit' triggered this build
>>>>>>>>> Build Source Stamp: [branch jena/site] 1794455
>>>>>>>>> Blamelist: andy
>>>>>>>>>
>>>>>>>>> Build succeeded!
>>>>>>>>>
>>>>>>>>> Sincerely,
>>>>>>>>> -The Buildbot
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
Re: buildbot success in on jena-site-staging
Posted by aj...@apache.org.
I had already closed this release with the right date and opened 3.4.0. Is that what you mean?
---
A. Soroka
Andy Seaborne wrote on 5/10/17 4:23 AM:
> JIRA?
>
> On 09/05/17 14:45, ajs6f@apache.org wrote:
>> Okay, just catching up to this-- thanks very much Andy for stepping in!
>>
>>
>> I think all that is left for me to do is apply the final git tag and
>> send announcements (I'm not thinking to send an announcement to
>> semantic-web@w3.org, or should I?).
>>
>> That was quite a ride. In California, Osma and I talked about some ideas
>> to improve the documentation infrastructure and one of them was to
>> switch from SVN. I don't know what our options are within Apache infra
>> but anything that avoids these massive commits could be interesting. At
>> the time, we were actually more interested in making contribution easier
>> by not having two different VCSs in play.
>>
>>
>> ---
>> A. Soroka
>>
>> Andy Seaborne wrote on 5/9/17 4:34 AM:
>>> Done and the site published (including version numbers on the download
>>> page).
>>>
>>> I think it was down to bad luck - "svn: E185004: Unexpected end of
>>> svndiff input" is a timeout (e.g. INFRA-8846) and trying at the busy
>>> time pushed it over the
>>> edge. It does seem to be a message that occurs in more than one
>>> situation.
>>>
>>> Once it started working again, things were quite smooth until a large
>>> module, then a glitch, then smooth again. I wonder if some backend
>>> system was hitting an
>>> unusual spike or had got itself into a confused state.
>>>
>>> Right, after that interrupt, what else needs doing?
>>>
>>> Andy
>>>
>>> On 08/05/17 22:20, Andy Seaborne wrote:
>>>> Adam - IF I get everything uploaded and the buildbot is happy, shall I
>>>> attempt to publish the site as well?
>>>>
>>>> Andy
>>>>
>>>> On 08/05/17 22:04, Andy Seaborne wrote:
>>>>> I got svn errors trying to do all the modules at once ...
>>>>>
>>>>> svn: E000110: Commit failed (details follow):
>>>>> svn: E000110: Error running context: Connection timed out
>>>>>
>>>>> and even larger modules seems to trigger this.
>>>>>
>>>>> I can try some more and then again tomorrow AM (Europe time) when
>>>>> things
>>>>> are less loaded.
>>>>>
>>>>> Andy
>>>>>
>>>>> On 08/05/17 21:41, Andy Seaborne wrote:
>>>>>> I'm rebuilding it from my machine and svn copy in case that is the
>>>>>> confusion - I'm spitting it into a delete then an add as well in case
>>>>>> doing both in one huge step. with replacements is the problem.
>>>>>>
>>>>>> Andy
>>>>>>
>>>>>> On 08/05/17 21:39, ajs6f@apache.org wrote:
>>>>>>> Andy, was that just you reverting the several mis-aimed commits I
>>>>>>> made
>>>>>>> today?
>>>>>>>
>>>>>>> ---
>>>>>>> A. Soroka
>>>>>>>
>>>>>>> buildbot@apache.org wrote on 5/8/17 4:38 PM:
>>>>>>>> The Buildbot has detected a restored build on builder
>>>>>>>> jena-site-staging while building . Full details are available at:
>>>>>>>> https://ci.apache.org/builders/jena-site-staging/builds/202
>>>>>>>>
>>>>>>>> Buildbot URL: https://ci.apache.org/
>>>>>>>>
>>>>>>>> Buildslave for this Build: bb-cms-slave
>>>>>>>>
>>>>>>>> Build Reason: The AnyBranchScheduler scheduler named
>>>>>>>> 'on-jena-site-commit' triggered this build
>>>>>>>> Build Source Stamp: [branch jena/site] 1794455
>>>>>>>> Blamelist: andy
>>>>>>>>
>>>>>>>> Build succeeded!
>>>>>>>>
>>>>>>>> Sincerely,
>>>>>>>> -The Buildbot
>>>>>>>>
>>>>>>>>
>>>>>>>>
Re: buildbot success in on jena-site-staging
Posted by Andy Seaborne <an...@apache.org>.
JIRA?
On 09/05/17 14:45, ajs6f@apache.org wrote:
> Okay, just catching up to this-- thanks very much Andy for stepping in!
>
>
> I think all that is left for me to do is apply the final git tag and
> send announcements (I'm not thinking to send an announcement to
> semantic-web@w3.org, or should I?).
>
> That was quite a ride. In California, Osma and I talked about some ideas
> to improve the documentation infrastructure and one of them was to
> switch from SVN. I don't know what our options are within Apache infra
> but anything that avoids these massive commits could be interesting. At
> the time, we were actually more interested in making contribution easier
> by not having two different VCSs in play.
>
>
> ---
> A. Soroka
>
> Andy Seaborne wrote on 5/9/17 4:34 AM:
>> Done and the site published (including version numbers on the download
>> page).
>>
>> I think it was down to bad luck - "svn: E185004: Unexpected end of
>> svndiff input" is a timeout (e.g. INFRA-8846) and trying at the busy
>> time pushed it over the
>> edge. It does seem to be a message that occurs in more than one
>> situation.
>>
>> Once it started working again, things were quite smooth until a large
>> module, then a glitch, then smooth again. I wonder if some backend
>> system was hitting an
>> unusual spike or had got itself into a confused state.
>>
>> Right, after that interrupt, what else needs doing?
>>
>> Andy
>>
>> On 08/05/17 22:20, Andy Seaborne wrote:
>>> Adam - IF I get everything uploaded and the buildbot is happy, shall I
>>> attempt to publish the site as well?
>>>
>>> Andy
>>>
>>> On 08/05/17 22:04, Andy Seaborne wrote:
>>>> I got svn errors trying to do all the modules at once ...
>>>>
>>>> svn: E000110: Commit failed (details follow):
>>>> svn: E000110: Error running context: Connection timed out
>>>>
>>>> and even larger modules seems to trigger this.
>>>>
>>>> I can try some more and then again tomorrow AM (Europe time) when
>>>> things
>>>> are less loaded.
>>>>
>>>> Andy
>>>>
>>>> On 08/05/17 21:41, Andy Seaborne wrote:
>>>>> I'm rebuilding it from my machine and svn copy in case that is the
>>>>> confusion - I'm spitting it into a delete then an add as well in case
>>>>> doing both in one huge step. with replacements is the problem.
>>>>>
>>>>> Andy
>>>>>
>>>>> On 08/05/17 21:39, ajs6f@apache.org wrote:
>>>>>> Andy, was that just you reverting the several mis-aimed commits I
>>>>>> made
>>>>>> today?
>>>>>>
>>>>>> ---
>>>>>> A. Soroka
>>>>>>
>>>>>> buildbot@apache.org wrote on 5/8/17 4:38 PM:
>>>>>>> The Buildbot has detected a restored build on builder
>>>>>>> jena-site-staging while building . Full details are available at:
>>>>>>> https://ci.apache.org/builders/jena-site-staging/builds/202
>>>>>>>
>>>>>>> Buildbot URL: https://ci.apache.org/
>>>>>>>
>>>>>>> Buildslave for this Build: bb-cms-slave
>>>>>>>
>>>>>>> Build Reason: The AnyBranchScheduler scheduler named
>>>>>>> 'on-jena-site-commit' triggered this build
>>>>>>> Build Source Stamp: [branch jena/site] 1794455
>>>>>>> Blamelist: andy
>>>>>>>
>>>>>>> Build succeeded!
>>>>>>>
>>>>>>> Sincerely,
>>>>>>> -The Buildbot
>>>>>>>
>>>>>>>
>>>>>>>
Re: buildbot success in on jena-site-staging
Posted by Andy Seaborne <an...@apache.org>.
I took a look at the diff and it looked ok to me. I'm on a phone in rural
south France this week so could someone apply it? Thanks.
On Thu, 11 May 2017, 17:33 , <so...@gmail.com> wrote:
> No, I am waiting to see the new documentation for jena-text merged-- Osma,
> are we waiting on anything for that? Would you like me to do it?
>
> I'm happy to omit the Fuseki versions (I would be happy to merge their
> versioning).
>
> ---
> A. Soroka
>
> Andy Seaborne wrote on 5/11/17 11:31 AM:
> >
> >
> > On 09/05/17 14:45, ajs6f@apache.org wrote:
> >> Okay, just catching up to this-- thanks very much Andy for stepping in!
> >>
> >>
> >> I think all that is left for me to do is apply the final git tag and
> >> send announcements (I'm not thinking to send an announcement to
> >> semantic-web@w3.org, or should I?).
> >
> > I don't see the [ANN] message in the archives for users@ - did I miss
> it? did it get caught in a spam trap?
> >
> > Anyway, suggestion, doing away with Fuseki version numbers for
> simplicity:
> >
> >
> > Subject: [ANN] Apache Jena 3.3.0
> >
> > We are pleased to announce the release of Apache Jena 3.3.0.
> >
> > The major feature of this release is around jena-text.
> >
> > * jena-text: Upgrade to Lucene v6.4.1
> > Note : data will need to be reloaded into text indexes.
> >
> > * jena-text: Support for Elasticsearch: v5.2.2
> > New module:
> > jena-text-es
> >
> > * jena-text: Drop support for solr4j
> > Please comment on JENA-1301 if this affects you.
> > There has been very little users@ traffic about the solr
> > integration over the years.
> >
> > * Add VCARD4 (JENA-1205)
> > Contribution from Bart Hanssens
> >
> > * RDFParser (JENA-1306)
> > New low level, detailed setup of parsers for special cases.
> > RDFDataMgr is still the main way to read data (it now uses RDFParser).
> >
> > * General maintenance
> > 37 JIRA tickets
> > See https://s.apache.org/jena-3.3.0-jira
> >
> > == Obtaining Apache Jena 3.3.0
> >
> > * Via central.maven.org
> >
> > The main jars and their dependencies can used with:
> >
> > <dependency>
> > <groupId>org.apache.jena</groupId>
> > <artifactId>apache-jena-libs</artifactId>
> > <type>pom</type>
> > <version>3.3.0</version>
> > </dependency>
> >
> > Full details of all maven artifacts are described at:
> >
> > http://jena.apache.org/download/maven.html
> >
> > * As binary downloads
> >
> > Apache Jena libraries are available as a binary distribution of
> > libraries. For details of a global mirror copy of Jena binaries please
> see:
> >
> > http://jena.apache.org/download/
> >
> > * Source code for the release
> >
> > The signed source code of this release is available at:
> >
> > http://www.apache.org/dist/jena/source/
> >
> > and the signed master source for all Apache Jena releases is available
> > at: http://archive.apache.org/dist/jena/
> >
> > == Contributing
> >
> > If you would like to help out, a good place to look is the list of
> > unresolved JIRA at:
> >
> > http://s.apache.org/jena-jira-current
> >
> > or review pull requests at
> >
> > https://github.com/apache/jena/pulls
> >
> > or drop into the dev@ list.
> >
> > We use github pull requests and other ways for accepting code:
> > https://github.com/apache/jena/blob/master/CONTRIBUTING.md
> >
> > The Apache Jena development community
>
Re: buildbot success in on jena-site-staging
Posted by so...@gmail.com.
No, I am waiting to see the new documentation for jena-text merged-- Osma, are we waiting on anything for that? Would you like me to do it?
I'm happy to omit the Fuseki versions (I would be happy to merge their versioning).
---
A. Soroka
Andy Seaborne wrote on 5/11/17 11:31 AM:
>
>
> On 09/05/17 14:45, ajs6f@apache.org wrote:
>> Okay, just catching up to this-- thanks very much Andy for stepping in!
>>
>>
>> I think all that is left for me to do is apply the final git tag and
>> send announcements (I'm not thinking to send an announcement to
>> semantic-web@w3.org, or should I?).
>
> I don't see the [ANN] message in the archives for users@ - did I miss it? did it get caught in a spam trap?
>
> Anyway, suggestion, doing away with Fuseki version numbers for simplicity:
>
>
> Subject: [ANN] Apache Jena 3.3.0
>
> We are pleased to announce the release of Apache Jena 3.3.0.
>
> The major feature of this release is around jena-text.
>
> * jena-text: Upgrade to Lucene v6.4.1
> Note : data will need to be reloaded into text indexes.
>
> * jena-text: Support for Elasticsearch: v5.2.2
> New module:
> jena-text-es
>
> * jena-text: Drop support for solr4j
> Please comment on JENA-1301 if this affects you.
> There has been very little users@ traffic about the solr
> integration over the years.
>
> * Add VCARD4 (JENA-1205)
> Contribution from Bart Hanssens
>
> * RDFParser (JENA-1306)
> New low level, detailed setup of parsers for special cases.
> RDFDataMgr is still the main way to read data (it now uses RDFParser).
>
> * General maintenance
> 37 JIRA tickets
> See https://s.apache.org/jena-3.3.0-jira
>
> == Obtaining Apache Jena 3.3.0
>
> * Via central.maven.org
>
> The main jars and their dependencies can used with:
>
> <dependency>
> <groupId>org.apache.jena</groupId>
> <artifactId>apache-jena-libs</artifactId>
> <type>pom</type>
> <version>3.3.0</version>
> </dependency>
>
> Full details of all maven artifacts are described at:
>
> http://jena.apache.org/download/maven.html
>
> * As binary downloads
>
> Apache Jena libraries are available as a binary distribution of
> libraries. For details of a global mirror copy of Jena binaries please see:
>
> http://jena.apache.org/download/
>
> * Source code for the release
>
> The signed source code of this release is available at:
>
> http://www.apache.org/dist/jena/source/
>
> and the signed master source for all Apache Jena releases is available
> at: http://archive.apache.org/dist/jena/
>
> == Contributing
>
> If you would like to help out, a good place to look is the list of
> unresolved JIRA at:
>
> http://s.apache.org/jena-jira-current
>
> or review pull requests at
>
> https://github.com/apache/jena/pulls
>
> or drop into the dev@ list.
>
> We use github pull requests and other ways for accepting code:
> https://github.com/apache/jena/blob/master/CONTRIBUTING.md
>
> The Apache Jena development community
Re: buildbot success in on jena-site-staging
Posted by Andy Seaborne <an...@apache.org>.
On 09/05/17 14:45, ajs6f@apache.org wrote:
> Okay, just catching up to this-- thanks very much Andy for stepping in!
>
>
> I think all that is left for me to do is apply the final git tag and
> send announcements (I'm not thinking to send an announcement to
> semantic-web@w3.org, or should I?).
I don't see the [ANN] message in the archives for users@ - did I miss
it? did it get caught in a spam trap?
Anyway, suggestion, doing away with Fuseki version numbers for simplicity:
Subject: [ANN] Apache Jena 3.3.0
We are pleased to announce the release of Apache Jena 3.3.0.
The major feature of this release is around jena-text.
* jena-text: Upgrade to Lucene v6.4.1
Note : data will need to be reloaded into text indexes.
* jena-text: Support for Elasticsearch: v5.2.2
New module:
jena-text-es
* jena-text: Drop support for solr4j
Please comment on JENA-1301 if this affects you.
There has been very little users@ traffic about the solr
integration over the years.
* Add VCARD4 (JENA-1205)
Contribution from Bart Hanssens
* RDFParser (JENA-1306)
New low level, detailed setup of parsers for special cases.
RDFDataMgr is still the main way to read data (it now uses RDFParser).
* General maintenance
37 JIRA tickets
See https://s.apache.org/jena-3.3.0-jira
== Obtaining Apache Jena 3.3.0
* Via central.maven.org
The main jars and their dependencies can used with:
<dependency>
<groupId>org.apache.jena</groupId>
<artifactId>apache-jena-libs</artifactId>
<type>pom</type>
<version>3.3.0</version>
</dependency>
Full details of all maven artifacts are described at:
http://jena.apache.org/download/maven.html
* As binary downloads
Apache Jena libraries are available as a binary distribution of
libraries. For details of a global mirror copy of Jena binaries please see:
http://jena.apache.org/download/
* Source code for the release
The signed source code of this release is available at:
http://www.apache.org/dist/jena/source/
and the signed master source for all Apache Jena releases is available
at: http://archive.apache.org/dist/jena/
== Contributing
If you would like to help out, a good place to look is the list of
unresolved JIRA at:
http://s.apache.org/jena-jira-current
or review pull requests at
https://github.com/apache/jena/pulls
or drop into the dev@ list.
We use github pull requests and other ways for accepting code:
https://github.com/apache/jena/blob/master/CONTRIBUTING.md
The Apache Jena development community
Re: buildbot success in on jena-site-staging
Posted by aj...@apache.org.
Okay, just catching up to this-- thanks very much Andy for stepping in!
I think all that is left for me to do is apply the final git tag and send announcements (I'm not thinking to send an announcement to semantic-web@w3.org, or
should I?).
That was quite a ride. In California, Osma and I talked about some ideas to improve the documentation infrastructure and one of them was to switch from SVN. I
don't know what our options are within Apache infra but anything that avoids these massive commits could be interesting. At the time, we were actually more
interested in making contribution easier by not having two different VCSs in play.
---
A. Soroka
Andy Seaborne wrote on 5/9/17 4:34 AM:
> Done and the site published (including version numbers on the download page).
>
> I think it was down to bad luck - "svn: E185004: Unexpected end of svndiff input" is a timeout (e.g. INFRA-8846) and trying at the busy time pushed it over the
> edge. It does seem to be a message that occurs in more than one situation.
>
> Once it started working again, things were quite smooth until a large module, then a glitch, then smooth again. I wonder if some backend system was hitting an
> unusual spike or had got itself into a confused state.
>
> Right, after that interrupt, what else needs doing?
>
> Andy
>
> On 08/05/17 22:20, Andy Seaborne wrote:
>> Adam - IF I get everything uploaded and the buildbot is happy, shall I
>> attempt to publish the site as well?
>>
>> Andy
>>
>> On 08/05/17 22:04, Andy Seaborne wrote:
>>> I got svn errors trying to do all the modules at once ...
>>>
>>> svn: E000110: Commit failed (details follow):
>>> svn: E000110: Error running context: Connection timed out
>>>
>>> and even larger modules seems to trigger this.
>>>
>>> I can try some more and then again tomorrow AM (Europe time) when things
>>> are less loaded.
>>>
>>> Andy
>>>
>>> On 08/05/17 21:41, Andy Seaborne wrote:
>>>> I'm rebuilding it from my machine and svn copy in case that is the
>>>> confusion - I'm spitting it into a delete then an add as well in case
>>>> doing both in one huge step. with replacements is the problem.
>>>>
>>>> Andy
>>>>
>>>> On 08/05/17 21:39, ajs6f@apache.org wrote:
>>>>> Andy, was that just you reverting the several mis-aimed commits I made
>>>>> today?
>>>>>
>>>>> ---
>>>>> A. Soroka
>>>>>
>>>>> buildbot@apache.org wrote on 5/8/17 4:38 PM:
>>>>>> The Buildbot has detected a restored build on builder
>>>>>> jena-site-staging while building . Full details are available at:
>>>>>> https://ci.apache.org/builders/jena-site-staging/builds/202
>>>>>>
>>>>>> Buildbot URL: https://ci.apache.org/
>>>>>>
>>>>>> Buildslave for this Build: bb-cms-slave
>>>>>>
>>>>>> Build Reason: The AnyBranchScheduler scheduler named
>>>>>> 'on-jena-site-commit' triggered this build
>>>>>> Build Source Stamp: [branch jena/site] 1794455
>>>>>> Blamelist: andy
>>>>>>
>>>>>> Build succeeded!
>>>>>>
>>>>>> Sincerely,
>>>>>> -The Buildbot
>>>>>>
>>>>>>
>>>>>>
Re: buildbot success in on jena-site-staging
Posted by Andy Seaborne <an...@apache.org>.
Done and the site published (including version numbers on the download
page).
I think it was down to bad luck - "svn: E185004: Unexpected end of
svndiff input" is a timeout (e.g. INFRA-8846) and trying at the busy
time pushed it over the edge. It does seem to be a message that occurs
in more than one situation.
Once it started working again, things were quite smooth until a large
module, then a glitch, then smooth again. I wonder if some backend
system was hitting an unusual spike or had got itself into a confused state.
Right, after that interrupt, what else needs doing?
Andy
On 08/05/17 22:20, Andy Seaborne wrote:
> Adam - IF I get everything uploaded and the buildbot is happy, shall I
> attempt to publish the site as well?
>
> Andy
>
> On 08/05/17 22:04, Andy Seaborne wrote:
>> I got svn errors trying to do all the modules at once ...
>>
>> svn: E000110: Commit failed (details follow):
>> svn: E000110: Error running context: Connection timed out
>>
>> and even larger modules seems to trigger this.
>>
>> I can try some more and then again tomorrow AM (Europe time) when things
>> are less loaded.
>>
>> Andy
>>
>> On 08/05/17 21:41, Andy Seaborne wrote:
>>> I'm rebuilding it from my machine and svn copy in case that is the
>>> confusion - I'm spitting it into a delete then an add as well in case
>>> doing both in one huge step. with replacements is the problem.
>>>
>>> Andy
>>>
>>> On 08/05/17 21:39, ajs6f@apache.org wrote:
>>>> Andy, was that just you reverting the several mis-aimed commits I made
>>>> today?
>>>>
>>>> ---
>>>> A. Soroka
>>>>
>>>> buildbot@apache.org wrote on 5/8/17 4:38 PM:
>>>>> The Buildbot has detected a restored build on builder
>>>>> jena-site-staging while building . Full details are available at:
>>>>> https://ci.apache.org/builders/jena-site-staging/builds/202
>>>>>
>>>>> Buildbot URL: https://ci.apache.org/
>>>>>
>>>>> Buildslave for this Build: bb-cms-slave
>>>>>
>>>>> Build Reason: The AnyBranchScheduler scheduler named
>>>>> 'on-jena-site-commit' triggered this build
>>>>> Build Source Stamp: [branch jena/site] 1794455
>>>>> Blamelist: andy
>>>>>
>>>>> Build succeeded!
>>>>>
>>>>> Sincerely,
>>>>> -The Buildbot
>>>>>
>>>>>
>>>>>
Re: buildbot success in on jena-site-staging
Posted by Andy Seaborne <an...@apache.org>.
Adam - IF I get everything uploaded and the buildbot is happy, shall I
attempt to publish the site as well?
Andy
On 08/05/17 22:04, Andy Seaborne wrote:
> I got svn errors trying to do all the modules at once ...
>
> svn: E000110: Commit failed (details follow):
> svn: E000110: Error running context: Connection timed out
>
> and even larger modules seems to trigger this.
>
> I can try some more and then again tomorrow AM (Europe time) when things
> are less loaded.
>
> Andy
>
> On 08/05/17 21:41, Andy Seaborne wrote:
>> I'm rebuilding it from my machine and svn copy in case that is the
>> confusion - I'm spitting it into a delete then an add as well in case
>> doing both in one huge step. with replacements is the problem.
>>
>> Andy
>>
>> On 08/05/17 21:39, ajs6f@apache.org wrote:
>>> Andy, was that just you reverting the several mis-aimed commits I made
>>> today?
>>>
>>> ---
>>> A. Soroka
>>>
>>> buildbot@apache.org wrote on 5/8/17 4:38 PM:
>>>> The Buildbot has detected a restored build on builder
>>>> jena-site-staging while building . Full details are available at:
>>>> https://ci.apache.org/builders/jena-site-staging/builds/202
>>>>
>>>> Buildbot URL: https://ci.apache.org/
>>>>
>>>> Buildslave for this Build: bb-cms-slave
>>>>
>>>> Build Reason: The AnyBranchScheduler scheduler named
>>>> 'on-jena-site-commit' triggered this build
>>>> Build Source Stamp: [branch jena/site] 1794455
>>>> Blamelist: andy
>>>>
>>>> Build succeeded!
>>>>
>>>> Sincerely,
>>>> -The Buildbot
>>>>
>>>>
>>>>
Re: buildbot success in on jena-site-staging
Posted by Andy Seaborne <an...@apache.org>.
I got svn errors trying to do all the modules at once ...
svn: E000110: Commit failed (details follow):
svn: E000110: Error running context: Connection timed out
and even larger modules seems to trigger this.
I can try some more and then again tomorrow AM (Europe time) when things
are less loaded.
Andy
On 08/05/17 21:41, Andy Seaborne wrote:
> I'm rebuilding it from my machine and svn copy in case that is the
> confusion - I'm spitting it into a delete then an add as well in case
> doing both in one huge step. with replacements is the problem.
>
> Andy
>
> On 08/05/17 21:39, ajs6f@apache.org wrote:
>> Andy, was that just you reverting the several mis-aimed commits I made
>> today?
>>
>> ---
>> A. Soroka
>>
>> buildbot@apache.org wrote on 5/8/17 4:38 PM:
>>> The Buildbot has detected a restored build on builder
>>> jena-site-staging while building . Full details are available at:
>>> https://ci.apache.org/builders/jena-site-staging/builds/202
>>>
>>> Buildbot URL: https://ci.apache.org/
>>>
>>> Buildslave for this Build: bb-cms-slave
>>>
>>> Build Reason: The AnyBranchScheduler scheduler named
>>> 'on-jena-site-commit' triggered this build
>>> Build Source Stamp: [branch jena/site] 1794455
>>> Blamelist: andy
>>>
>>> Build succeeded!
>>>
>>> Sincerely,
>>> -The Buildbot
>>>
>>>
>>>
Re: buildbot success in on jena-site-staging
Posted by Andy Seaborne <an...@apache.org>.
I'm rebuilding it from my machine and svn copy in case that is the
confusion - I'm spitting it into a delete then an add as well in case
doing both in one huge step. with replacements is the problem.
Andy
On 08/05/17 21:39, ajs6f@apache.org wrote:
> Andy, was that just you reverting the several mis-aimed commits I made
> today?
>
> ---
> A. Soroka
>
> buildbot@apache.org wrote on 5/8/17 4:38 PM:
>> The Buildbot has detected a restored build on builder
>> jena-site-staging while building . Full details are available at:
>> https://ci.apache.org/builders/jena-site-staging/builds/202
>>
>> Buildbot URL: https://ci.apache.org/
>>
>> Buildslave for this Build: bb-cms-slave
>>
>> Build Reason: The AnyBranchScheduler scheduler named
>> 'on-jena-site-commit' triggered this build
>> Build Source Stamp: [branch jena/site] 1794455
>> Blamelist: andy
>>
>> Build succeeded!
>>
>> Sincerely,
>> -The Buildbot
>>
>>
>>
Re: buildbot success in on jena-site-staging
Posted by aj...@apache.org.
Andy, was that just you reverting the several mis-aimed commits I made today?
---
A. Soroka
buildbot@apache.org wrote on 5/8/17 4:38 PM:
> The Buildbot has detected a restored build on builder jena-site-staging while building . Full details are available at:
> https://ci.apache.org/builders/jena-site-staging/builds/202
>
> Buildbot URL: https://ci.apache.org/
>
> Buildslave for this Build: bb-cms-slave
>
> Build Reason: The AnyBranchScheduler scheduler named 'on-jena-site-commit' triggered this build
> Build Source Stamp: [branch jena/site] 1794455
> Blamelist: andy
>
> Build succeeded!
>
> Sincerely,
> -The Buildbot
>
>
>