[
https://issues.apache.org/jira/browse/JENA-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne reassigned JENA-1844:
---
Assignee: Andy Seaborne
> OpAsQuery: ORDER BY forgets Extend/Bind
>
[
https://issues.apache.org/jira/browse/JENA-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne reassigned JENA-1843:
---
Assignee: Andy Seaborne
> OpAsQuery: Wrong order of Extend/Bind
>
On 21/02/2020 18:59, Roy Lenferink wrote:
3/ There is a "jena-site:release-docs" branch for javadoc
Let's say this has /javadoc
If we have the following configured in the gitwcsub.cfg (INFRA stuff)
/www/jena.apache.org: $gitbox/jena-site
This means that the 'asf-site' contains
Valid point. The reason for not including the history was all the javadoc
stuff.
But the --ignore-paths can maybe help with that. I'll have a look if
possible.
Roy
Op wo 26 feb. 2020 om 12:11 schreef Andy Seaborne :
> That would not carry over the history although the history would include
>
[
https://issues.apache.org/jira/browse/JENA-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17045393#comment-17045393
]
Andy Seaborne commented on JENA-1815:
-
I haven't seen a PR come in so I can't say what might happen.
That would not carry over the history although the history would include
all the javadoc over time. Importing svn would keep the history
I don't know if a partial import can be done, without
content/documentation/javadoc/
"git svn --ignore-paths=" looks hopeful (I've never run "git svn"
[
https://issues.apache.org/jira/browse/JENA-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne closed JENA-1849.
---
> Website Download not functioning
>
>
> Key: JENA-1849
[
https://issues.apache.org/jira/browse/JENA-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-1849.
-
Resolution: Feedback Received
> Website Download not functioning
>
