[jira] [Resolved] (JCR-4251) Release Jackrabbit 2.17.1

2018-02-01 Thread Julian Reschke (JIRA)

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

Julian Reschke resolved JCR-4251.
-
Resolution: Fixed

> Release Jackrabbit 2.17.1
> -
>
> Key: JCR-4251
> URL: https://issues.apache.org/jira/browse/JCR-4251
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[ANNOUNCE] Apache Jackrabbit 2.17.1 released

2018-02-01 Thread Julian Reschke

The Apache Jackrabbit community is pleased to announce the release of
Apache Jackrabbit 2.17.1. The release is available for download at:

 http://jackrabbit.apache.org/downloads.html

See the full release notes below for details about this release:

Release Notes -- Apache Jackrabbit -- Version 2.17.1

Introduction


This is Apache Jackrabbit(TM) 2.17.1, a fully compliant implementation 
of the

Content Repository for Java(TM) Technology API, version 2.0 (JCR 2.0) as
specified in the Java Specification Request 283 (JSR 283).

Apache Jackrabbit 2.17.1 is an unstable release cut directly from
Jackrabbit trunk, with a focus on new features and other
improvements. For production use we recommend the latest stable 2.16.x
release.

Changes in Jackrabbit 2.17.1


Bug

[JCR-4241] - Jacoco plugin fails with exception
[JCR-4242] - Build failure: unapproved license

Improvement

[JCR-4001] - When using Node.getProperties(String namePattern) also 
child nodes are processed

[JCR-4237] - cleanup throws clauses of private methods
[JCR-4238] - use StandardCharsets to avoid having to handle 
UnsupportedEncodingException

[JCR-4239] - Suppress Tika startup warnings
[JCR-4249] - Introduce replacement for java.security.acl.Group

Task

[JCR-4215] - Use Tika version 1.17
[JCR-4229] - Remove Oak dependency in webapp
[JCR-4236] - remove obsolete textFilterClasses config parameters
[JCR-4240] - IndexingQueueTest relies on Tika behavior that is 
changed in Tika 1.17

[JCR-4244] - Upgrade tomcat dependency to 8.5.24
[JCR-4247] - Update commons-io dependency
[JCR-4248] - Upgrade httpcore dependency to 4.4.9
[JCR-4250] - remove guava dependency
[JCR-4252] - Upgrade httpclient dependency to 4.5.5

In addition to the above-mentioned changes, this release contains
all the changes included up to the Apache Jackrabbit 2.16.x release.

For more detailed information about all the changes in this and other
Jackrabbit releases, please see the Jackrabbit issue tracker at

https://issues.apache.org/jira/browse/JCR

Release Contents


This release consists of a single source archive packaged as a zip file.
The archive can be unpacked with the jar tool from your JDK installation.
See the README.txt file for instructions on how to build this release.

The source archive is accompanied by SHA1 and MD5 checksums and a PGP
signature that you can use to verify the authenticity of your download.
The public key used for the PGP signature can be found at
https://svn.apache.org/repos/asf/jackrabbit/dist/KEYS.

About Apache Jackrabbit
---

Apache Jackrabbit is a fully conforming implementation of the Content
Repository for Java Technology API (JCR). A content repository is a
hierarchical content store with support for structured and unstructured
content, full text search, versioning, transactions, observation, and
more.

For more information, visit http://jackrabbit.apache.org/

About The Apache Software Foundation


Established in 1999, The Apache Software Foundation provides organizational,
legal, and financial support for more than 140 freely-available,
collaboratively-developed Open Source projects. The pragmatic Apache License
enables individual and commercial users to easily deploy Apache software;
the Foundation's intellectual property framework limits the legal exposure
of its 3,800+ contributors.

For more information, visit http://www.apache.org/

Trademarks
--

Apache Jackrabbit, Jackrabbit, Apache, the Apache feather logo, and the 
Apache

Jackrabbit project logo are trademarks of The Apache Software Foundation.


[jira] [Closed] (JCR-4248) Upgrade httpcore dependency to 4.4.9

2018-02-01 Thread Julian Reschke (JIRA)

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

Julian Reschke closed JCR-4248.
---

> Upgrade httpcore dependency to 4.4.9
> 
>
> Key: JCR-4248
> URL: https://issues.apache.org/jira/browse/JCR-4248
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>  Components: jackrabbit-webapp
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Trivial
>  Labels: candidate_jcr_2_16
> Fix For: 2.18, 2.17.1
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (JCR-4241) Jacoco plugin fails with exception

2018-02-01 Thread Julian Reschke (JIRA)

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

Julian Reschke closed JCR-4241.
---

> Jacoco plugin fails with exception
> --
>
> Key: JCR-4241
> URL: https://issues.apache.org/jira/browse/JCR-4241
> Project: Jackrabbit Content Repository
>  Issue Type: Bug
>  Components: jackrabbit-webapp
>Affects Versions: 2.16, 2.12.8, 2.14.3
>Reporter: Marcel Reutegger
>Assignee: Marcel Reutegger
>Priority: Minor
> Fix For: 2.18, 2.12.9, 2.14.5, 2.16.1, 2.17.1
>
>
> The build fails when the jacoco plugin is enabled. See also recent Jenkins 
> failures. E.g. 
> https://builds.apache.org/job/Jackrabbit-trunk/2555/org.apache.jackrabbit$jackrabbit-webapp/console



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (JCR-4252) Upgrade httpclient dependency to 4.5.5

2018-02-01 Thread Julian Reschke (JIRA)

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

Julian Reschke closed JCR-4252.
---

> Upgrade httpclient dependency to 4.5.5
> --
>
> Key: JCR-4252
> URL: https://issues.apache.org/jira/browse/JCR-4252
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>  Components: jackrabbit-webapp
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Trivial
>  Labels: candidate_jcr_2_16
> Fix For: 2.18, 2.17.1
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (JCR-4215) Use Tika version 1.17

2018-02-01 Thread Julian Reschke (JIRA)

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

Julian Reschke closed JCR-4215.
---

> Use Tika version 1.17
> -
>
> Key: JCR-4215
> URL: https://issues.apache.org/jira/browse/JCR-4215
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Major
>  Labels: candidate_jcr_2_16
> Fix For: 2.18, 2.17.1
>
> Attachments: 
> TEST-org.apache.jackrabbit.core.query.lucene.IndexingQueueTest.xml, 
> org.apache.jackrabbit.core.query.lucene.IndexingQueueTest.log, 
> org.apache.jackrabbit.core.query.lucene.IndexingQueueTest.txt
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (JCR-4229) Remove Oak dependency in webapp

2018-02-01 Thread Julian Reschke (JIRA)

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

Julian Reschke closed JCR-4229.
---

> Remove Oak dependency in webapp
> ---
>
> Key: JCR-4229
> URL: https://issues.apache.org/jira/browse/JCR-4229
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>  Components: jackrabbit-webapp
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
> Fix For: 2.18, 2.17.1
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (JCR-4001) When using Node.getProperties(String namePattern) also child nodes are processed

2018-02-01 Thread Julian Reschke (JIRA)

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

Julian Reschke closed JCR-4001.
---

> When using Node.getProperties(String namePattern) also child nodes are 
> processed
> 
>
> Key: JCR-4001
> URL: https://issues.apache.org/jira/browse/JCR-4001
> Project: Jackrabbit Content Repository
>  Issue Type: Improvement
>  Components: jackrabbit-jcr-commons
>Reporter: Luca Tagliani
>Assignee: Julian Reschke
>Priority: Major
>  Labels: candidate_jcr_2_16
> Fix For: 2.18, 2.17.1
>
> Attachments: JCR-4001-2.diff, JCR-4001.patch
>
>
> Call to Node.getProperties(String namePattern) processed also child nodes and 
> not only properties.
> This can deteriorate performance when there are lots of children.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (JCR-4247) Update commons-io dependency

2018-02-01 Thread Julian Reschke (JIRA)

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

Julian Reschke closed JCR-4247.
---

> Update commons-io dependency
> 
>
> Key: JCR-4247
> URL: https://issues.apache.org/jira/browse/JCR-4247
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>  Components: parent
>Affects Versions: 2.18
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
>  Labels: candidate_jcr_2_16
> Fix For: 2.17.1
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (JCR-4244) Upgrade tomcat dependency to 8.5.24

2018-02-01 Thread Julian Reschke (JIRA)

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

Julian Reschke closed JCR-4244.
---

> Upgrade tomcat dependency to 8.5.24
> ---
>
> Key: JCR-4244
> URL: https://issues.apache.org/jira/browse/JCR-4244
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>  Components: jackrabbit-webapp
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Major
>  Labels: candidate_jcr_2_16
> Fix For: 2.18, 2.17.1
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (JCR-4249) Introduce replacement for java.security.acl.Group

2018-02-01 Thread Julian Reschke (JIRA)

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

Julian Reschke closed JCR-4249.
---

> Introduce replacement for java.security.acl.Group
> -
>
> Key: JCR-4249
> URL: https://issues.apache.org/jira/browse/JCR-4249
> Project: Jackrabbit Content Repository
>  Issue Type: Improvement
>  Components: JCR API, security
>Reporter: Alex Deparvu
>Assignee: Alex Deparvu
>Priority: Major
> Fix For: 2.18, 2.17.1
>
> Attachments: JCR-4249-v2.patch, JCR-4249.patch
>
>
> See OAK-7024 and JCR-4246 for more information.
> I've decided to split off the api changes to have them in early for a release 
> so both projects could use the same class as replacement of the Group.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[RESULT] [VOTE] Release Apache Jackrabbit 2.17.1

2018-02-01 Thread Julian Reschke

On 2018-01-30 06:50, Julian Reschke wrote:

...


Hi there,

the vote passes as follows:

+1 Claus Köll 
+1 Dave Brosius 
+1 Davide Giannella 
+1 Julian Reschke 
+1 Marcel Reutegger 

Thanks for voting. I'll push the release out.

Best regards, Julian



[jira] [Commented] (JCR-3923) Repository root doesn't respect rep:glob

2018-02-01 Thread Kamil (JIRA)

[ 
https://issues.apache.org/jira/browse/JCR-3923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16349096#comment-16349096
 ] 

Kamil commented on JCR-3923:


Don't you think that it is rather unintuitive that "/" doesn't match the root 
node?
I think this is the main issue...
Moreover - how do you want to differentiate between "matches node / only" and 
"/ and all descendants"?

> Repository root doesn't respect rep:glob
> 
>
> Key: JCR-3923
> URL: https://issues.apache.org/jira/browse/JCR-3923
> Project: Jackrabbit Content Repository
>  Issue Type: Bug
>Reporter: Kamil
>Priority: Major
>
> I have following node structure:
> {noformat}
> /test
> /test/child
> /foo
> {noformat}
> When I set Principal based privileges to some user as:
> {noformat}
> Map restrictions = new HashMap();
> ValueFactory vf = session.getValueFactory();
> restrictions.put("rep:nodePath", vf.createValue("/test", PropertyType.PATH));
> restrictions.put("rep:glob",  vf.createValue(""));
>   
> jacl.addEntry(principal, privileges, allow, restrictions);
>   
> acManager.setPolicy(jacl.getPath(), jacl);
> session.save();
> {noformat}
> where according to this documentation 
> http://jackrabbit.apache.org/api/2.2/org/apache/jackrabbit/core/security/authorization/GlobPattern.html
>  empty string means "matches /foo only", user can see only:
> {noformat}
> /test
> {noformat}
> without a child, which is correct. But when I set:
> {noformat}
> Map restrictions = new HashMap();
> ValueFactory vf = session.getValueFactory();
> restrictions.put("rep:nodePath", vf.createValue("/", PropertyType.PATH));
> restrictions.put("rep:glob",  vf.createValue(""));
>   
> jacl.addEntry(principal, privileges, allow, restrictions);
>   
> acManager.setPolicy(jacl.getPath(), jacl);
> session.save();
> {noformat}
> then user can see all descendants of root:
> {noformat}
> /test
> /test/child
> /foo
> {noformat}
> which is not correct



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: adaptTo() 2018: Tickets now available / Start Call for Papers

2018-02-01 Thread Tommaso Teofili
I am sorry if your company lost money with adaptTo, that's organizer's
decision whether to make it or not and how much to ask people to pay, no
doubt about it. Of course good venue / food / etc are expensive, but still
IMHO it sounds a crazy price (and it's an early bird!) for an event meant
to gather people with possibly different backgrounds from our communities.

My 2 cents,
Tommaso

Il giorno gio 1 feb 2018 alle ore 18:01 Stefan Seifert <
sseif...@pro-vision.de> ha scritto:

> hello tommaso.
>
> thanks for the feedback...
>
> we did not make the decision on the prices lightheartedly. in the last 7
> years we never made any profit with adaptTo() (and did not intend to do
> so), but most times paid on top, even with having some sponsors. this year
> we have a bigger location, having a good environment, food, (working) WLAN
> etc. - that's all expensive.
>
> please note there is 50% discount on the regular price for apache
> committers (any project), perhaps this hint is a bit hidden in our website.
>
> stefan
>
>
> >-Original Message-
> >From: Tommaso Teofili [mailto:tommaso.teof...@gmail.com]
> >Sent: Thursday, February 1, 2018 5:52 PM
> >To: dev@jackrabbit.apache.org
> >Cc: us...@jackrabbit.apache.org; oak-...@jackrabbit.apache.org
> >Subject: Re: adaptTo() 2018: Tickets now available / Start Call for Papers
> >
> >Hi Sebastian,
> >
> >here's my feedback: 599€ as an early bird price sounds crazy and it's all
> >but inclusive for people not being backed by companies willing to pay the
> >conference.
> >
> >Regards,
> >Tommaso
> >
> >Il giorno gio 1 feb 2018 alle ore 15:57 Stefan Seifert <
> >sseif...@pro-vision.de> ha scritto:
> >
> >> Dear adaptTo() Community,
> >>
> >> the sale of tickets for adaptTo() 2018 is open.
> >>
> >> Get your Early-Bird-Ticket here: https://adapt.to/tickets
> >>
> >> We also started the Call for Papers today! If you would like to be a
> >> speaker, please check out https://adapt.to/cfp
> >>
> >> Focusing on Apache Sling, Apache Felix and Apache Jackrabbit, the
> >> adaptTo() conference in Potsdam (near Berlin) is aimed at developers
> >using
> >> some or all if this stack.
> >>
> >> This year´s conference date is 10 - 12 September; latest information can
> >> be found on https://adapt.to
> >>
> >> Kind regards on behalf of the adaptTo() Team,
> >> Stefan
> >>
> >>
> >>
>


[jira] [Commented] (JCR-3923) Repository root doesn't respect rep:glob

2018-02-01 Thread Konrad Windszus (JIRA)

[ 
https://issues.apache.org/jira/browse/JCR-3923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16348945#comment-16348945
 ] 

Konrad Windszus commented on JCR-3923:
--

Done in https://issues.apache.org/jira/browse/OAK-7233.

> Repository root doesn't respect rep:glob
> 
>
> Key: JCR-3923
> URL: https://issues.apache.org/jira/browse/JCR-3923
> Project: Jackrabbit Content Repository
>  Issue Type: Bug
>Reporter: Kamil
>Priority: Major
>
> I have following node structure:
> {noformat}
> /test
> /test/child
> /foo
> {noformat}
> When I set Principal based privileges to some user as:
> {noformat}
> Map restrictions = new HashMap();
> ValueFactory vf = session.getValueFactory();
> restrictions.put("rep:nodePath", vf.createValue("/test", PropertyType.PATH));
> restrictions.put("rep:glob",  vf.createValue(""));
>   
> jacl.addEntry(principal, privileges, allow, restrictions);
>   
> acManager.setPolicy(jacl.getPath(), jacl);
> session.save();
> {noformat}
> where according to this documentation 
> http://jackrabbit.apache.org/api/2.2/org/apache/jackrabbit/core/security/authorization/GlobPattern.html
>  empty string means "matches /foo only", user can see only:
> {noformat}
> /test
> {noformat}
> without a child, which is correct. But when I set:
> {noformat}
> Map restrictions = new HashMap();
> ValueFactory vf = session.getValueFactory();
> restrictions.put("rep:nodePath", vf.createValue("/", PropertyType.PATH));
> restrictions.put("rep:glob",  vf.createValue(""));
>   
> jacl.addEntry(principal, privileges, allow, restrictions);
>   
> acManager.setPolicy(jacl.getPath(), jacl);
> session.save();
> {noformat}
> then user can see all descendants of root:
> {noformat}
> /test
> /test/child
> /foo
> {noformat}
> which is not correct



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (JCR-3923) Repository root doesn't respect rep:glob

2018-02-01 Thread angela (JIRA)

[ 
https://issues.apache.org/jira/browse/JCR-3923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16348911#comment-16348911
 ] 

angela commented on JCR-3923:
-

[~kwin], can you file a documentation issue with 
https://issues.apache.org/jira/projects/OAK then we can take care of explicitly 
mentioning the concat-nature and highlight the fact that for the root-node a 
leading / in the pattern won't work.

> Repository root doesn't respect rep:glob
> 
>
> Key: JCR-3923
> URL: https://issues.apache.org/jira/browse/JCR-3923
> Project: Jackrabbit Content Repository
>  Issue Type: Bug
>Reporter: Kamil
>Priority: Major
>
> I have following node structure:
> {noformat}
> /test
> /test/child
> /foo
> {noformat}
> When I set Principal based privileges to some user as:
> {noformat}
> Map restrictions = new HashMap();
> ValueFactory vf = session.getValueFactory();
> restrictions.put("rep:nodePath", vf.createValue("/test", PropertyType.PATH));
> restrictions.put("rep:glob",  vf.createValue(""));
>   
> jacl.addEntry(principal, privileges, allow, restrictions);
>   
> acManager.setPolicy(jacl.getPath(), jacl);
> session.save();
> {noformat}
> where according to this documentation 
> http://jackrabbit.apache.org/api/2.2/org/apache/jackrabbit/core/security/authorization/GlobPattern.html
>  empty string means "matches /foo only", user can see only:
> {noformat}
> /test
> {noformat}
> without a child, which is correct. But when I set:
> {noformat}
> Map restrictions = new HashMap();
> ValueFactory vf = session.getValueFactory();
> restrictions.put("rep:nodePath", vf.createValue("/", PropertyType.PATH));
> restrictions.put("rep:glob",  vf.createValue(""));
>   
> jacl.addEntry(principal, privileges, allow, restrictions);
>   
> acManager.setPolicy(jacl.getPath(), jacl);
> session.save();
> {noformat}
> then user can see all descendants of root:
> {noformat}
> /test
> /test/child
> /foo
> {noformat}
> which is not correct



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


FW: adaptTo() 2018: Tickets now available / Start Call for Papers

2018-02-01 Thread Stefan Seifert
forgot to mention: there is a discount for apache committers (any project - 
sling, felix, jackrabbit)
see https://adapt.to/conference for details.

stefan

-Original Message-
From: Stefan Seifert [mailto:sseif...@pro-vision.de] 
Sent: Thursday, February 1, 2018 3:58 PM
To: d...@jackrabbit.apache.org; us...@jackrabbit.apache.org; 
oak-dev@jackrabbit.apache.org
Subject: adaptTo() 2018: Tickets now available / Start Call for Papers

Dear adaptTo() Community,

the sale of tickets for adaptTo() 2018 is open.

Get your Early-Bird-Ticket here: https://adapt.to/tickets

We also started the Call for Papers today! If you would like to be a speaker, 
please check out https://adapt.to/cfp 

Focusing on Apache Sling, Apache Felix and Apache Jackrabbit, the adaptTo() 
conference in Potsdam (near Berlin) is aimed at developers using some or all if 
this stack.

This year´s conference date is 10 - 12 September; latest information can be 
found on https://adapt.to

Kind regards on behalf of the adaptTo() Team,
Stefan






FW: adaptTo() 2018: Tickets now available / Start Call for Papers

2018-02-01 Thread Stefan Seifert
forgot to mention: there is a discount for apache committers (any project - 
sling, felix, jackrabbit)
see https://adapt.to/conference for details.

stefan

-Original Message-
From: Stefan Seifert [mailto:sseif...@pro-vision.de] 
Sent: Thursday, February 1, 2018 3:58 PM
To: dev@jackrabbit.apache.org; us...@jackrabbit.apache.org; 
oak-...@jackrabbit.apache.org
Subject: adaptTo() 2018: Tickets now available / Start Call for Papers

Dear adaptTo() Community,

the sale of tickets for adaptTo() 2018 is open.

Get your Early-Bird-Ticket here: https://adapt.to/tickets

We also started the Call for Papers today! If you would like to be a speaker, 
please check out https://adapt.to/cfp 

Focusing on Apache Sling, Apache Felix and Apache Jackrabbit, the adaptTo() 
conference in Potsdam (near Berlin) is aimed at developers using some or all if 
this stack.

This year´s conference date is 10 - 12 September; latest information can be 
found on https://adapt.to

Kind regards on behalf of the adaptTo() Team,
Stefan






[jira] [Comment Edited] (JCR-3923) Repository root doesn't respect rep:glob

2018-02-01 Thread Konrad Windszus (JIRA)

[ 
https://issues.apache.org/jira/browse/JCR-3923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16348902#comment-16348902
 ] 

Konrad Windszus edited comment on JCR-3923 at 2/1/18 5:00 PM:
--

[~anchela] Thanks a lot for your hints. In our case it seems indeed like we are 
using a {{rep:glob}} with a leading "/". Could you reference some documentation 
which states how the rep:glob is exactly taken into consideration (which makes 
it obvious that the rep:glob should never start with a "/")? The examples at 
https://jackrabbit.apache.org/oak/docs/security/authorization/restriction.html#Examples
 are not clear enough. Maybe that could be extended with an example for the 
root node.


was (Author: kwin):
[~anchela] Thanks a lot for your hints. In our case it seems indeed like we are 
using a {{rep:glob}} with a leading "/". Could you reference some documentation 
which states how the rep:glob is exactly taken into consideration (which makes 
it obvious that the rep:glob should never start with a "/")?

> Repository root doesn't respect rep:glob
> 
>
> Key: JCR-3923
> URL: https://issues.apache.org/jira/browse/JCR-3923
> Project: Jackrabbit Content Repository
>  Issue Type: Bug
>Reporter: Kamil
>Priority: Major
>
> I have following node structure:
> {noformat}
> /test
> /test/child
> /foo
> {noformat}
> When I set Principal based privileges to some user as:
> {noformat}
> Map restrictions = new HashMap();
> ValueFactory vf = session.getValueFactory();
> restrictions.put("rep:nodePath", vf.createValue("/test", PropertyType.PATH));
> restrictions.put("rep:glob",  vf.createValue(""));
>   
> jacl.addEntry(principal, privileges, allow, restrictions);
>   
> acManager.setPolicy(jacl.getPath(), jacl);
> session.save();
> {noformat}
> where according to this documentation 
> http://jackrabbit.apache.org/api/2.2/org/apache/jackrabbit/core/security/authorization/GlobPattern.html
>  empty string means "matches /foo only", user can see only:
> {noformat}
> /test
> {noformat}
> without a child, which is correct. But when I set:
> {noformat}
> Map restrictions = new HashMap();
> ValueFactory vf = session.getValueFactory();
> restrictions.put("rep:nodePath", vf.createValue("/", PropertyType.PATH));
> restrictions.put("rep:glob",  vf.createValue(""));
>   
> jacl.addEntry(principal, privileges, allow, restrictions);
>   
> acManager.setPolicy(jacl.getPath(), jacl);
> session.save();
> {noformat}
> then user can see all descendants of root:
> {noformat}
> /test
> /test/child
> /foo
> {noformat}
> which is not correct



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


RE: adaptTo() 2018: Tickets now available / Start Call for Papers

2018-02-01 Thread Stefan Seifert
hello tommaso.

thanks for the feedback...

we did not make the decision on the prices lightheartedly. in the last 7 years 
we never made any profit with adaptTo() (and did not intend to do so), but most 
times paid on top, even with having some sponsors. this year we have a bigger 
location, having a good environment, food, (working) WLAN etc. - that's all 
expensive.

please note there is 50% discount on the regular price for apache committers 
(any project), perhaps this hint is a bit hidden in our website.

stefan


>-Original Message-
>From: Tommaso Teofili [mailto:tommaso.teof...@gmail.com]
>Sent: Thursday, February 1, 2018 5:52 PM
>To: dev@jackrabbit.apache.org
>Cc: us...@jackrabbit.apache.org; oak-...@jackrabbit.apache.org
>Subject: Re: adaptTo() 2018: Tickets now available / Start Call for Papers
>
>Hi Sebastian,
>
>here's my feedback: 599€ as an early bird price sounds crazy and it's all
>but inclusive for people not being backed by companies willing to pay the
>conference.
>
>Regards,
>Tommaso
>
>Il giorno gio 1 feb 2018 alle ore 15:57 Stefan Seifert <
>sseif...@pro-vision.de> ha scritto:
>
>> Dear adaptTo() Community,
>>
>> the sale of tickets for adaptTo() 2018 is open.
>>
>> Get your Early-Bird-Ticket here: https://adapt.to/tickets
>>
>> We also started the Call for Papers today! If you would like to be a
>> speaker, please check out https://adapt.to/cfp
>>
>> Focusing on Apache Sling, Apache Felix and Apache Jackrabbit, the
>> adaptTo() conference in Potsdam (near Berlin) is aimed at developers
>using
>> some or all if this stack.
>>
>> This year´s conference date is 10 - 12 September; latest information can
>> be found on https://adapt.to
>>
>> Kind regards on behalf of the adaptTo() Team,
>> Stefan
>>
>>
>>


[jira] [Commented] (JCR-3923) Repository root doesn't respect rep:glob

2018-02-01 Thread Konrad Windszus (JIRA)

[ 
https://issues.apache.org/jira/browse/JCR-3923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16348902#comment-16348902
 ] 

Konrad Windszus commented on JCR-3923:
--

[~anchela] Thanks a lot for your hints. In our case it seems indeed like we are 
using a {{rep:glob}} with a leading "/". Could you reference some documentation 
which states how the rep:glob is exactly taken into consideration (which makes 
it obvious that the rep:glob should never start with a "/")?

> Repository root doesn't respect rep:glob
> 
>
> Key: JCR-3923
> URL: https://issues.apache.org/jira/browse/JCR-3923
> Project: Jackrabbit Content Repository
>  Issue Type: Bug
>Reporter: Kamil
>Priority: Major
>
> I have following node structure:
> {noformat}
> /test
> /test/child
> /foo
> {noformat}
> When I set Principal based privileges to some user as:
> {noformat}
> Map restrictions = new HashMap();
> ValueFactory vf = session.getValueFactory();
> restrictions.put("rep:nodePath", vf.createValue("/test", PropertyType.PATH));
> restrictions.put("rep:glob",  vf.createValue(""));
>   
> jacl.addEntry(principal, privileges, allow, restrictions);
>   
> acManager.setPolicy(jacl.getPath(), jacl);
> session.save();
> {noformat}
> where according to this documentation 
> http://jackrabbit.apache.org/api/2.2/org/apache/jackrabbit/core/security/authorization/GlobPattern.html
>  empty string means "matches /foo only", user can see only:
> {noformat}
> /test
> {noformat}
> without a child, which is correct. But when I set:
> {noformat}
> Map restrictions = new HashMap();
> ValueFactory vf = session.getValueFactory();
> restrictions.put("rep:nodePath", vf.createValue("/", PropertyType.PATH));
> restrictions.put("rep:glob",  vf.createValue(""));
>   
> jacl.addEntry(principal, privileges, allow, restrictions);
>   
> acManager.setPolicy(jacl.getPath(), jacl);
> session.save();
> {noformat}
> then user can see all descendants of root:
> {noformat}
> /test
> /test/child
> /foo
> {noformat}
> which is not correct



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: adaptTo() 2018: Tickets now available / Start Call for Papers

2018-02-01 Thread Tommaso Teofili
sorry, I meant to write Stefan, not Sebastian, of course.

Regards,
Tommaso

Il giorno gio 1 feb 2018 alle ore 17:52 Tommaso Teofili <
tommaso.teof...@gmail.com> ha scritto:

> Hi Sebastian,
>
> here's my feedback: 599€ as an early bird price sounds crazy and it's all
> but inclusive for people not being backed by companies willing to pay the
> conference.
>
> Regards,
> Tommaso
>
>
> Il giorno gio 1 feb 2018 alle ore 15:57 Stefan Seifert <
> sseif...@pro-vision.de> ha scritto:
>
>> Dear adaptTo() Community,
>>
>> the sale of tickets for adaptTo() 2018 is open.
>>
>> Get your Early-Bird-Ticket here: https://adapt.to/tickets
>>
>> We also started the Call for Papers today! If you would like to be a
>> speaker, please check out https://adapt.to/cfp
>>
>> Focusing on Apache Sling, Apache Felix and Apache Jackrabbit, the
>> adaptTo() conference in Potsdam (near Berlin) is aimed at developers using
>> some or all if this stack.
>>
>> This year´s conference date is 10 - 12 September; latest information can
>> be found on https://adapt.to
>>
>> Kind regards on behalf of the adaptTo() Team,
>> Stefan
>>
>>
>>


Re: adaptTo() 2018: Tickets now available / Start Call for Papers

2018-02-01 Thread Tommaso Teofili
Hi Sebastian,

here's my feedback: 599€ as an early bird price sounds crazy and it's all
but inclusive for people not being backed by companies willing to pay the
conference.

Regards,
Tommaso

Il giorno gio 1 feb 2018 alle ore 15:57 Stefan Seifert <
sseif...@pro-vision.de> ha scritto:

> Dear adaptTo() Community,
>
> the sale of tickets for adaptTo() 2018 is open.
>
> Get your Early-Bird-Ticket here: https://adapt.to/tickets
>
> We also started the Call for Papers today! If you would like to be a
> speaker, please check out https://adapt.to/cfp
>
> Focusing on Apache Sling, Apache Felix and Apache Jackrabbit, the
> adaptTo() conference in Potsdam (near Berlin) is aimed at developers using
> some or all if this stack.
>
> This year´s conference date is 10 - 12 September; latest information can
> be found on https://adapt.to
>
> Kind regards on behalf of the adaptTo() Team,
> Stefan
>
>
>


Re: adaptTo() 2018: Tickets now available / Start Call for Papers

2018-02-01 Thread Tommaso Teofili
Hi Sebastian,

here's my feedback: 599€ as an early bird price sounds crazy and it's all
but inclusive for people not being backed by companies willing to pay the
conference.

Regards,
Tommaso

Il giorno gio 1 feb 2018 alle ore 15:57 Stefan Seifert <
sseif...@pro-vision.de> ha scritto:

> Dear adaptTo() Community,
>
> the sale of tickets for adaptTo() 2018 is open.
>
> Get your Early-Bird-Ticket here: https://adapt.to/tickets
>
> We also started the Call for Papers today! If you would like to be a
> speaker, please check out https://adapt.to/cfp
>
> Focusing on Apache Sling, Apache Felix and Apache Jackrabbit, the
> adaptTo() conference in Potsdam (near Berlin) is aimed at developers using
> some or all if this stack.
>
> This year´s conference date is 10 - 12 September; latest information can
> be found on https://adapt.to
>
> Kind regards on behalf of the adaptTo() Team,
> Stefan
>
>
>


[jira] [Comment Edited] (JCR-3923) Repository root doesn't respect rep:glob

2018-02-01 Thread angela (JIRA)

[ 
https://issues.apache.org/jira/browse/JCR-3923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16348836#comment-16348836
 ] 

angela edited comment on JCR-3923 at 2/1/18 4:21 PM:
-

[~reschke], it should also work on the root node. I don't know about 
jackrabbit-core but afaik it works with Oak (there should even be some test 
case if i remember correctly). One common mistake though is that the specified 
pattern is defined with a leading path, which on the root node will result in 
an invalid path that is never matched as the GlobPattern just concatenates 
string.
in any case issues with Oak should be reported with the Oak project as it's a 
separate code base with a separate jira bucket.


was (Author: anchela):
[~reschke], it should also work on the root node. I don't know about 
jackrabbit-core but afaik it works with Oak (there should even be some test 
case if i remember correctly). One common mistake though is that the specified 
pattern is defined with a leading path, which on the root node will result in 
an invalid path that is never matched as the GlobPattern just concatenates 
string.

> Repository root doesn't respect rep:glob
> 
>
> Key: JCR-3923
> URL: https://issues.apache.org/jira/browse/JCR-3923
> Project: Jackrabbit Content Repository
>  Issue Type: Bug
>Reporter: Kamil
>Priority: Major
>
> I have following node structure:
> {noformat}
> /test
> /test/child
> /foo
> {noformat}
> When I set Principal based privileges to some user as:
> {noformat}
> Map restrictions = new HashMap();
> ValueFactory vf = session.getValueFactory();
> restrictions.put("rep:nodePath", vf.createValue("/test", PropertyType.PATH));
> restrictions.put("rep:glob",  vf.createValue(""));
>   
> jacl.addEntry(principal, privileges, allow, restrictions);
>   
> acManager.setPolicy(jacl.getPath(), jacl);
> session.save();
> {noformat}
> where according to this documentation 
> http://jackrabbit.apache.org/api/2.2/org/apache/jackrabbit/core/security/authorization/GlobPattern.html
>  empty string means "matches /foo only", user can see only:
> {noformat}
> /test
> {noformat}
> without a child, which is correct. But when I set:
> {noformat}
> Map restrictions = new HashMap();
> ValueFactory vf = session.getValueFactory();
> restrictions.put("rep:nodePath", vf.createValue("/", PropertyType.PATH));
> restrictions.put("rep:glob",  vf.createValue(""));
>   
> jacl.addEntry(principal, privileges, allow, restrictions);
>   
> acManager.setPolicy(jacl.getPath(), jacl);
> session.save();
> {noformat}
> then user can see all descendants of root:
> {noformat}
> /test
> /test/child
> /foo
> {noformat}
> which is not correct



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (JCR-3923) Repository root doesn't respect rep:glob

2018-02-01 Thread angela (JIRA)

[ 
https://issues.apache.org/jira/browse/JCR-3923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16348836#comment-16348836
 ] 

angela commented on JCR-3923:
-

[~reschke], it should also work on the root node. I don't know about 
jackrabbit-core but afaik it works with Oak (there should even be some test 
case if i remember correctly). One common mistake though is that the specified 
pattern is defined with a leading path, which on the root node will result in 
an invalid path that is never matched as the GlobPattern just concatenates 
string.

> Repository root doesn't respect rep:glob
> 
>
> Key: JCR-3923
> URL: https://issues.apache.org/jira/browse/JCR-3923
> Project: Jackrabbit Content Repository
>  Issue Type: Bug
>Reporter: Kamil
>Priority: Major
>
> I have following node structure:
> {noformat}
> /test
> /test/child
> /foo
> {noformat}
> When I set Principal based privileges to some user as:
> {noformat}
> Map restrictions = new HashMap();
> ValueFactory vf = session.getValueFactory();
> restrictions.put("rep:nodePath", vf.createValue("/test", PropertyType.PATH));
> restrictions.put("rep:glob",  vf.createValue(""));
>   
> jacl.addEntry(principal, privileges, allow, restrictions);
>   
> acManager.setPolicy(jacl.getPath(), jacl);
> session.save();
> {noformat}
> where according to this documentation 
> http://jackrabbit.apache.org/api/2.2/org/apache/jackrabbit/core/security/authorization/GlobPattern.html
>  empty string means "matches /foo only", user can see only:
> {noformat}
> /test
> {noformat}
> without a child, which is correct. But when I set:
> {noformat}
> Map restrictions = new HashMap();
> ValueFactory vf = session.getValueFactory();
> restrictions.put("rep:nodePath", vf.createValue("/", PropertyType.PATH));
> restrictions.put("rep:glob",  vf.createValue(""));
>   
> jacl.addEntry(principal, privileges, allow, restrictions);
>   
> acManager.setPolicy(jacl.getPath(), jacl);
> session.save();
> {noformat}
> then user can see all descendants of root:
> {noformat}
> /test
> /test/child
> /foo
> {noformat}
> which is not correct



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (JCR-3923) Repository root doesn't respect rep:glob

2018-02-01 Thread Julian Reschke (JIRA)

[ 
https://issues.apache.org/jira/browse/JCR-3923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16348787#comment-16348787
 ] 

Julian Reschke commented on JCR-3923:
-

I don't know this part of the code well enough to understand whether this is by 
design or not ([~anchela]?).

That said, this is not code shared with Oak, but I see that Oak has a similar 
class in 
https://github.com/apache/jackrabbit-oak/blob/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/security/authorization/restriction/GlobPattern.java

> Repository root doesn't respect rep:glob
> 
>
> Key: JCR-3923
> URL: https://issues.apache.org/jira/browse/JCR-3923
> Project: Jackrabbit Content Repository
>  Issue Type: Bug
>Reporter: Kamil
>Priority: Major
>
> I have following node structure:
> {noformat}
> /test
> /test/child
> /foo
> {noformat}
> When I set Principal based privileges to some user as:
> {noformat}
> Map restrictions = new HashMap();
> ValueFactory vf = session.getValueFactory();
> restrictions.put("rep:nodePath", vf.createValue("/test", PropertyType.PATH));
> restrictions.put("rep:glob",  vf.createValue(""));
>   
> jacl.addEntry(principal, privileges, allow, restrictions);
>   
> acManager.setPolicy(jacl.getPath(), jacl);
> session.save();
> {noformat}
> where according to this documentation 
> http://jackrabbit.apache.org/api/2.2/org/apache/jackrabbit/core/security/authorization/GlobPattern.html
>  empty string means "matches /foo only", user can see only:
> {noformat}
> /test
> {noformat}
> without a child, which is correct. But when I set:
> {noformat}
> Map restrictions = new HashMap();
> ValueFactory vf = session.getValueFactory();
> restrictions.put("rep:nodePath", vf.createValue("/", PropertyType.PATH));
> restrictions.put("rep:glob",  vf.createValue(""));
>   
> jacl.addEntry(principal, privileges, allow, restrictions);
>   
> acManager.setPolicy(jacl.getPath(), jacl);
> session.save();
> {noformat}
> then user can see all descendants of root:
> {noformat}
> /test
> /test/child
> /foo
> {noformat}
> which is not correct



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (JCR-3923) Repository root doesn't respect rep:glob

2018-02-01 Thread Konrad Windszus (JIRA)

[ 
https://issues.apache.org/jira/browse/JCR-3923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16348748#comment-16348748
 ] 

Konrad Windszus commented on JCR-3923:
--

We are running into the same issue with Oak (1.6.2). Is this a known issue?

> Repository root doesn't respect rep:glob
> 
>
> Key: JCR-3923
> URL: https://issues.apache.org/jira/browse/JCR-3923
> Project: Jackrabbit Content Repository
>  Issue Type: Bug
>Reporter: Kamil
>Priority: Major
>
> I have following node structure:
> {noformat}
> /test
> /test/child
> /foo
> {noformat}
> When I set Principal based privileges to some user as:
> {noformat}
> Map restrictions = new HashMap();
> ValueFactory vf = session.getValueFactory();
> restrictions.put("rep:nodePath", vf.createValue("/test", PropertyType.PATH));
> restrictions.put("rep:glob",  vf.createValue(""));
>   
> jacl.addEntry(principal, privileges, allow, restrictions);
>   
> acManager.setPolicy(jacl.getPath(), jacl);
> session.save();
> {noformat}
> where according to this documentation 
> http://jackrabbit.apache.org/api/2.2/org/apache/jackrabbit/core/security/authorization/GlobPattern.html
>  empty string means "matches /foo only", user can see only:
> {noformat}
> /test
> {noformat}
> without a child, which is correct. But when I set:
> {noformat}
> Map restrictions = new HashMap();
> ValueFactory vf = session.getValueFactory();
> restrictions.put("rep:nodePath", vf.createValue("/", PropertyType.PATH));
> restrictions.put("rep:glob",  vf.createValue(""));
>   
> jacl.addEntry(principal, privileges, allow, restrictions);
>   
> acManager.setPolicy(jacl.getPath(), jacl);
> session.save();
> {noformat}
> then user can see all descendants of root:
> {noformat}
> /test
> /test/child
> /foo
> {noformat}
> which is not correct



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


adaptTo() 2018: Tickets now available / Start Call for Papers

2018-02-01 Thread Stefan Seifert
Dear adaptTo() Community,

the sale of tickets for adaptTo() 2018 is open.

Get your Early-Bird-Ticket here: https://adapt.to/tickets

We also started the Call for Papers today! If you would like to be a speaker, 
please check out https://adapt.to/cfp 

Focusing on Apache Sling, Apache Felix and Apache Jackrabbit, the adaptTo() 
conference in Potsdam (near Berlin) is aimed at developers using some or all if 
this stack.

This year´s conference date is 10 - 12 September; latest information can be 
found on https://adapt.to

Kind regards on behalf of the adaptTo() Team,
Stefan




adaptTo() 2018: Tickets now available / Start Call for Papers

2018-02-01 Thread Stefan Seifert
Dear adaptTo() Community,

the sale of tickets for adaptTo() 2018 is open.

Get your Early-Bird-Ticket here: https://adapt.to/tickets

We also started the Call for Papers today! If you would like to be a speaker, 
please check out https://adapt.to/cfp 

Focusing on Apache Sling, Apache Felix and Apache Jackrabbit, the adaptTo() 
conference in Potsdam (near Berlin) is aimed at developers using some or all if 
this stack.

This year´s conference date is 10 - 12 September; latest information can be 
found on https://adapt.to

Kind regards on behalf of the adaptTo() Team,
Stefan




intent to backport OAK-4318 to branch 1.6

2018-02-01 Thread Tommaso Teofili
Hi all,

I'd like to backport upgrade to Solr 5.5.5 (OAK-4318) to branch 1.6.

Regards,
Tommaso


BUILD FAILURE: Jackrabbit Oak - Build # 1220 - Still Failing

2018-02-01 Thread Apache Jenkins Server
The Apache Jenkins build system has built Jackrabbit Oak (build #1220)

Status: Still Failing

Check console output at https://builds.apache.org/job/Jackrabbit%20Oak/1220/ to 
view the results.

Changes:
No changes
 

Test results:
All tests passed

Jackrabbit-trunk - Build # 2577 - Failure

2018-02-01 Thread Apache Jenkins Server
The Apache Jenkins build system has built Jackrabbit-trunk (build #2577)

Status: Failure

Check console output at https://builds.apache.org/job/Jackrabbit-trunk/2577/ to 
view the results.

[jira] [Commented] (JCR-4253) RepositoryConfig: add some handling for mkdir failure

2018-02-01 Thread Julian Reschke (JIRA)

[ 
https://issues.apache.org/jira/browse/JCR-4253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16348370#comment-16348370
 ] 

Julian Reschke commented on JCR-4253:
-

trunk: [r1822863|http://svn.apache.org/r1822863]


> RepositoryConfig: add some handling for mkdir failure
> -
>
> Key: JCR-4253
> URL: https://issues.apache.org/jira/browse/JCR-4253
> Project: Jackrabbit Content Repository
>  Issue Type: Improvement
>  Components: jackrabbit-core
>Reporter: Diego Schivo
>Assignee: Julian Reschke
>Priority: Minor
>  Labels: candidate_jcr_2_16
> Fix For: 2.18, 2.17.2
>
> Attachments: JCR-4253.diff, patch.txt
>
>
> Improve log readability in case for some reason (eg: file system permissions) 
> the repository and workspace root directory could not be created.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (JCR-4253) RepositoryConfig: add some handling for mkdir failure

2018-02-01 Thread Julian Reschke (JIRA)

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

Julian Reschke resolved JCR-4253.
-
   Resolution: Fixed
Fix Version/s: 2.17.2

> RepositoryConfig: add some handling for mkdir failure
> -
>
> Key: JCR-4253
> URL: https://issues.apache.org/jira/browse/JCR-4253
> Project: Jackrabbit Content Repository
>  Issue Type: Improvement
>  Components: jackrabbit-core
>Reporter: Diego Schivo
>Assignee: Julian Reschke
>Priority: Minor
>  Labels: candidate_jcr_2_16
> Fix For: 2.18, 2.17.2
>
> Attachments: JCR-4253.diff, patch.txt
>
>
> Improve log readability in case for some reason (eg: file system permissions) 
> the repository and workspace root directory could not be created.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (JCR-4253) RepositoryConfig: add some handling for mkdir failure

2018-02-01 Thread Julian Reschke (JIRA)

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

Julian Reschke updated JCR-4253:

Labels: candidate_jcr_2_16  (was: )

> RepositoryConfig: add some handling for mkdir failure
> -
>
> Key: JCR-4253
> URL: https://issues.apache.org/jira/browse/JCR-4253
> Project: Jackrabbit Content Repository
>  Issue Type: Improvement
>  Components: jackrabbit-core
>Reporter: Diego Schivo
>Assignee: Julian Reschke
>Priority: Minor
>  Labels: candidate_jcr_2_16
> Fix For: 2.18, 2.17.2
>
> Attachments: JCR-4253.diff, patch.txt
>
>
> Improve log readability in case for some reason (eg: file system permissions) 
> the repository and workspace root directory could not be created.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


BUILD FAILURE: Jackrabbit Oak - Build # 1219 - Still Failing

2018-02-01 Thread Apache Jenkins Server
The Apache Jenkins build system has built Jackrabbit Oak (build #1219)

Status: Still Failing

Check console output at https://builds.apache.org/job/Jackrabbit%20Oak/1219/ to 
view the results.

Changes:
No changes
 

Test results:
No tests ran.

[jira] [Updated] (JCR-4253) RepositoryConfig: add some handling for mkdir failure

2018-02-01 Thread Julian Reschke (JIRA)

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

Julian Reschke updated JCR-4253:

Attachment: JCR-4253.diff

> RepositoryConfig: add some handling for mkdir failure
> -
>
> Key: JCR-4253
> URL: https://issues.apache.org/jira/browse/JCR-4253
> Project: Jackrabbit Content Repository
>  Issue Type: Improvement
>  Components: jackrabbit-core
>Reporter: Diego Schivo
>Priority: Minor
> Fix For: 2.18
>
> Attachments: JCR-4253.diff, patch.txt
>
>
> Improve log readability in case for some reason (eg: file system permissions) 
> the repository and workspace root directory could not be created.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (JCR-4253) RepositoryConfig: add some handling for mkdir failure

2018-02-01 Thread Julian Reschke (JIRA)

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

Julian Reschke reassigned JCR-4253:
---

Assignee: Julian Reschke

> RepositoryConfig: add some handling for mkdir failure
> -
>
> Key: JCR-4253
> URL: https://issues.apache.org/jira/browse/JCR-4253
> Project: Jackrabbit Content Repository
>  Issue Type: Improvement
>  Components: jackrabbit-core
>Reporter: Diego Schivo
>Assignee: Julian Reschke
>Priority: Minor
> Fix For: 2.18
>
> Attachments: JCR-4253.diff, patch.txt
>
>
> Improve log readability in case for some reason (eg: file system permissions) 
> the repository and workspace root directory could not be created.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)