[jira] [Resolved] (SLING-7172) Change SlingQuery Pipe API

2017-10-22 Thread Nicolas Peltier (JIRA) 

 [ 
https://issues.apache.org/jira/browse/SLING-7172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nicolas Peltier resolved SLING-7172.

   Resolution: Fixed
Fix Version/s: pipes 1.2.0

> Change SlingQuery Pipe API
> --
>
> Key: SLING-7172
> URL: https://issues.apache.org/jira/browse/SLING-7172
> Project: Sling
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: pipes 1.1.0
>Reporter: Nicolas Peltier
> Fix For: pipes 1.2.0
>
>
> currently SlingQuery Pipe expression is used for retrieving resources using 
> getChildren. This should be calling "find" which is more natural for 
> developers.
> getChildren should still be optional (flag isDeep=false)? 
> we should update to 4.0 version



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SLING-7161) Update site to reference git instead of svn

2017-10-22 Thread Robert Munteanu (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-7161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214412#comment-16214412
 ] 

Robert Munteanu commented on SLING-7161:


{quote}Do we already have a technical user with read access to Apache or can we 
request one from INFRA?{quote}

I asked at 
https://lists.apache.org/thread.html/52199fba646b1c91edb79d2e022b0b4eecb7053807154d426a6a96c5@%3Cbuilds.apache.org%3E
 , no reply yet.

Given that we need to issue lots of requests to the GitHub API and:

- it's slow
- it can become rate limited
- it becomes complicated to manage security credentials everywhere

I would suggest that we do the polling in a single place and write the output 
to git. For instance have a Jenkins job that regenerates the project list in 
XML or JSON format every 1 hour, and then every other 'client' can just use 
that:

- Jenkins seed job
- repo manifest generation script
- website

I think it's faster, easier to manage and more secure. Also, at least for now, 
we can regenerate the "master" repo list manually.

> Update site to reference git instead of svn
> ---
>
> Key: SLING-7161
> URL: https://issues.apache.org/jira/browse/SLING-7161
> Project: Sling
>  Issue Type: Sub-task
>  Components: Site
>Reporter: Robert Munteanu
>
> All the https://svn.apache.org/repos/asf/sling/... tags should be rewritten 
> to the git repos.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SLING-7140) Support redirects to URLs provided by the underlying datastore.

2017-10-22 Thread Carsten Ziegeler (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-7140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214381#comment-16214381
 ] 

Carsten Ziegeler commented on SLING-7140:
-

external sounds good to me (ext is ambigious, providers, extension or convert 
too general)

> Support redirects to URLs provided by the underlying datastore.
> ---
>
> Key: SLING-7140
> URL: https://issues.apache.org/jira/browse/SLING-7140
> Project: Sling
>  Issue Type: Bug
>  Components: Servlets
>Affects Versions: Servlets Get 2.1.26, JCR Resource 3.0.4
>Reporter: Ian Boston
>Assignee: Ian Boston
> Fix For: Servlets Get 2.1.28, JCR Resource 3.0.6, API 2.16.4, 
> Resource Resolver 1.5.32
>
>
> Incorporate changes to allow OAK-6575 to work in Sling, 
> Patch available at 
> https://github.com/apache/sling/compare/trunk...ieb:OAK-6575-3-2
> Cant me applied until OAK-6575 is released in a version suitable for use in 
> Sling.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: [sling-site] branch asf-site updated: Source code moved to Git

2017-10-22 Thread Konrad Windszus 
To me it seems, that this update was only pushed to asf-site but I fail to see 
the according commit to the source MD files in the master branch.
The last commit on 
https://github.com/apache/sling-site/blob/master/src/main/jbake/content/project-information.md
 was from the 8th of October from Robert.

@Bertrand: Could it be that you forgot to push those commits upstream?

We should IMHO prevent the site from being published when the latest state has 
not been pushed to the master branch, but it seems that the Maven SCM Publish 
Plugin does not have an option yet to enforce that [0].
Konrad

[0] - 
http://maven.apache.org/plugins/maven-scm-publish-plugin/publish-scm-mojo.html).


On 2017-10-19 12:51, bdelacre...@apache.org wrote: 
> This is an automated email from the ASF dual-hosted git repository.
> 
> bdelacretaz pushed a commit to branch asf-site
> in repository https://gitbox.apache.org/repos/asf/sling-site.git
> 
> 
> The following commit(s) were added to refs/heads/asf-site by this push:
>  new 947d44e  Source code moved to Git
> 947d44e is described below
> 
> commit 947d44e8ba12a85aabd00ee8fd6be8aa8d6108d0
> Author: Bertrand Delacretaz 
> AuthorDate: Thu Oct 19 12:50:09 2017 +0200
> 
> Source code moved to Git
> ---
>  project-information.html | 36 +---
>  tags/adaptTo.html|  2 ++
>  tags/api.html|  2 ++
>  tags/authentication.html |  2 ++
>  tags/bundles.html|  2 ++
>  tags/caching.html|  2 ++
>  tags/commons.html|  2 ++
>  tags/community.html  |  2 ++
>  tags/configuration.html  |  2 ++
>  tags/contentdistribution.html|  2 ++
>  tags/contentloading.html |  2 ++
>  tags/core.html   |  2 ++
>  tags/databases.html  |  2 ++
>  tags/development.html|  2 ++
>  tags/discovery.html  |  2 ++
>  tags/documentation.html  |  2 ++
>  tags/downloads.html  |  2 ++
>  tags/eclipse.html|  2 ++
>  tags/editors.html|  2 ++
>  tags/embedding.html  |  2 ++
>  tags/error.html  |  2 ++
>  tags/errorhandling.html  |  2 ++
>  tags/events.html |  2 ++
>  tags/featureflags.html   |  2 ++
>  tags/formauth.html   |  2 ++
>  tags/{commons.html => git.html}  |  4 +++-
>  tags/{mocks.html => github.html} |  4 +++-
>  tags/groovy.html |  2 ++
>  tags/healthchecks.html   |  2 ++
>  tags/htl.html|  2 ++
>  tags/html.html   |  2 ++
>  tags/i18n.html   |  2 ++
>  tags/ide.html|  2 ++
>  tags/installer.html  |  2 ++
>  tags/issuetracker.html   |  2 ++
>  tags/jackrabbit.html |  2 ++
>  tags/jcr.html|  2 ++
>  tags/jobs.html   |  2 ++
>  tags/jsp.html|  2 ++
>  tags/launchers.html  |  2 ++
>  tags/launchpad.html  |  2 ++
>  tags/logging.html|  2 ++
>  tags/mailinglists.html   |  2 ++
>  tags/maven.html  |  2 ++
>  tags/metrics.html|  2 ++
>  tags/mimetypes.html  |  2 ++
>  tags/mocks.html  |  2 ++
>  tags/models.html |  2 ++
>  tags/modules.html|  2 ++
>  tags/news.html   |  2 ++
>  tags/nodetypes.html  |  2 ++
>  tags/nosql.html  |  2 ++
>  tags/oak.html|  2 ++
>  tags/obsolete.html   |  2 ++
>  tags/openid.html |  2 ++
>  tags/operations.html |  2 ++
>  tags/osgi.html   |  2 ++
>  tags/pipes.html  |  2 ++
>  tags/pmc.html|  2 ++
>  tags/postprocessing.html |  2 ++
>  tags/postservlet.html|  2 ++
>  tags/publishing.html |  2 ++
>  tags/repoinit.html   |  2 ++
>  tags/repository.html |  2 ++
>  tags/requests.html   |  2 ++
>  tags/resourcemappings.html   |  2 ++
>  tags/resourceproviders.html  |  2 ++
>  tags/resourceresolver.html   |  2 ++
>  tags/resources.html  |  2 ++
>  tags/runmodes.html   |  2 ++
>  tags/scheduling.html |  2 ++
>  tags/scriptresolver.html |  2 ++
>  tags/scripts.html|  2 ++
>  tags/security.html   |  2 ++
>  tags/serviceusers.html   |  2 ++
>  tags/servletresolver.html|  2 ++
>  tags/servlets.html   |  2 ++
>  tags/slingquery.html |  2 ++
>  tags/slingstart.html |  2 ++
>  tags/sourcecode.html |  2 ++
>  tags/testing.html|  2 ++
>  tags/threads.html|  2 ++
>  tags/thymeleaf.html  |  2 ++
>  tags/tutorial.html

[jira] [Commented] (SLING-7161) Update site to reference git instead of svn

2017-10-22 Thread Konrad Windszus (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-7161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214366#comment-16214366
 ] 

Konrad Windszus commented on SLING-7161:


I created a new branch for listing all Git repo urls with a dedicated JBake 
template leveraging the Github API at 
https://github.com/apache/sling-site/tree/scm-project-url-list in the site. 
There are still some issues with that branch namely:

# a lot of code duplication between {{page.tpl}} and {{scm-projects.tpl}}. IMHO 
a lot more should be moved into {{layout/main.tpl}}, like the breadcrumb.
# inconsistent spacing in Groovy template (sometimes tabs, sometimes spaces). 
Can we agree on what should be used here?
# Github API has some rate limitation in place. Since just iterating over all 
Apache repos requires a lot of requests (due to pagination) this hits us with 
the second run of JBake. We should try out what limits there are with an OAuth 
authentication. Do we already have a technical user with read access to Apache 
or can we request one from INFRA?

> Update site to reference git instead of svn
> ---
>
> Key: SLING-7161
> URL: https://issues.apache.org/jira/browse/SLING-7161
> Project: Sling
>  Issue Type: Sub-task
>  Components: Site
>Reporter: Robert Munteanu
>
> All the https://svn.apache.org/repos/asf/sling/... tags should be rewritten 
> to the git repos.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: What to do with github.com/apache/sling (was [git] Migration to git repositories sort of complete)

2017-10-22 Thread Ian Boston 
Hi,
Good solution. One small modification to help anyone get to the old tree.

Rather than switching the main branch and making it empty,  if you branch
trunk to a new branch "archive" and then make trunk empty as you suggest,
it will be possible to point anyone who gets a 404 to the new "archive"
branch. Tagging the last commit from SVN would also help keep a permanent
record.

Only those URLs that are not pointing to a commit/tag/branch (other than
trunk) will be broken and the README left in trunk can explain how to
change the URL.

Best Regards
Ian

On 22 October 2017 at 14:08, Justin Edelson 
wrote:

> +1
>
> Great solution.
> On Sat, Oct 21, 2017 at 3:26 PM Robert Munteanu 
> wrote:
>
> > On Fri, 2017-10-20 at 23:19 +0200, Robert Munteanu wrote:
> > > I guess the 'minimal damage' approach would be to switch the main
> > > branch and make that empty, with just a README.md .
> > >
> > > Would need to talk to infra to see how that can happen. Unless anyone
> > > is opposed, I would create a branch called 'archived' with the
> > > following README.md contents:
> >
> > Here's how it would look once switched:
> >
> >   https://github.com/apache/sling/tree/archived
> >
> > Robert
> >
>

Re: What to do with github.com/apache/sling (was [git] Migration to git repositories sort of complete)

2017-10-22 Thread Justin Edelson 
+1

Great solution.
On Sat, Oct 21, 2017 at 3:26 PM Robert Munteanu  wrote:

> On Fri, 2017-10-20 at 23:19 +0200, Robert Munteanu wrote:
> > I guess the 'minimal damage' approach would be to switch the main
> > branch and make that empty, with just a README.md .
> >
> > Would need to talk to infra to see how that can happen. Unless anyone
> > is opposed, I would create a branch called 'archived' with the
> > following README.md contents:
>
> Here's how it would look once switched:
>
>   https://github.com/apache/sling/tree/archived
>
> Robert
>

[jira] [Commented] (SLING-7140) Support redirects to URLs provided by the underlying datastore.

2017-10-22 Thread Ian Boston (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-7140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214260#comment-16214260
 ] 

Ian Boston commented on SLING-7140:
---

Agreed. The version change in the ResourceResolver didn't feel right at the 
time. Strange that none of the IT tests I ran picked up the other issues. 
Probably because PaxExam doesn't test the current trunk unless to change it 
also.

I put the interfaces in the resource api because I didnt want to create a new 
package, but if its Ok to create a new package, what should it be called ?

A new package will be better also  since I can already think of some use cases 
where URIProvder.Scope would need to be extended to allow CRUD.


I think it should be under resource, since it's always directly related to a 
resource and could be used by any resource provider, not just JCR or the 
current Oak implementation of JCR. 


org.apache.sling.api.resource.convert 
org.apache.sling.api.resource.providers
org.apache.sling.api.resource.external
org.apache.sling.api.resource.ext
org.apache.sling.api.resource.extension

Whatever the package name is, tt would need to have the Interfaces in this 
commit 
https://github.com/apache/sling-org-apache-sling-api/commit/a228b98f3a58409507b98e0d5b2d8e52b755d94f


> Support redirects to URLs provided by the underlying datastore.
> ---
>
> Key: SLING-7140
> URL: https://issues.apache.org/jira/browse/SLING-7140
> Project: Sling
>  Issue Type: Bug
>  Components: Servlets
>Affects Versions: Servlets Get 2.1.26, JCR Resource 3.0.4
>Reporter: Ian Boston
>Assignee: Ian Boston
> Fix For: Servlets Get 2.1.28, JCR Resource 3.0.6, API 2.16.4, 
> Resource Resolver 1.5.32
>
>
> Incorporate changes to allow OAK-6575 to work in Sling, 
> Patch available at 
> https://github.com/apache/sling/compare/trunk...ieb:OAK-6575-3-2
> Cant me applied until OAK-6575 is released in a version suitable for use in 
> Sling.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)