date:20161114


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

Carsten Ziegeler updated SLING-6174:

Attachment: jcresource-patch.txt

> Use Jackrabbit/Oak globbing support
> ---
>
> Key: SLING-6174
> URL: https://issues.apache.org/jira/browse/SLING-6174
> Project: Sling
>  Issue Type: Improvement
>  Components: JCR
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: JCR Resource 2.9.0
>
> Attachments: jcresource-patch.txt
>
>
> We recently switched back to use a jcr listener (SLING-6138) unfortunately, 
> Jackrabbit does not support glob patterns atm.
> Once JCR-4044 is fixed, we should use it.
> If the JR api will not support glob support, we have to come up with a 
> different solution as today, either
> - switch back to oak observer
> - or only register a single jcr listener on root and do the filtering 
> internally



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-6174) Use Jackrabbit/Oak globbing support


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

Carsten Ziegeler updated SLING-6174:

Attachment: (was: jcresource-patch.txt)

> Use Jackrabbit/Oak globbing support
> ---
>
> Key: SLING-6174
> URL: https://issues.apache.org/jira/browse/SLING-6174
> Project: Sling
>  Issue Type: Improvement
>  Components: JCR
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: JCR Resource 2.9.0
>
>
> We recently switched back to use a jcr listener (SLING-6138) unfortunately, 
> Jackrabbit does not support glob patterns atm.
> Once JCR-4044 is fixed, we should use it.
> If the JR api will not support glob support, we have to come up with a 
> different solution as today, either
> - switch back to oak observer
> - or only register a single jcr listener on root and do the filtering 
> internally



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

java.lang.AbstractMethodError: org.apache.sling.jcr.base.AbstractSlingRepositoryManager.getLoginAdminWhitelist() - trunk build does not work // was: mountByFS does not work

2016-11-14 Thread Sandro Boehme


Am 14.11.16 um 23:02 schrieb Robert Munteanu:

On Mon, 2016-11-14 at 21:50 +0100, Sandro Boehme wrote:

Hi Robert,


It took me a while to get the trunk to build. I had to disable
the
Rat
checks and update the dependency to org.apache.sling.jcr.base
version
2.4.3-SNAPSHOT in org.apache.sling.jcr.oak.server.
Why isn't there a build job anymore for trunk? Should I build
Sling
differently than described at the website [1]?


The context as is at [2]. Basically, the big 'trunk' jobs were too
slow
and flaky. Now we have many small jobs, with none of them slow and
a
couple of them flaky :-)

But the reactor build should work nonetheless.

I currently can't build it due to repository.apache.org timeouts,
can
you post any errors that you get?

Thanks,

Robert


[2]: https://cwiki.apache.org/confluence/display/SLING/Sling+Jenkin
s+Se
tup


The dependency to oasling.jcr.base 2.4.x has been changed by Julian
in
the meantime to prepare for the oak.server-1.1.2 release.
So I could build the trunk a few minutes ago.
But the server doesn't seem to start completely. When accessing
http://localhost:8080 I get an HTTP 503 saying
"Problem accessing /. Reason:
AuthenticationSupport service missing. Cannot authenticate request."
138 bundles are available and active.

The error log shows me this error:
14.11.2016 21:30:58.119 *ERROR* [OsgiInstallerImpl]
org.apache.sling.jcr.oak.server.internal.OakSlingRepositoryManager
start: Uncaught Throwable trying to access Repository, calling
stopRepository()
java.lang.AbstractMethodError:
org.apache.sling.jcr.base.AbstractSlingRepositoryManager.getLoginAdmi
nWhitelist()Lorg/apache/sling/jcr/base/LoginAdminWhitelist;


(snip)

Seems like a mismatch between bundle versions. I think that this
class/config was moved to oak-server recently. Just to be sure, can you
navigate to launchpad/builder and:

- remove any existing 'sling' directory
- run `mvn clean verify`
- run `java -jar target/org.apache.sling.launchpad-9-SNAPSHOT.jar`

Robert



I have created new home folders with the -c option already. I followed 
your instructions anyways but I get the same error.
BTW: org.apache.sling.launchpad.SmokeIT fails with the same error 
(...AuthenticationSupport service missing...).


I agree that it might be a config error. The following bundles are 
active as seen in /system/console/bundles:

- org.apache.sling.auth.core 1.3.20
- org.apache.sling.jcr.oak.server 1.1.1.SNAPSHOT
- org.apache.sling.jcr.base 2.4.1.SNAPSHOT
I also switched to org.apache.sling.jcr.oak.server 1.1.3.SNAPSHOT by 
changing /launchpad/builder/src/main/provisioning/oak.txt. But the error 
is still there.


Best,

Sandro

Re: trunk build does not work // was: mountByFS does not work

On Mon, 2016-11-14 at 21:50 +0100, Sandro Boehme wrote:
> Hi Robert,
> 
> > > It took me a while to get the trunk to build. I had to disable
> > > the
> > > Rat
> > > checks and update the dependency to org.apache.sling.jcr.base
> > > version
> > > 2.4.3-SNAPSHOT in org.apache.sling.jcr.oak.server.
> > > Why isn't there a build job anymore for trunk? Should I build
> > > Sling
> > > differently than described at the website [1]?
> > 
> > The context as is at [2]. Basically, the big 'trunk' jobs were too
> > slow
> > and flaky. Now we have many small jobs, with none of them slow and
> > a
> > couple of them flaky :-)
> > 
> > But the reactor build should work nonetheless.
> > 
> > I currently can't build it due to repository.apache.org timeouts,
> > can
> > you post any errors that you get?
> > 
> > Thanks,
> > 
> > Robert
> > 
> > 
> > [2]: https://cwiki.apache.org/confluence/display/SLING/Sling+Jenkin
> > s+Se
> > tup
> 
> The dependency to oasling.jcr.base 2.4.x has been changed by Julian
> in 
> the meantime to prepare for the oak.server-1.1.2 release.
> So I could build the trunk a few minutes ago.
> But the server doesn't seem to start completely. When accessing 
> http://localhost:8080 I get an HTTP 503 saying
> "Problem accessing /. Reason:
> AuthenticationSupport service missing. Cannot authenticate request."
> 138 bundles are available and active.
> 
> The error log shows me this error:
> 14.11.2016 21:30:58.119 *ERROR* [OsgiInstallerImpl] 
> org.apache.sling.jcr.oak.server.internal.OakSlingRepositoryManager 
> start: Uncaught Throwable trying to access Repository, calling 
> stopRepository()
> java.lang.AbstractMethodError: 
> org.apache.sling.jcr.base.AbstractSlingRepositoryManager.getLoginAdmi
> nWhitelist()Lorg/apache/sling/jcr/base/LoginAdminWhitelist;
> 
(snip)

Seems like a mismatch between bundle versions. I think that this
class/config was moved to oak-server recently. Just to be sure, can you
navigate to launchpad/builder and:

- remove any existing 'sling' directory
- run `mvn clean verify`
- run `java -jar target/org.apache.sling.launchpad-9-SNAPSHOT.jar`

Robert

trunk build does not work // was: mountByFS does not work

2016-11-14 Thread Sandro Boehme

Hi Robert,

It took me a while to get the trunk to build. I had to disable the
Rat
checks and update the dependency to org.apache.sling.jcr.base
version
2.4.3-SNAPSHOT in org.apache.sling.jcr.oak.server.
Why isn't there a build job anymore for trunk? Should I build Sling
differently than described at the website [1]?

The context as is at [2]. Basically, the big 'trunk' jobs were too slow
and flaky. Now we have many small jobs, with none of them slow and a
couple of them flaky :-)

But the reactor build should work nonetheless.

I currently can't build it due to repository.apache.org timeouts, can
you post any errors that you get?

Thanks,

Robert

[2]: https://cwiki.apache.org/confluence/display/SLING/Sling+Jenkins+Se
tup

The dependency to oasling.jcr.base 2.4.x has been changed by Julian in
the meantime to prepare for the oak.server-1.1.2 release.

So I could build the trunk a few minutes ago.
But the server doesn't seem to start completely. When accessing
http://localhost:8080 I get an HTTP 503 saying

"Problem accessing /. Reason:
AuthenticationSupport service missing. Cannot authenticate request."
138 bundles are available and active.

The error log shows me this error:
14.11.2016 21:30:58.119 *ERROR* [OsgiInstallerImpl]
org.apache.sling.jcr.oak.server.internal.OakSlingRepositoryManager
start: Uncaught Throwable trying to access Repository, calling
stopRepository()
java.lang.AbstractMethodError:
org.apache.sling.jcr.base.AbstractSlingRepositoryManager.getLoginAdminWhitelist()Lorg/apache/sling/jcr/base/LoginAdminWhitelist;
at
org.apache.sling.jcr.base.AbstractSlingRepository2.loginAdministrative(AbstractSlingRepository2.java:373)
at
org.apache.sling.jcr.base.internal.loader.Loader.getSession(Loader.java:326)
at
org.apache.sling.jcr.base.internal.loader.Loader.registerNamespaces(Loader.java:213)
at
org.apache.sling.jcr.base.internal.loader.Loader.registerBundleInternal(Loader.java:225)
at
org.apache.sling.jcr.base.internal.loader.Loader.registerBundle(Loader.java:158)

at
org.apache.sling.jcr.base.internal.loader.Loader.(Loader.java:75)
at
org.apache.sling.jcr.base.AbstractSlingRepositoryManager.start(AbstractSlingRepositoryManager.java:371)

...

Any advice would be much appreciated!

Best,
Sandro

Re: [VOTE] Release Apache Sling Commons ClassLoader 1.3.6

2016-11-14 Thread Daniel Klco

+1

On Mon, Nov 14, 2016 at 12:03 PM, Radu Cotescu  wrote:

> +1
>

Re: [VOTE] Release Apache Sling Authentication Service 1.3.22

2016-11-14 Thread Daniel Klco

+1

On Mon, Nov 14, 2016 at 4:37 AM, Robert Munteanu  wrote:

> On Fri, 2016-11-11 at 15:12 +, Antonio Sanso wrote:
> > Please vote to approve this release:
>
> +1
>
> Robert

Re: [VOTE] Release Apache Sling Commons ClassLoader 1.3.6

2016-11-14 Thread Radu Cotescu

+1

Re: Suggestion: use redirectTestOutputToFile for maven-failsafe-plugin

Thanks Robert, that's great! Having a direct correlation between test
and stdout would make analysis easier and it would unclutter the
build's stdout.

Regards
Julian

On Mon, Nov 14, 2016 at 5:03 PM, Robert Munteanu  wrote:
> Hi Julian,
>
> On Mon, 2016-11-14 at 16:19 +0100, Julian Sedding wrote:
>> Hi all
>>
>> I find using "redirectTestOutputToFile" for the maven-failsafe-plugin
>> makes it easier to see which IT is failing and also helps by
>> providing
>> the logs per IT.
>>
>> What are your opinions on this? Does anyone know if it makes it
>> harder
>> to analyze failures on Jenkins (or can the *-output.txt files be
>> inspected via the web UI?).
>
> I have not tried to see what happens on Jenkins, but it seems that [1]
> provides a solution for that, in case we decide it's neede.
>
>>
>> If there is agreement, I would like to set this option in the parent
>> pom.
>>
>> Regards
>> Julian
>
>
> Robert
>
> [1]: https://wiki.jenkins-ci.org/display/JENKINS/JUnit+Attachments+Plug
> in

Re: Suggestion: use redirectTestOutputToFile for maven-failsafe-plugin

Hi Julian,

On Mon, 2016-11-14 at 16:19 +0100, Julian Sedding wrote:
> Hi all
> 
> I find using "redirectTestOutputToFile" for the maven-failsafe-plugin
> makes it easier to see which IT is failing and also helps by
> providing
> the logs per IT.
> 
> What are your opinions on this? Does anyone know if it makes it
> harder
> to analyze failures on Jenkins (or can the *-output.txt files be
> inspected via the web UI?).

I have not tried to see what happens on Jenkins, but it seems that [1]
provides a solution for that, in case we decide it's neede.

> 
> If there is agreement, I would like to set this option in the parent
> pom.
> 
> Regards
> Julian


Robert

[1]: https://wiki.jenkins-ci.org/display/JENKINS/JUnit+Attachments+Plug
in

Re: [VOTE] Release Apache Sling JCR Resource 2.8.2 and Apache Sling JCR Oak Repository Server 1.1.2

On Mon, 2016-11-14 at 16:43 +0100, Julian Sedding wrote:
> Please vote to approve this release:

+1

Robert

signature.asc
Description: This is a digitally signed message part

Re: [VOTE] Release Apache Sling JCR Resource 2.8.2 and Apache Sling JCR Oak Repository Server 1.1.2

2016-11-14 Thread Carsten Ziegeler

+1


 

-- 
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org

Re: Build failed in Jenkins: sling-bundles-jcr-oak-server-1.8 #87

This failure is expected, as o.a.s.jcr.oak.server is currently under
vote together with o.a.s.jcr.resource 2.8.2.

Regards
Julian

On Mon, Nov 14, 2016 at 4:50 PM, Apache Jenkins Server
 wrote:
> See 
> 
>
> Changes:
>
> [jsedding] [maven-release-plugin] prepare for next development iteration
>
> [jsedding] [maven-release-plugin] prepare release 
> org.apache.sling.jcr.oak.server-1.1.2
>
> --
> Started by an SCM change
> [EnvInject] - Loading node environment variables.
> Building remotely on H17 (ubuntu) in workspace 
> 
> Updating https://svn.apache.org/repos/asf/sling/trunk/bundles/jcr/oak-server 
> at revision '2016-11-14T15:49:20.874 +'
> U pom.xml
> At revision 1769655
>
> Parsing POMs
> Established TCP socket on 36554
> maven32-agent.jar already up to date
> maven32-interceptor.jar already up to date
> maven3-interceptor-commons.jar already up to date
> [sling-bundles-jcr-oak-server-1.8] $ 
> /home/jenkins/tools/java/latest1.8/bin/java -Xmx2g -Xms256m 
> -XX:MaxPermSize=512m -cp 
> /home/jenkins/jenkins-slave/maven32-agent.jar:/home/jenkins/tools/maven/apache-maven-3.3.9/boot/plexus-classworlds-2.5.2.jar:/home/jenkins/tools/maven/apache-maven-3.3.9/conf/logging
>  jenkins.maven3.agent.Maven32Main 
> /home/jenkins/tools/maven/apache-maven-3.3.9 
> /home/jenkins/jenkins-slave/slave.jar 
> /home/jenkins/jenkins-slave/maven32-interceptor.jar 
> /home/jenkins/jenkins-slave/maven3-interceptor-commons.jar 36554
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
> support was removed in 8.0
> <===[JENKINS REMOTING CAPACITY]===>   channel started
> Executing Maven:  -B -f 
>  
> -Dmaven.repo.local=/home/jenkins/jenkins-slave/maven-repositories/0 -U clean 
> verify
> [INFO] Scanning for projects...
> [INFO]
> [INFO] 
> 
> [INFO] Building Apache Sling JCR Oak Repository Server 1.1.3-SNAPSHOT
> [INFO] 
> 
> [INFO] Downloading: 
> https://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.jcr.base/2.4.2/org.apache.sling.jcr.base-2.4.2.pom
> [INFO] Downloaded: 
> https://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.jcr.base/2.4.2/org.apache.sling.jcr.base-2.4.2.pom
>  (6 KB at 15.7 KB/sec)
> [INFO] Downloading: 
> https://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.testing.paxexam/0.0.2/org.apache.sling.testing.paxexam-0.0.2.pom
> [INFO] Downloaded: 
> https://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.testing.paxexam/0.0.2/org.apache.sling.testing.paxexam-0.0.2.pom
>  (6 KB at 31.2 KB/sec)
> [INFO] Downloading: 
> https://repo.maven.apache.org/maven2/org/osgi/org.osgi.service.event/1.3.1/org.osgi.service.event-1.3.1.pom
> [INFO] Downloaded: 
> https://repo.maven.apache.org/maven2/org/osgi/org.osgi.service.event/1.3.1/org.osgi.service.event-1.3.1.pom
>  (2 KB at 70.1 KB/sec)
> [INFO] Downloading: 
> https://repo.maven.apache.org/maven2/org/osgi/org.osgi.service.cm/1.5.0/org.osgi.service.cm-1.5.0.pom
> [INFO] Downloaded: 
> https://repo.maven.apache.org/maven2/org/osgi/org.osgi.service.cm/1.5.0/org.osgi.service.cm-1.5.0.pom
>  (2 KB at 69.7 KB/sec)
> [INFO] Downloading: 
> https://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.jcr.resource/2.8.2/org.apache.sling.jcr.resource-2.8.2.pom
> [WARNING] The POM for 
> org.apache.sling:org.apache.sling.jcr.resource:jar:2.8.2 is missing, no 
> dependency information available
> [INFO] Downloading: 
> https://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.jcr.base/2.4.2/org.apache.sling.jcr.base-2.4.2.jar
> [INFO] Downloading: 
> https://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.testing.paxexam/0.0.2/org.apache.sling.testing.paxexam-0.0.2.jar
> [INFO] Downloading: 
> https://repo.maven.apache.org/maven2/org/osgi/org.osgi.service.event/1.3.1/org.osgi.service.event-1.3.1.jar
> [INFO] Downloading: 
> https://repo.maven.apache.org/maven2/org/osgi/org.osgi.service.cm/1.5.0/org.osgi.service.cm-1.5.0.jar
> [INFO] Downloading: 
> https://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.jcr.resource/2.8.2/org.apache.sling.jcr.resource-2.8.2.jar
> [INFO] Downloaded: 
> https://repo.maven.apache.org/maven2/org/osgi/org.osgi.service.cm/1.5.0/org.osgi.service.cm-1.5.0.jar
>  (46 KB at 907.6 KB/sec)
> [INFO] Downloaded: 
> https://repo.maven.apache.org/maven2/org/osgi/org.osgi.service.event/1.3.1/org.osgi.service.event-1.3.1.jar
>  (36 KB at 666.1 KB/sec)
> [INFO] Downloaded: 
> https://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.jcr.base/2.4.2/org.apache.sling.jcr.base-2.4.2.jar
>  (43 KB at 764.1 KB

[VOTE] Release Apache Sling JCR Resource 2.8.2 and Apache Sling JCR Oak Repository Server 1.1.2

Hi,

We solved 8 issues in the JCR Resource 2.8.2 release:
https://issues.apache.org/jira/browse/SLING/fixforversion/12336744

We solved 4 issues in the JCR Oak Repository Server 1.1.2 release:
https://issues.apache.org/jira/browse/SLING/fixforversion/12338111

Note: The build of Oak Server 1.1.2 depends on JCR Resource 2.8.2 for testing.

Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-1576/

You can use this UNIX script to download the release and verify the signatures:
http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh

Usage:
sh check_staged_release.sh 1576 /tmp/sling-staging

Please vote to approve this release:

  [ ] +1 Approve the release
  [ ]  0 Don't care
  [ ] -1 Don't release, because ...

This majority vote is open for at least 72 hours.

Regards
Julian

[jira] [Updated] (SLING-6130) Restrict access for principal everyone and move configuration to repoinit

2016-11-14 Thread Julian Sedding (JIRA)


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

Julian Sedding updated SLING-6130:
--
Fix Version/s: (was: JCR Oak Server 1.1.2)
   JCR Oak Server 1.1.4

> Restrict access for principal everyone and move configuration to repoinit
> -
>
> Key: SLING-6130
> URL: https://issues.apache.org/jira/browse/SLING-6130
> Project: Sling
>  Issue Type: Improvement
>  Components: JCR, Oak
>Affects Versions: JCR Oak Server 1.1.0
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
>  Labels: security
> Fix For: JCR Oak Server 1.1.4
>
> Attachments: error.log
>
>
> Currently {{everyone}} can {{read}} from {{/}} (configured in 
> {{OakSlingRepositoryManager}}).
> Access for {{everyone}} should be restricted:
> * {{read}} should be restricted to {{/content}}
> * configuration of principals and ACLs should be done with _repoinit_
> # -Change path from {{/}} to {{/content}} in {{OakSlingRepositoryManager}}- 
> (/) (-[r1764259|https://svn.apache.org/r1764259]-)
> # Fix modules (samples) relying on _unrestricted_ {{read}} access
> # Move configuration of ACLs to _repoinit_ (/)
> discussion on 
> [dev@|https://lists.apache.org/thread.html/36908ed62ac93c63cad594a897f8abceb93f08da5bcea30dbce98e58@%3Cdev.sling.apache.org%3E]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Suggestion: use redirectTestOutputToFile for maven-failsafe-plugin

Hi all

I find using "redirectTestOutputToFile" for the maven-failsafe-plugin
makes it easier to see which IT is failing and also helps by providing
the logs per IT.

What are your opinions on this? Does anyone know if it makes it harder
to analyze failures on Jenkins (or can the *-output.txt files be
inspected via the web UI?).

If there is agreement, I would like to set this option in the parent pom.

Regards
Julian

Re: Release of org.apache.sling.testing.paxexam today

Hi Olli

Yes, it's the new API that's blocking. I'll follow your suggestion to
downgrade and replace with setVersion(). Thanks.

Regards
Julian

On Mon, Nov 14, 2016 at 3:50 PM, Oliver Lietz  wrote:
> On Monday 14 November 2016 15:02:32 Julian Sedding wrote:
>> Hi all
>>
>> If no one beats me to it, I will release
>> "org.apache.sling.testing.paxexam" today. It currently blocks the
>> release of "org.apache.sling.jcr.oak.server".
>>
>> Objections anyone?
>
> hi Julian,
>
> what is blocking? setVersionFromProject() can be replaced by setVersion() and
> fixed versions (downgrading to 0.0.2) as it is done for Felix HTTP to be
> compatible with Java 7.
>
> I have some updates for the module but they can be applied after Oak Server is
> released.
>
> Regards,
> O.
>
>> Regards
>> Julian
>

Re: Release of org.apache.sling.testing.paxexam today

2016-11-14 Thread Oliver Lietz

On Monday 14 November 2016 15:02:32 Julian Sedding wrote:
> Hi all
> 
> If no one beats me to it, I will release
> "org.apache.sling.testing.paxexam" today. It currently blocks the
> release of "org.apache.sling.jcr.oak.server".
> 
> Objections anyone?

hi Julian,

what is blocking? setVersionFromProject() can be replaced by setVersion() and 
fixed versions (downgrading to 0.0.2) as it is done for Felix HTTP to be 
compatible with Java 7.

I have some updates for the module but they can be applied after Oak Server is 
released.

Regards,
O.

> Regards
> Julian

[jira] [Updated] (SLING-5983) Remove deprecated jcr resource API


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

Carsten Ziegeler updated SLING-5983:

Assignee: (was: Carsten Ziegeler)

> Remove deprecated jcr resource API
> --
>
> Key: SLING-5983
> URL: https://issues.apache.org/jira/browse/SLING-5983
> Project: Sling
>  Issue Type: Improvement
>  Components: JCR
>Reporter: Carsten Ziegeler
> Fix For: JCR Resource 2.9.2
>
>
> The jcr resource API has been deprecated for some time and not used anymore 
> in our codebase, we should now remove it from the jcr resource bundle
> We should also remove the deprecated PathMapper



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-6163) Improve observation of files in JCR


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

Carsten Ziegeler updated SLING-6163:

Fix Version/s: (was: JCR Resource 2.9.2)
   JCR Resource 2.9.0

> Improve observation of files in JCR
> ---
>
> Key: SLING-6163
> URL: https://issues.apache.org/jira/browse/SLING-6163
> Project: Sling
>  Issue Type: Improvement
>  Components: JCR
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: JCR Resource 2.9.0
>
>
> Currently, if a jcr:content node is modified, and an observation event is 
> sent out, the jcr listener reads the parent node to find out if this 
> jcr:content is a sub node of a file. If so, it reports a change on the file 
> node.
> This is required for all listeners interested in changes in files, as they 
> usually listen for a file node change, but not for the sub node /jcr:content 
> - which doesn't exist with other resource providers anyway
> The problem is that this read is done for every change of a jcr:content node, 
> regardless whether this is a file. And if several props change on such a 
> node, it is read over and over again



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-6174) Use Jackrabbit/Oak globbing support


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

Carsten Ziegeler updated SLING-6174:

Fix Version/s: (was: JCR Resource 2.9.2)
   JCR Resource 2.9.0

> Use Jackrabbit/Oak globbing support
> ---
>
> Key: SLING-6174
> URL: https://issues.apache.org/jira/browse/SLING-6174
> Project: Sling
>  Issue Type: Improvement
>  Components: JCR
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: JCR Resource 2.9.0
>
> Attachments: jcresource-patch.txt
>
>
> We recently switched back to use a jcr listener (SLING-6138) unfortunately, 
> Jackrabbit does not support glob patterns atm.
> Once JCR-4044 is fixed, we should use it.
> If the JR api will not support glob support, we have to come up with a 
> different solution as today, either
> - switch back to oak observer
> - or only register a single jcr listener on root and do the filtering 
> internally



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Release of org.apache.sling.testing.paxexam today

Hi all

If no one beats me to it, I will release
"org.apache.sling.testing.paxexam" today. It currently blocks the
release of "org.apache.sling.jcr.oak.server".

Objections anyone?

Regards
Julian

Re: [VOTE] Release Apache Sling Resource Resolver 1.5.4

On Mon, 2016-11-14 at 14:03 +0100, Carsten Ziegeler wrote:
> Please vote to approve this release:

+1

Robert

Re: [VOTE] Release Apache Sling Resource Resolver 1.5.4

+1 (non binding)

All checks ok.

Regards
Julian

On Mon, Nov 14, 2016 at 2:04 PM, Carsten Ziegeler  wrote:
> +1
>
>
>
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@apache.org
>

[jira] [Updated] (SLING-6174) Use Jackrabbit/Oak globbing support


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

Carsten Ziegeler updated SLING-6174:

Attachment: jcresource-patch.txt

> Use Jackrabbit/Oak globbing support
> ---
>
> Key: SLING-6174
> URL: https://issues.apache.org/jira/browse/SLING-6174
> Project: Sling
>  Issue Type: Improvement
>  Components: JCR
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: JCR Resource 2.9.2
>
> Attachments: jcresource-patch.txt
>
>
> We recently switched back to use a jcr listener (SLING-6138) unfortunately, 
> Jackrabbit does not support glob patterns atm.
> Once JCR-4044 is fixed, we should use it.
> If the JR api will not support glob support, we have to come up with a 
> different solution as today, either
> - switch back to oak observer
> - or only register a single jcr listener on root and do the filtering 
> internally



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-6174) Use Jackrabbit/Oak globbing support


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

Carsten Ziegeler updated SLING-6174:

Attachment: (was: jcresource-patch.txt)

> Use Jackrabbit/Oak globbing support
> ---
>
> Key: SLING-6174
> URL: https://issues.apache.org/jira/browse/SLING-6174
> Project: Sling
>  Issue Type: Improvement
>  Components: JCR
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: JCR Resource 2.9.2
>
> Attachments: jcresource-patch.txt
>
>
> We recently switched back to use a jcr listener (SLING-6138) unfortunately, 
> Jackrabbit does not support glob patterns atm.
> Once JCR-4044 is fixed, we should use it.
> If the JR api will not support glob support, we have to come up with a 
> different solution as today, either
> - switch back to oak observer
> - or only register a single jcr listener on root and do the filtering 
> internally



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [VOTE] Release Apache Sling Resource Resolver 1.5.4

2016-11-14 Thread Carsten Ziegeler

+1

 

-- 
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org

[VOTE] Release Apache Sling Resource Resolver 1.5.4

2016-11-14 Thread Carsten Ziegeler

Hi,

We solved 1 issues in this release:
https://issues.apache.org/jira/browse/SLING-6283

Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-1575/

You can use this UNIX script to download the release and verify the
signatures:
http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh

Usage:
sh check_staged_release.sh 1575 /tmp/sling-staging

Please vote to approve this release:

  [ ] +1 Approve the release
  [ ]  0 Don't care
  [ ] -1 Don't release, because ...

This majority vote is open for at least 72 hours.

Regards
Carsten
-- 
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org

Re: mountByFS does not work

Hi Sandro,

On Sun, 2016-11-13 at 23:49 +0100, Sandro Boehme wrote:
> > > > The problem is that we need to update the fsresource bundle to
> > > > use the
> > > > resource resolver observation api. I'll try to take care of it.
> > > 
> > > Ah. Thanks a lot!
> > > 
> > 
> > I've updated the fsresource bundle (SLING-6279) but didn't test it
> > so far :)
> > So if you want to give it a try...
> 
> Thanks for updating Carsten!
> 
> It took me a while to get the trunk to build. I had to disable the
> Rat 
> checks and update the dependency to org.apache.sling.jcr.base
> version 
> 2.4.3-SNAPSHOT in org.apache.sling.jcr.oak.server.
> Why isn't there a build job anymore for trunk? Should I build Sling 
> differently than described at the website [1]?

The context as is at [2]. Basically, the big 'trunk' jobs were too slow
and flaky. Now we have many small jobs, with none of them slow and a
couple of them flaky :-)

But the reactor build should work nonetheless.

I currently can't build it due to repository.apache.org timeouts, can
you post any errors that you get?

Thanks,

Robert

> 
> Now when I access http://localhost:8080/ I get the error 
> "AuthenticationSupport service missing. Cannot authenticate
> request.". I 
> will have a look at it again at an other day and may ask for support
> later.
> But of course if you have a hint already I would be happy about any
> advice.
> 
> [1] - 
> http://sling.apache.org/documentation/development/getting-and-buildin
> g-sling.html
> 
> Best,
> 
> Sandro


[2]: https://cwiki.apache.org/confluence/display/SLING/Sling+Jenkins+Se
tup

[jira] [Updated] (SLING-5235) Remove loginAdministrative() usage from org.apache.sling.resourceresolver


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

Carsten Ziegeler updated SLING-5235:

Fix Version/s: (was: Resource Resolver 1.5.4)
   Resource Resolver 1.5.6

> Remove loginAdministrative() usage from org.apache.sling.resourceresolver
> -
>
> Key: SLING-5235
> URL: https://issues.apache.org/jira/browse/SLING-5235
> Project: Sling
>  Issue Type: Improvement
>  Components: ResourceResolver
>Reporter: Antonio Sanso
> Fix For: Resource Resolver 1.5.6
>
>
> counted 6 occurrences



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-6284) PreparePackageMojo.testSubsystemBaseGeneration often fails on Jenkins


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

Robert Munteanu commented on SLING-6284:


Made the mojo fail fast if a directory could not be created in 
https://svn.apache.org/r1769613

> PreparePackageMojo.testSubsystemBaseGeneration often fails on Jenkins
> -
>
> Key: SLING-6284
> URL: https://issues.apache.org/jira/browse/SLING-6284
> Project: Sling
>  Issue Type: Bug
>  Components: Maven Plugins and Archetypes
>Affects Versions: Slingstart Maven Plugin 1.6.0
>Reporter: Robert Munteanu
>  Labels: sling-IT
> Fix For: Slingstart Maven Plugin 1.7.0
>
>
> The test seems to fail every other run. The error is
> {noformat}org.apache.maven.plugin.MojoExecutionException: Problem creating 
> subsystem .esa file 
> /tmp/PreparePackageMojoTest1894864848680720292/slingstart-tmp/test1.subsystem-base
>   at 
> sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
>   at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
>   at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
>   at 
> sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214)
>   at java.nio.file.Files.newByteChannel(Files.java:317)
>   at java.nio.file.Files.newByteChannel(Files.java:363)
>   at 
> java.nio.file.spi.FileSystemProvider.newInputStream(FileSystemProvider.java:380)
>   at java.nio.file.Files.newInputStream(Files.java:108)
>   at java.nio.file.Files.copy(Files.java:2895)
>   at 
> org.apache.sling.maven.slingstart.PreparePackageMojo.createSubsystemBaseFile(PreparePackageMojo.java:351)
>   at 
> org.apache.sling.maven.slingstart.PreparePackageMojo.buildSubsystemBase(PreparePackageMojo.java:244)
>   at 
> org.apache.sling.maven.slingstart.PreparePackageMojo.buildContentsMap(PreparePackageMojo.java:224)
>   at 
> org.apache.sling.maven.slingstart.PreparePackageMojo.prepareGlobal(PreparePackageMojo.java:130)
>   at 
> org.apache.sling.maven.slingstart.PreparePackageMojo.execute(PreparePackageMojo.java:120)
>   at 
> org.apache.sling.maven.slingstart.PreparePackageMojoTest.testSubsystemBaseGeneration(PreparePackageMojoTest.java:176){noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SLING-6284) PreparePackageMojo.testSubsystemBaseGeneration often fails on Jenkins

Robert Munteanu created SLING-6284:
--

 Summary: PreparePackageMojo.testSubsystemBaseGeneration often 
fails on Jenkins
 Key: SLING-6284
 URL: https://issues.apache.org/jira/browse/SLING-6284
 Project: Sling
  Issue Type: Bug
  Components: Maven Plugins and Archetypes
Affects Versions: Slingstart Maven Plugin 1.6.0
Reporter: Robert Munteanu
 Fix For: Slingstart Maven Plugin 1.7.0


The test seems to fail every other run. The error is

{noformat}org.apache.maven.plugin.MojoExecutionException: Problem creating 
subsystem .esa file 
/tmp/PreparePackageMojoTest1894864848680720292/slingstart-tmp/test1.subsystem-base
at 
sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
at 
sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214)
at java.nio.file.Files.newByteChannel(Files.java:317)
at java.nio.file.Files.newByteChannel(Files.java:363)
at 
java.nio.file.spi.FileSystemProvider.newInputStream(FileSystemProvider.java:380)
at java.nio.file.Files.newInputStream(Files.java:108)
at java.nio.file.Files.copy(Files.java:2895)
at 
org.apache.sling.maven.slingstart.PreparePackageMojo.createSubsystemBaseFile(PreparePackageMojo.java:351)
at 
org.apache.sling.maven.slingstart.PreparePackageMojo.buildSubsystemBase(PreparePackageMojo.java:244)
at 
org.apache.sling.maven.slingstart.PreparePackageMojo.buildContentsMap(PreparePackageMojo.java:224)
at 
org.apache.sling.maven.slingstart.PreparePackageMojo.prepareGlobal(PreparePackageMojo.java:130)
at 
org.apache.sling.maven.slingstart.PreparePackageMojo.execute(PreparePackageMojo.java:120)
at 
org.apache.sling.maven.slingstart.PreparePackageMojoTest.testSubsystemBaseGeneration(PreparePackageMojoTest.java:176){noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-5229) Remove getAdministrativeResourceResolver() and loginAdministrative() usage from JCR components

2016-11-14 Thread Julian Sedding (JIRA)


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

Julian Sedding updated SLING-5229:
--
Fix Version/s: (was: JCR Base 2.4.2)
   JCR Base 2.4.4

> Remove getAdministrativeResourceResolver() and loginAdministrative() usage 
> from JCR components
> --
>
> Key: SLING-5229
> URL: https://issues.apache.org/jira/browse/SLING-5229
> Project: Sling
>  Issue Type: Improvement
>  Components: JCR
>Reporter: Antonio Sanso
> Fix For: JCR Resource 2.9.2, JCR Installer 3.1.20, JCR 
> ContentLoader 2.2.0, JCR Compiler 2.1.2, JCR Davex 1.3.6, JCR Base 2.4.4
>
>
> * {{org.apache.sling.jcr.compiler}} : 1
> * {{org.apache.sling.installer.provider.jcr}}: 4
> * {{org.apache.sling.jcr.base}}: 2
> * {{org.apache.sling.jcr.contentloader}}: 2
> * {{org.apache.sling.jcr.davex}}: 1
> * {{org.apache.sling.jcr.resource}}: 5
> total of 15 occurrences



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[RESULT] [VOTE] Release Apache Sling JCR Base 2.4.2

Hi

The vote has passed with the following result:

+1 (binding): Stefan Seifert, Carsten Ziegeler, Oliver Lietz
+1 (non binding): Julian Sedding

Thanks for voting.

I will promote the artifacts to the central Maven repository and
update the news page.

@any PMC member: please copy this release to the Sling dist directory.

Regards
Julian

[jira] [Resolved] (SLING-6283) Exclusion of observations with listeners using patterns is too aggressive


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

Carsten Ziegeler resolved SLING-6283.
-
Resolution: Fixed

> Exclusion of observations with listeners using patterns is too aggressive
> -
>
> Key: SLING-6283
> URL: https://issues.apache.org/jira/browse/SLING-6283
> Project: Sling
>  Issue Type: Bug
>  Components: ResourceResolver
>Affects Versions: Resource Resolver 1.5.2
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: Resource Resolver 1.5.4
>
>
> If for example a resource change listeners registers for 
> {noformat}
> /libs/**/*.jsp
> {noformat}
> and a resource provider is registered at /libs/.servlet
> Then the above listener is excluded. Path.matches() is defined the way that 
> it returns true in this case. The API of Path is fine, however it is not 
> usable for the resource resolver implementation



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SLING-6283) Exclusion of observations with listeners using patterns is too aggressive

Carsten Ziegeler created SLING-6283:
---

 Summary: Exclusion of observations with listeners using patterns 
is too aggressive
 Key: SLING-6283
 URL: https://issues.apache.org/jira/browse/SLING-6283
 Project: Sling
  Issue Type: Bug
  Components: ResourceResolver
Affects Versions: Resource Resolver 1.5.2
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
 Fix For: Resource Resolver 1.5.4


If for example a resource change listeners registers for 
{noformat}
/libs/**/*.jsp
{noformat}

and a resource provider is registered at /libs/.servlet

Then the above listener is excluded. Path.matches() is defined the way that it 
returns true in this case. The API of Path is fine, however it is not usable 
for the resource resolver implementation




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-6163) Improve observation of files in JCR


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

Carsten Ziegeler updated SLING-6163:

Fix Version/s: (was: JCR Resource 2.9.0)
   JCR Resource 2.9.2

> Improve observation of files in JCR
> ---
>
> Key: SLING-6163
> URL: https://issues.apache.org/jira/browse/SLING-6163
> Project: Sling
>  Issue Type: Improvement
>  Components: JCR
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: JCR Resource 2.9.2
>
>
> Currently, if a jcr:content node is modified, and an observation event is 
> sent out, the jcr listener reads the parent node to find out if this 
> jcr:content is a sub node of a file. If so, it reports a change on the file 
> node.
> This is required for all listeners interested in changes in files, as they 
> usually listen for a file node change, but not for the sub node /jcr:content 
> - which doesn't exist with other resource providers anyway
> The problem is that this read is done for every change of a jcr:content node, 
> regardless whether this is a file. And if several props change on such a 
> node, it is read over and over again



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-5229) Remove getAdministrativeResourceResolver() and loginAdministrative() usage from JCR components


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

Carsten Ziegeler updated SLING-5229:

Fix Version/s: (was: JCR Resource 2.9.0)
   JCR Resource 2.9.2

> Remove getAdministrativeResourceResolver() and loginAdministrative() usage 
> from JCR components
> --
>
> Key: SLING-5229
> URL: https://issues.apache.org/jira/browse/SLING-5229
> Project: Sling
>  Issue Type: Improvement
>  Components: JCR
>Reporter: Antonio Sanso
> Fix For: JCR Resource 2.9.2, JCR Installer 3.1.20, JCR 
> ContentLoader 2.2.0, JCR Compiler 2.1.2, JCR Davex 1.3.6, JCR Base 2.4.2
>
>
> * {{org.apache.sling.jcr.compiler}} : 1
> * {{org.apache.sling.installer.provider.jcr}}: 4
> * {{org.apache.sling.jcr.base}}: 2
> * {{org.apache.sling.jcr.contentloader}}: 2
> * {{org.apache.sling.jcr.davex}}: 1
> * {{org.apache.sling.jcr.resource}}: 5
> total of 15 occurrences



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-6174) Use Jackrabbit/Oak globbing support


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

Carsten Ziegeler updated SLING-6174:

Fix Version/s: (was: JCR Resource 2.9.0)
   JCR Resource 2.9.2

> Use Jackrabbit/Oak globbing support
> ---
>
> Key: SLING-6174
> URL: https://issues.apache.org/jira/browse/SLING-6174
> Project: Sling
>  Issue Type: Improvement
>  Components: JCR
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: JCR Resource 2.9.2
>
> Attachments: jcresource-patch.txt
>
>
> We recently switched back to use a jcr listener (SLING-6138) unfortunately, 
> Jackrabbit does not support glob patterns atm.
> Once JCR-4044 is fixed, we should use it.
> If the JR api will not support glob support, we have to come up with a 
> different solution as today, either
> - switch back to oak observer
> - or only register a single jcr listener on root and do the filtering 
> internally



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-6281) Provide Commons Caching (JSR 107/JCache)

2016-11-14 Thread Oliver Lietz (JIRA)


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

Oliver Lietz updated SLING-6281:

Description: 
current goals and non-goals:

* (+) API aligned to JSR 107/JCache
* (+) providing {{Cache}}s as OSGi Services
* (+) providing {{CacheManager}}s as OSGi Services
* (+) OSGi configuration support
* (-) cache invalidation
* (-) scope handling (request, thread)


> Provide Commons Caching (JSR 107/JCache)
> 
>
> Key: SLING-6281
> URL: https://issues.apache.org/jira/browse/SLING-6281
> Project: Sling
>  Issue Type: New Feature
>  Components: Commons
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
>
> current goals and non-goals:
> * (+) API aligned to JSR 107/JCache
> * (+) providing {{Cache}}s as OSGi Services
> * (+) providing {{CacheManager}}s as OSGi Services
> * (+) OSGi configuration support
> * (-) cache invalidation
> * (-) scope handling (request, thread)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-6282) Provide Commons Caching Ehcache


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

Robert Munteanu commented on SLING-6282:


Then let's discuss on the dev mailing list if you intend to submit your changes 
to Sling 'proper', I think it's best to only have one caching initiative

> Provide Commons Caching Ehcache
> ---
>
> Key: SLING-6282
> URL: https://issues.apache.org/jira/browse/SLING-6282
> Project: Sling
>  Issue Type: New Feature
>  Components: Commons
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-6282) Provide Commons Caching Ehcache

2016-11-14 Thread Oliver Lietz (JIRA)


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

Oliver Lietz commented on SLING-6282:
-

Yes, I spent half a day with what is in extensions cache. There is no release 
and they have some limitations and features which do not fit my requirements. 
See SLING-6281 also, the existing cache extensions do not use JSR 107/JCache 
API. Therefore I started from scratch in my whiteboard.

> Provide Commons Caching Ehcache
> ---
>
> Key: SLING-6282
> URL: https://issues.apache.org/jira/browse/SLING-6282
> Project: Sling
>  Issue Type: New Feature
>  Components: Commons
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (SLING-6271) ContentDispositionFilter can suppress content type upon request forwarding

2016-11-14 Thread Antonio Sanso (JIRA)


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

Antonio Sanso reassigned SLING-6271:


Assignee: Antonio Sanso

> ContentDispositionFilter can suppress content type upon request forwarding
> --
>
> Key: SLING-6271
> URL: https://issues.apache.org/jira/browse/SLING-6271
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Security 1.1.0
>Reporter: Rob Ryan
>Assignee: Antonio Sanso
> Attachments: conservative.patch.txt, simple.patch.txt
>
>
> In SLING-4604 Alessandro Bonfatti noted a use case whereby a response would 
> contain no Content-Type header despite a similar non-forwarded request would 
> have a Content-Type. He further traced it to the ContentDispositionFilter and 
> the change where I introduced a shortcut in cases the same content type was 
> being set repeatedly.
> The scenario is:
> setContentType is called
> RequestDispatcher.forward is used to forward a request to a new servlet for 
> further handling. 
> setContentType is called.
> As of SLING-4604, the second setContentType call will be ignored if it sets 
> the same content type. But even if it *is* the same, setContentType needs to 
> be called again because request forwarding clears all headers with 
> response.reset().
> I will attach two patches, one (simple) very simple, and the best performing. 
> The other (conservative) is more complex, but should still perform adequately 
> and is conservative in the following senses:
> It will always call super.setContentType when its setContentType is invoked.
> On each setContentType it will re-apply the Content-Disposition header if 
> there is not one present and the 'attachment' value is called for by the 
> configuration.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [VOTE] Release Apache Sling Authentication Service 1.3.22

On Fri, 2016-11-11 at 15:12 +, Antonio Sanso wrote:
> Please vote to approve this release:

+1

Robert

signature.asc
Description: This is a digitally signed message part

Re: [VOTE] Release Apache Sling Authentication Service 1.3.22

2016-11-14 Thread Antonio Sanso

my own +1

regards

antonio
On Nov 11, 2016, at 4:12 PM, Antonio Sanso  wrote:

> Hi,
> 
> We solved 1 issues in this release:
> https://issues.apache.org/jira/browse/SLING/fixforversion/12338698
> 
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-1574/
> 
> You can use this UNIX script to download the release and verify the 
> signatures:
> http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh
> 
> Usage:
> sh check_staged_release.sh 1574 /tmp/sling-staging
> 
> Please vote to approve this release:
> 
>  [ ] +1 Approve the release
>  [ ]  0 Don't care
>  [ ] -1 Don't release, because ...
> 
> This majority vote is open for at least 72 hours.

[jira] [Commented] (SLING-6282) Provide Commons Caching Ehcache