re still there.
>
> Andy
>
>
>
> On 17/07/2020 21:58, Andy Seaborne wrote:
> > Thanks!
> >
> > Fingers-crossed - copying the job across will work. It's not like the
> > site build is unique for Jena.
> >
> > Good timing WRT the
If any help is needed with the re-creation of the jena-site job let me know
!
Roy
Op vr 17 jul. 2020 om 22:21 schreef Andy Seaborne
> Jenkins is on the move.
>
> I've asked for a Folder on the new system.
>
> I am so glad we have a simple build setup!
>
> Andy
>
>
> On 16/07/2020 17:33,
On 2020/03/08 10:29:17, Andy Seaborne wrote:
>
>
> On 08/03/2020 09:40, Roy Lenferink wrote:
> > Hi Andy,
> >
> > Good to be pro-active on this! However, I had yet to send reply to this
> > list that the actual move was
> > alread
Hi Andy,
Good to be pro-active on this! However, I had yet to send reply to this list
that the actual move was
already done :) See [1] for the actual change.
To verify: on jena.a.o the 'Edit this page' button is visible (meaning the site
is served from Git), and
this correctly redirects the
Perfect. Thanks Andy!
I used the following command for svn to git conversion:
git svn clone --trunk="https://svn.apache.org/repos/asf/jena/site/trunk/;
--authors-file=authors.txt
--ignore-paths="(content/documentation/javadoc|content/documentation/temp)"
jena-site
Best way to move forward is
After fiddling around a bit I managed to get the SVN history included as well
(had to run it multiple
times because of a temporary javadoc location at /content/documentation/temp).
All content is included except 'content/documentation/javadoc' and
'content/documentation/temp'.
I have renamed
ebsite would be good but personally I don't see it as a
> blocker.
>
> Andy
>
> On 25/02/2020 13:05, Roy Lenferink wrote:
> > [1] has just been updated. Easiest way to move forward (after the
> jena-site repository has been
> > requested and created) is to clo
erated website
- 'release-docs' => javadoc documentation available on /documentation/javadoc/*
Let me know if help is needed!
[1] https://github.com/rlenferink/jena-site
On 2020/02/25 12:24:47, Roy Lenferink wrote:
> Hi,
>
> The vote has passed with the following results:
>
&g
[
https://issues.apache.org/jira/browse/JENA-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17044410#comment-17044410
]
Roy Lenferink commented on JENA-1849:
-
Thanks for reporting. This seems like an ASF wide issue. Other
Hi,
The vote has passed with the following results:
+1 Bruno P. Kinoshita (binding)
+1 Andy Seaborne (binding)
+1 Adam Soroka (binding)
+1 Rob Vesse (binding)
+1 Chris Tomlinson (binding)
+1 Roy Lenferink (non-binding)
No -1 votes have been cast.
To continue I'll need some help from a PMC
Adding my +1 as well before closing the vote
On 2020/02/24 09:47:27, Rob Vesse wrote:
> +1
>
> Glad to see progress on this
>
> Rob
>
On 2020/02/21 18:24:08, Andy Seaborne wrote:
> Is the following description correct and complete?
>
> 1/ We have repo "jena-site"
>
> I prefer the website to be separate from the code and not in the
> source-release so we are free to publish the site at anytime.
This is indeed my
On 2020/02/19 23:06:31, Andy Seaborne wrote:
>
>
> On 19/02/2020 19:06, Andy Seaborne wrote:
> > I am finding some conversion issues around boxes and
> >
> > https://jena.apache.org/tutorials/rdf_api.html#ch-Statements
> > vs
> >
(inline comments)
On 2020/02/19 17:04:56, Andy Seaborne wrote:
>
> Sorry, I haven't had time to investigate all the machinery but if the
> javadoc is a different branch or repo, how does publish happen? And not
> happen for changes during the development cycle?
>
Publishing right now
Hi Jena community,
After last weeks proposal [1] I'd like to start a vote for moving over from the
current Apache CMS
(and SVN) to use Hugo and git :)
Short recap about Hugo: Hugo is a static site generator which is already having
more stars on
GitHub than Jekyll. It is easy to get started
Hi all,
I think most (definitely valid) points have been addressed. I'll start a vote
for this shortly.
Roy
On 2020/02/15 13:28:11, Roy Lenferink wrote:
> Hi Jena community,
>
> I noticed Jena is still serving its site from SVN with help of the Apache
> CMS. At the Apache Celi
Hi Andy,
Thanks for your answer!
I can confirm it is easier to use Hugo on Windows compared to Jekyll (I am
generating and testing
using the Ubuntu shell on Windows). Just downloading the tarball containing the
Hugo binary and
you're good to go. With Jekyll the process is a bit more complex as
rd party data sharing
> or unless there is approval from Apache legal.
>
> Claude
>
> On Sat, Feb 15, 2020 at 1:28 PM Roy Lenferink wrote:
>
> > Hi Jena community,
> >
> > I noticed Jena is still serving its site from SVN with help of the Apache
> > CMS. At the Ap
Hi Jena community,
I noticed Jena is still serving its site from SVN with help of the Apache CMS.
At the Apache Celix
project we decided to move away from the CMS and move towards git for serving
our website [1].
This because the CMS was introduced in 2010 and is currently not accepting any
19 matches
Mail list logo
