[jira] [Commented] (OAK-7417) Build Jackrabbit Oak #1379 failed

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-7417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16444674#comment-16444674
 ] 

Hudson commented on OAK-7417:
-

Previously failing build now is OK.
 Passed run: [Jackrabbit Oak 
#1387|https://builds.apache.org/job/Jackrabbit%20Oak/1387/] [console 
log|https://builds.apache.org/job/Jackrabbit%20Oak/1387/console]

> Build Jackrabbit Oak #1379 failed
> -
>
> Key: OAK-7417
> URL: https://issues.apache.org/jira/browse/OAK-7417
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: continuous integration
>Reporter: Hudson
>Priority: Major
>
> No description is provided
> The build Jackrabbit Oak #1379 has failed.
> First failed run: [Jackrabbit Oak 
> #1379|https://builds.apache.org/job/Jackrabbit%20Oak/1379/] [console 
> log|https://builds.apache.org/job/Jackrabbit%20Oak/1379/console]



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

[jira] [Commented] (OAK-7428) LdapIdentityProvider doesn't support creating external ids from custom attributes

[Manfred Baedke (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-7428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16444517#comment-16444517
 ] 

Manfred Baedke commented on OAK-7428:
-

Fixed in trunk: http://svn.apache.org/viewvc?view=revision=1829587

> LdapIdentityProvider doesn't support creating external ids from custom 
> attributes
> -
>
> Key: OAK-7428
> URL: https://issues.apache.org/jira/browse/OAK-7428
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: auth-ldap
>Reporter: Manfred Baedke
>Assignee: Manfred Baedke
>Priority: Major
>
> The LdapIdentityProvider always uses the value of an authorizables DN to 
> create external ids. But DNs may change over time, while the external id of 
> an authorizable have to be stable because the property rep:externalID is 
> protected.
> Therefore we need to add the option to use the value of a configurable LDAP 
> attribute to create external ids from it.



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

[jira] [Commented] (OAK-7417) Build Jackrabbit Oak #1379 failed

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-7417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1613#comment-1613
 ] 

Hudson commented on OAK-7417:
-

Previously failing build now is OK.
 Passed run: [Jackrabbit Oak 
#1386|https://builds.apache.org/job/Jackrabbit%20Oak/1386/] [console 
log|https://builds.apache.org/job/Jackrabbit%20Oak/1386/console]

> Build Jackrabbit Oak #1379 failed
> -
>
> Key: OAK-7417
> URL: https://issues.apache.org/jira/browse/OAK-7417
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: continuous integration
>Reporter: Hudson
>Priority: Major
>
> No description is provided
> The build Jackrabbit Oak #1379 has failed.
> First failed run: [Jackrabbit Oak 
> #1379|https://builds.apache.org/job/Jackrabbit%20Oak/1379/] [console 
> log|https://builds.apache.org/job/Jackrabbit%20Oak/1379/console]



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

[jira] [Created] (OAK-7428) LdapIdentityProvider doesn't support creating external ids from custom attributes

[Manfred Baedke (JIRA)]

Manfred Baedke created OAK-7428:
---

 Summary: LdapIdentityProvider doesn't support creating external 
ids from custom attributes
 Key: OAK-7428
 URL: https://issues.apache.org/jira/browse/OAK-7428
 Project: Jackrabbit Oak
  Issue Type: Bug
  Components: auth-ldap
Reporter: Manfred Baedke
Assignee: Manfred Baedke


The LdapIdentityProvider always uses the value of an authorizables DN to create 
external ids. But DNs may change over time, while the external id of an 
authorizable have to be stable because the property rep:externalID is protected.

Therefore we need to add the option to use the value of a configurable LDAP 
attribute to create external ids from it.



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

[jira] [Created] (OAK-7427) Inconsistent method name

[KuiLIU (JIRA)]

KuiLIU created OAK-7427:
---

 Summary: Inconsistent method name
 Key: OAK-7427
 URL: https://issues.apache.org/jira/browse/OAK-7427
 Project: Jackrabbit Oak
  Issue Type: Improvement
Reporter: KuiLIU


The following method is named as "serialize", but the method seems like to 
format the data.
The method name "format" should be more clear than "serialize".

{code:java}
private static String serialize(String segmentId, Iterable 
references) {
return segmentId + ":" + Joiner.on(",").join(references);
}
{code}




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

[jira] [Commented] (OAK-7417) Build Jackrabbit Oak #1379 failed

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-7417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16444276#comment-16444276
 ] 

Hudson commented on OAK-7417:
-

Previously failing build now is OK.
 Passed run: [Jackrabbit Oak 
#1385|https://builds.apache.org/job/Jackrabbit%20Oak/1385/] [console 
log|https://builds.apache.org/job/Jackrabbit%20Oak/1385/console]

> Build Jackrabbit Oak #1379 failed
> -
>
> Key: OAK-7417
> URL: https://issues.apache.org/jira/browse/OAK-7417
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: continuous integration
>Reporter: Hudson
>Priority: Major
>
> No description is provided
> The build Jackrabbit Oak #1379 has failed.
> First failed run: [Jackrabbit Oak 
> #1379|https://builds.apache.org/job/Jackrabbit%20Oak/1379/] [console 
> log|https://builds.apache.org/job/Jackrabbit%20Oak/1379/console]



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

[jira] [Commented] (OAK-7426) RDB*Store: update Tomcat JDBC pool dependency to 8.5.30

[Julian Reschke (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-7426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16444271#comment-16444271
 ] 

Julian Reschke commented on OAK-7426:
-

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


> RDB*Store: update Tomcat JDBC pool dependency to 8.5.30
> ---
>
> Key: OAK-7426
> URL: https://issues.apache.org/jira/browse/OAK-7426
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
>  Labels: candidate_oak_1_8
> Fix For: 1.9.0, 1.10
>
>




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

[jira] [Resolved] (OAK-7426) RDB*Store: update Tomcat JDBC pool dependency to 8.5.30

[Julian Reschke (JIRA)]

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

Julian Reschke resolved OAK-7426.
-
Resolution: Fixed

> RDB*Store: update Tomcat JDBC pool dependency to 8.5.30
> ---
>
> Key: OAK-7426
> URL: https://issues.apache.org/jira/browse/OAK-7426
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
>  Labels: candidate_oak_1_8
> Fix For: 1.9.0, 1.10
>
>




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

[jira] [Updated] (OAK-7426) RDB*Store: update Tomcat JDBC pool dependency to 8.5.30

[Julian Reschke (JIRA)]

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

Julian Reschke updated OAK-7426:

Fix Version/s: 1.9.0

> RDB*Store: update Tomcat JDBC pool dependency to 8.5.30
> ---
>
> Key: OAK-7426
> URL: https://issues.apache.org/jira/browse/OAK-7426
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
>  Labels: candidate_oak_1_8
> Fix For: 1.9.0, 1.10
>
>




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

[jira] [Updated] (OAK-7426) RDB*Store: update Tomcat JDBC pool dependency to 8.5.30

[Julian Reschke (JIRA)]

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

Julian Reschke updated OAK-7426:

Labels: candidate_oak_1_8  (was: )

> RDB*Store: update Tomcat JDBC pool dependency to 8.5.30
> ---
>
> Key: OAK-7426
> URL: https://issues.apache.org/jira/browse/OAK-7426
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
>  Labels: candidate_oak_1_8
> Fix For: 1.9.0, 1.10
>
>




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

[jira] [Created] (OAK-7426) RDB*Store: update Tomcat JDBC pool dependency to 8.5.30

[Julian Reschke (JIRA)]

Julian Reschke created OAK-7426:
---

 Summary: RDB*Store: update Tomcat JDBC pool dependency to 8.5.30
 Key: OAK-7426
 URL: https://issues.apache.org/jira/browse/OAK-7426
 Project: Jackrabbit Oak
  Issue Type: Task
  Components: parent
Reporter: Julian Reschke
Assignee: Julian Reschke
 Fix For: 1.10






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

[jira] [Resolved] (OAK-7424) SecurityProviderBuilder expects CompositeConfiguration

[angela (JIRA)]

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

angela resolved OAK-7424.
-
   Resolution: Fixed
Fix Version/s: 1.10
   1.9.0

> SecurityProviderBuilder expects CompositeConfiguration
> --
>
> Key: OAK-7424
> URL: https://issues.apache.org/jira/browse/OAK-7424
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: core, security
>Reporter: angela
>Assignee: angela
>Priority: Minor
> Fix For: 1.9.0, 1.10
>
> Attachments: OAK-7424.patch
>
>
> [~stillalex], as discussed there is currently no way to init the 
> SecurityProviderBuilder with non-composite configurations despite the fact 
> that the {{SecurityProvider}} built from the various modules doesn't require 
> any configuration to be a composite.



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

[jira] [Commented] (OAK-7424) SecurityProviderBuilder expects CompositeConfiguration

[angela (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-7424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16444173#comment-16444173
 ] 

angela commented on OAK-7424:
-

[~stillalex], added more flavor to the pasta at revision 1829556.


> SecurityProviderBuilder expects CompositeConfiguration
> --
>
> Key: OAK-7424
> URL: https://issues.apache.org/jira/browse/OAK-7424
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: core, security
>Reporter: angela
>Assignee: angela
>Priority: Minor
> Attachments: OAK-7424.patch
>
>
> [~stillalex], as discussed there is currently no way to init the 
> SecurityProviderBuilder with non-composite configurations despite the fact 
> that the {{SecurityProvider}} built from the various modules doesn't require 
> any configuration to be a composite.



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

[jira] [Commented] (OAK-7424) SecurityProviderBuilder expects CompositeConfiguration

[Alex Deparvu (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-7424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16444126#comment-16444126
 ] 

Alex Deparvu commented on OAK-7424:
---

ugh, copy pasta code, you are right the code should work with non-composites as 
well.
patch looks good! +1

> SecurityProviderBuilder expects CompositeConfiguration
> --
>
> Key: OAK-7424
> URL: https://issues.apache.org/jira/browse/OAK-7424
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: core, security
>Reporter: angela
>Assignee: angela
>Priority: Minor
> Attachments: OAK-7424.patch
>
>
> [~stillalex], as discussed there is currently no way to init the 
> SecurityProviderBuilder with non-composite configurations despite the fact 
> that the {{SecurityProvider}} built from the various modules doesn't require 
> any configuration to be a composite.



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

[jira] [Commented] (OAK-7424) SecurityProviderBuilder expects CompositeConfiguration

[angela (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-7424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16444111#comment-16444111
 ] 

angela commented on OAK-7424:
-

[~stillalex], proposed patch attached

> SecurityProviderBuilder expects CompositeConfiguration
> --
>
> Key: OAK-7424
> URL: https://issues.apache.org/jira/browse/OAK-7424
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: core, security
>Reporter: angela
>Assignee: angela
>Priority: Minor
> Attachments: OAK-7424.patch
>
>
> [~stillalex], as discussed there is currently no way to init the 
> SecurityProviderBuilder with non-composite configurations despite the fact 
> that the {{SecurityProvider}} built from the various modules doesn't require 
> any configuration to be a composite.



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

[jira] [Updated] (OAK-7424) SecurityProviderBuilder expects CompositeConfiguration

[angela (JIRA)]

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

angela updated OAK-7424:

Attachment: OAK-7424.patch

> SecurityProviderBuilder expects CompositeConfiguration
> --
>
> Key: OAK-7424
> URL: https://issues.apache.org/jira/browse/OAK-7424
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: core, security
>Reporter: angela
>Assignee: angela
>Priority: Minor
> Attachments: OAK-7424.patch
>
>
> [~stillalex], as discussed there is currently no way to init the 
> SecurityProviderBuilder with non-composite configurations despite the fact 
> that the {{SecurityProvider}} built from the various modules doesn't require 
> any configuration to be a composite.



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

[jira] [Commented] (OAK-7417) Build Jackrabbit Oak #1379 failed

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-7417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16444105#comment-16444105
 ] 

Hudson commented on OAK-7417:
-

Previously failing build now is OK.
 Passed run: [Jackrabbit Oak 
#1384|https://builds.apache.org/job/Jackrabbit%20Oak/1384/] [console 
log|https://builds.apache.org/job/Jackrabbit%20Oak/1384/console]

> Build Jackrabbit Oak #1379 failed
> -
>
> Key: OAK-7417
> URL: https://issues.apache.org/jira/browse/OAK-7417
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: continuous integration
>Reporter: Hudson
>Priority: Major
>
> No description is provided
> The build Jackrabbit Oak #1379 has failed.
> First failed run: [Jackrabbit Oak 
> #1379|https://builds.apache.org/job/Jackrabbit%20Oak/1379/] [console 
> log|https://builds.apache.org/job/Jackrabbit%20Oak/1379/console]



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

[jira] [Comment Edited] (OAK-7163) Upgrade commons-io dependency to 2.6

[Julian Reschke (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-7163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327127#comment-16327127
 ] 

Julian Reschke edited comment on OAK-7163 at 4/19/18 2:16 PM:
--

trunk: [r1829546|http://svn.apache.org/r1829546] 
[r1821372|http://svn.apache.org/r1821372] 
[r1821245|http://svn.apache.org/r1821245]



was (Author: reschke):
trunk: [r1821372|http://svn.apache.org/r1821372] 
[r1821245|http://svn.apache.org/r1821245]


> Upgrade commons-io dependency to 2.6
> 
>
> Key: OAK-7163
> URL: https://issues.apache.org/jira/browse/OAK-7163
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
>  Labels: candidate_oak_1_8
> Fix For: 1.9.0, 1.10
>
>




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

[jira] [Resolved] (OAK-7163) Upgrade commons-io dependency to 2.6

[Julian Reschke (JIRA)]

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

Julian Reschke resolved OAK-7163.
-
   Resolution: Fixed
Fix Version/s: 1.9.0

> Upgrade commons-io dependency to 2.6
> 
>
> Key: OAK-7163
> URL: https://issues.apache.org/jira/browse/OAK-7163
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
>  Labels: candidate_oak_1_8
> Fix For: 1.9.0, 1.10
>
>




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

[jira] [Created] (OAK-7425) Add discovery mechanism for tooling implementations

[Francesco Mari (JIRA)]

Francesco Mari created OAK-7425:
---

 Summary: Add discovery mechanism for tooling implementations
 Key: OAK-7425
 URL: https://issues.apache.org/jira/browse/OAK-7425
 Project: Jackrabbit Oak
  Issue Type: Improvement
  Components: segment-tar
Reporter: Francesco Mari
Assignee: Francesco Mari
 Fix For: 1.10
 Attachments: 001.patch

This issue proposes an idea for discovering implementations of tooling for the 
Segment Store. Developing a tool for the Segment Store should include the 
following step.

* The tool compiles against the {{NodeStore}} API and the API exposed through 
the oak-segment-tar-tool-api. In particular, the tool uses the 
{{ToolingSupportFactory}} and related interfaces to instantiate a NodeStore 
and, optionally, a {{NodeState}} for the proc tree.
* The tool runs with an implementation-dependent uber-jar in the classpath. The 
uber-jar includes the {{ToolingSupportFactory}} API, its implementation, and 
every other class required for the implementation to work. No other JARs is 
required to use the {{ToolingSupportFactory}} API. The tool uses the Java's 
{{ServiceLoader}} to instantiate an implementation of 
{{ToolingSupportFactory}}. The uber-jar is the {{oak-segment-tar-tool}} module.

The patch falls short of fully implementing the use case because 
{{oak-segment-tar-tool-api}} is not versioned independently from Oak. This 
can't happen at the moment because {{oak-store-spi}} and its dependencies are 
not independently versioned either. The workflow described above could still 
work, but only because the {{NodeStore}} and {{NodeState}} API are quite 
stable. A cleaner solution to dependency management is required in the long run.





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

[jira] [Commented] (OAK-7401) Changes kept in memory when update limit is hit in commit hook

[Marcel Reutegger (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-7401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16444060#comment-16444060
 ] 

Marcel Reutegger commented on OAK-7401:
---

Created a PR with proposed fix: https://github.com/apache/jackrabbit-oak/pull/84

> Changes kept in memory when update limit is hit in commit hook
> --
>
> Key: OAK-7401
> URL: https://issues.apache.org/jira/browse/OAK-7401
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: documentmk
>Affects Versions: 1.0, 1.2, 1.4, 1.6.0, 1.8.0
>Reporter: Marcel Reutegger
>Assignee: Marcel Reutegger
>Priority: Major
> Fix For: 1.10
>
>
> In some cases no persisted branch is created by the DocumentNodeStore when 
> the number of changes hit the update limit. This happens when the current 
> branch state is in-memory and the commit hook contributes changes that reach 
> the update limit. The implementation keeps those changes in memory, which may 
> lead to a commit way bigger than specified by the update limit.



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

[jira] [Created] (OAK-7424) SecurityProviderBuilder expects CompositeConfiguration

[angela (JIRA)]

angela created OAK-7424:
---

 Summary: SecurityProviderBuilder expects CompositeConfiguration
 Key: OAK-7424
 URL: https://issues.apache.org/jira/browse/OAK-7424
 Project: Jackrabbit Oak
  Issue Type: Improvement
  Components: core, security
Reporter: angela
Assignee: angela


[~stillalex], as discussed there is currently no way to init the 
SecurityProviderBuilder with non-composite configurations despite the fact that 
the {{SecurityProvider}} built from the various modules doesn't require any 
configuration to be a composite.



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

[jira] [Resolved] (OAK-7160) Update commons-codec dependency to 1.11

[Julian Reschke (JIRA)]

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

Julian Reschke resolved OAK-7160.
-
   Resolution: Fixed
Fix Version/s: 1.9.0

> Update commons-codec dependency to 1.11
> ---
>
> Key: OAK-7160
> URL: https://issues.apache.org/jira/browse/OAK-7160
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
>  Labels: candidate_oak_1_8
> Fix For: 1.9.0, 1.10
>
>




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

[jira] [Comment Edited] (OAK-7160) Update commons-codec dependency to 1.11

[Julian Reschke (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-7160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16326864#comment-16326864
 ] 

Julian Reschke edited comment on OAK-7160 at 4/19/18 1:00 PM:
--

trunk: [r1829534|http://svn.apache.org/r1829534] 
[r1821360|http://svn.apache.org/r1821360] 
[r1821221|http://svn.apache.org/r1821221]



was (Author: reschke):
trunk: [r1821360|http://svn.apache.org/r1821360] 
[r1821221|http://svn.apache.org/r1821221]


> Update commons-codec dependency to 1.11
> ---
>
> Key: OAK-7160
> URL: https://issues.apache.org/jira/browse/OAK-7160
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
>  Labels: candidate_oak_1_8
> Fix For: 1.9.0, 1.10
>
>




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

[jira] [Updated] (OAK-7160) Update commons-codec dependency to 1.11

[Julian Reschke (JIRA)]

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

Julian Reschke updated OAK-7160:

Summary: Update commons-codec dependency to 1.11  (was: Update 
commons-codec dependency)

> Update commons-codec dependency to 1.11
> ---
>
> Key: OAK-7160
> URL: https://issues.apache.org/jira/browse/OAK-7160
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
>  Labels: candidate_oak_1_8
> Fix For: 1.9.0, 1.10
>
>




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

[jira] [Created] (OAK-7423) Document the proc tree

[Francesco Mari (JIRA)]

Francesco Mari created OAK-7423:
---

 Summary: Document the proc tree
 Key: OAK-7423
 URL: https://issues.apache.org/jira/browse/OAK-7423
 Project: Jackrabbit Oak
  Issue Type: Documentation
  Components: segment-tar
Reporter: Francesco Mari
Assignee: Francesco Mari
 Fix For: 1.10


The proc tree, contributed in OAK-7416, lacks Javadoc and high-level 
documentation. In particular, the exposed content structure should be described 
in greater detail.



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

[jira] [Commented] (OAK-7417) Build Jackrabbit Oak #1379 failed

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-7417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443991#comment-16443991
 ] 

Hudson commented on OAK-7417:
-

Previously failing build now is OK.
 Passed run: [Jackrabbit Oak 
#1383|https://builds.apache.org/job/Jackrabbit%20Oak/1383/] [console 
log|https://builds.apache.org/job/Jackrabbit%20Oak/1383/console]

> Build Jackrabbit Oak #1379 failed
> -
>
> Key: OAK-7417
> URL: https://issues.apache.org/jira/browse/OAK-7417
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: continuous integration
>Reporter: Hudson
>Priority: Major
>
> No description is provided
> The build Jackrabbit Oak #1379 has failed.
> First failed run: [Jackrabbit Oak 
> #1379|https://builds.apache.org/job/Jackrabbit%20Oak/1379/] [console 
> log|https://builds.apache.org/job/Jackrabbit%20Oak/1379/console]



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

[jira] [Resolved] (OAK-7416) Contribute a 'proc' subtree for the Segment Node Store

[Francesco Mari (JIRA)]

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

Francesco Mari resolved OAK-7416.
-
   Resolution: Fixed
Fix Version/s: 1.9.0

Fixed at r1829528.

> Contribute a 'proc' subtree for the Segment Node Store
> --
>
> Key: OAK-7416
> URL: https://issues.apache.org/jira/browse/OAK-7416
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: segment-tar
>Reporter: Francesco Mari
>Assignee: Francesco Mari
>Priority: Major
>  Labels: tooling
> Fix For: 1.9.0, 1.10
>
>
> With guidance from [~mduerig], I recently developed a way to expose Segment 
> Node Store's internal information through the NodeState API. 
> The concept is similar in spirit to the proc file system in Linux: the proc 
> subtree exposes internal information in a straightforward manner, enabling 
> consumers to rely on a well-understood API to access the data. This proc 
> subtree shelters tooling from variations of the internal APIs of the Segment 
> Store. As long as the data exported through the proc subtree is stable, the 
> same tools are going to work across different versions of the Segment Store 
> with minimal to no modifications.
> The proc subtree has been developed in [this branch on 
> GitHub|https://github.com/francescomari/jackrabbit-oak/tree/proc]. I created 
> this issue in order to review the work done so far, and to track the 
> contribution of the proc subtree in Oak.



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

[jira] [Commented] (OAK-7422) Update jackson dependencies to 2.9.5

[Julian Reschke (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-7422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443922#comment-16443922
 ] 

Julian Reschke commented on OAK-7422:
-

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


> Update jackson dependencies to 2.9.5
> 
>
> Key: OAK-7422
> URL: https://issues.apache.org/jira/browse/OAK-7422
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: oak-http, solr
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Major
>  Labels: candidate_oak_1_8
> Fix For: 1.9.0, 1.10
>
>
> See 



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

[jira] [Resolved] (OAK-7422) Update jackson dependencies to 2.9.5

[Julian Reschke (JIRA)]

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

Julian Reschke resolved OAK-7422.
-
Resolution: Fixed

> Update jackson dependencies to 2.9.5
> 
>
> Key: OAK-7422
> URL: https://issues.apache.org/jira/browse/OAK-7422
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: oak-http, solr
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Major
>  Labels: candidate_oak_1_8
> Fix For: 1.9.0, 1.10
>
>
> See 



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

[jira] [Updated] (OAK-7422) Update jackson dependencies to 2.9.5

[Julian Reschke (JIRA)]

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

Julian Reschke updated OAK-7422:

Labels: candidate_oak_1_8  (was: )

> Update jackson dependencies to 2.9.5
> 
>
> Key: OAK-7422
> URL: https://issues.apache.org/jira/browse/OAK-7422
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: oak-http, solr
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Major
>  Labels: candidate_oak_1_8
> Fix For: 1.9.0, 1.10
>
>
> See 



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

[jira] [Updated] (OAK-7422) Update jackson dependencies to 2.9.5

[Julian Reschke (JIRA)]

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

Julian Reschke updated OAK-7422:

Summary: Update jackson dependencies to 2.9.5  (was: Update jackson 
dependency)

> Update jackson dependencies to 2.9.5
> 
>
> Key: OAK-7422
> URL: https://issues.apache.org/jira/browse/OAK-7422
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: oak-http, solr
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Major
>  Labels: candidate_oak_1_8
> Fix For: 1.9.0, 1.10
>
>
> See 



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

[jira] [Commented] (OAK-7417) Build Jackrabbit Oak #1379 failed

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-7417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443885#comment-16443885
 ] 

Hudson commented on OAK-7417:
-

Previously failing build now is OK.
 Passed run: [Jackrabbit Oak 
#1382|https://builds.apache.org/job/Jackrabbit%20Oak/1382/] [console 
log|https://builds.apache.org/job/Jackrabbit%20Oak/1382/console]

> Build Jackrabbit Oak #1379 failed
> -
>
> Key: OAK-7417
> URL: https://issues.apache.org/jira/browse/OAK-7417
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: continuous integration
>Reporter: Hudson
>Priority: Major
>
> No description is provided
> The build Jackrabbit Oak #1379 has failed.
> First failed run: [Jackrabbit Oak 
> #1379|https://builds.apache.org/job/Jackrabbit%20Oak/1379/] [console 
> log|https://builds.apache.org/job/Jackrabbit%20Oak/1379/console]



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

[jira] [Comment Edited] (OAK-7297) New fixture for the Azure Segment Store

[JIRA]

[ 
https://issues.apache.org/jira/browse/OAK-7297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16406126#comment-16406126
 ] 

Tomek Rękawek edited comment on OAK-7297 at 4/19/18 10:59 AM:
--

Merged to trunk [r1827293|https://svn.apache.org/r1827293], 
[r1829523|https://svn.apache.org/r1829523], 
[r1829525|https://svn.apache.org/r1829525]


was (Author: tomek.rekawek):
Merged to trunk [r1827293|https://svn.apache.org/r1827293].

> New fixture for the Azure Segment Store
> ---
>
> Key: OAK-7297
> URL: https://issues.apache.org/jira/browse/OAK-7297
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: benchmarks, it
>Reporter: Tomek Rękawek
>Assignee: Tomek Rękawek
>Priority: Major
> Fix For: 1.9.0, 1.10
>
> Attachments: OAK-7297.patch
>
>
> We should add a new {{SEGMENT_AZURE}} fixture, so it's possible to run the 
> integrationt tests for the [Azure Segment Store|OAK-6922]. By default it 
> should connect to a local Azure Storage emulator:
> * https://docs.microsoft.com/en-us/azure/storage/common/storage-use-emulator
> * https://github.com/arafato/azurite
> If the {{oak.segment.azure.connection}} system property is defined, then it 
> should try to connect to the specified [connection 
> string|https://docs.microsoft.com/en-us/azure/storage/common/storage-configure-connection-string].



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

[jira] [Created] (OAK-7422) Update jackson dependency

[Julian Reschke (JIRA)]

Julian Reschke created OAK-7422:
---

 Summary: Update jackson dependency
 Key: OAK-7422
 URL: https://issues.apache.org/jira/browse/OAK-7422
 Project: Jackrabbit Oak
  Issue Type: Task
  Components: oak-http
Reporter: Julian Reschke
Assignee: Julian Reschke
 Fix For: 1.9.0, 1.10


See 



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

[jira] [Updated] (OAK-7422) Update jackson dependency

[Julian Reschke (JIRA)]

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

Julian Reschke updated OAK-7422:

Component/s: solr

> Update jackson dependency
> -
>
> Key: OAK-7422
> URL: https://issues.apache.org/jira/browse/OAK-7422
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: oak-http, solr
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Major
> Fix For: 1.9.0, 1.10
>
>
> See 



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

[jira] [Commented] (OAK-7148) Document excerpt support (specially excerpts for properties)

[Thomas Mueller (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-7148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443789#comment-16443789
 ] 

Thomas Mueller commented on OAK-7148:
-

Documented in: 
http://jackrabbit.apache.org/oak/docs/query/query-engine.html#Excerpts_and_Highlighting
http://jackrabbit.apache.org/oak/docs/query/grammar-xpath.html#column


> Document excerpt support (specially excerpts for properties)
> 
>
> Key: OAK-7148
> URL: https://issues.apache.org/jira/browse/OAK-7148
> Project: Jackrabbit Oak
>  Issue Type: Documentation
>  Components: query
>Reporter: Thomas Mueller
>Assignee: Thomas Mueller
>Priority: Major
> Fix For: 1.9.0, 1.10
>
>
> Currently, it's possible to get excerpts for properties. For this case, our 
> own "simple excerpt" mechanism is used (which has many limitations).
> We need to document this feature and the limitations.



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

[jira] [Resolved] (OAK-7148) Document excerpt support (specially excerpts for properties)

[Thomas Mueller (JIRA)]

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

Thomas Mueller resolved OAK-7148.
-
Resolution: Fixed

> Document excerpt support (specially excerpts for properties)
> 
>
> Key: OAK-7148
> URL: https://issues.apache.org/jira/browse/OAK-7148
> Project: Jackrabbit Oak
>  Issue Type: Documentation
>  Components: query
>Reporter: Thomas Mueller
>Assignee: Thomas Mueller
>Priority: Major
> Fix For: 1.9.0, 1.10
>
>
> Currently, it's possible to get excerpts for properties. For this case, our 
> own "simple excerpt" mechanism is used (which has many limitations).
> We need to document this feature and the limitations.



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

[jira] [Resolved] (OAK-7418) SecurityProviderBuilder ignores configuration option authorizationCompositionType

[angela (JIRA)]

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

angela resolved OAK-7418.
-
   Resolution: Fixed
Fix Version/s: 1.10
   1.9.0

fixed at revision 1829520 with minor modification to the patch: the default 
constructor also needs to set an empty configuration in order to avoid npe.


> SecurityProviderBuilder ignores configuration option 
> authorizationCompositionType
> -
>
> Key: OAK-7418
> URL: https://issues.apache.org/jira/browse/OAK-7418
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: core, security
>Reporter: angela
>Assignee: angela
>Priority: Minor
> Fix For: 1.9.0, 1.10
>
> Attachments: OAK-7418.patch
>
>
> For test purpose it would be good to be able to make use of the 
> {{authorizationCompositionType}} configuration option but it seems that 
> {{SecurityProviderBuilder}} ignores it.
> [~stillalex], fyi.



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

[jira] [Commented] (OAK-7151) Support indexed based excerpts on properties

[Thomas Mueller (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-7151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443765#comment-16443765
 ] 

Thomas Mueller commented on OAK-7151:
-

http://svn.apache.org/r1829519 (trunk) - fix and test cases for the above 
problem with "rep:excerpt()"

> Support indexed based excerpts on properties
> 
>
> Key: OAK-7151
> URL: https://issues.apache.org/jira/browse/OAK-7151
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: lucene
>Reporter: Vikas Saurabh
>Assignee: Vikas Saurabh
>Priority: Major
> Fix For: 1.10
>
> Attachments: OAK-7151.patch, OAK-7151.xpath-new-syntax.patch, 
> OAK-7151.xpath.patch
>
>
> As discovered in OAK-4401 we fallback to {{SimpleExcerptProvider}} when 
> requesting excerpts for properties.
> The issue as highlighted in [~teofili]'s comment \[0] is that we at time of 
> query we don't have information about which all columns/fields would be 
> required for excerpts.
> A possible approach is that the query specified explicitly which columns 
> would be required in facets (of course, node level excerpt would still be 
> supported). This issue is to track that improvement.
> Note: this is *not* a substitute for OAK-4401 which is about doing saner 
> highlighting when {{SimpleExcerptProvider}} comes into play e.g. despite this 
> issue excerpt for non-stored fields (properties which aren't configured with 
> {{useInExcerpt}} in the index definition}, we'd need to fallback to 
> {{SimpleExcerptProvider}}.
> /[~tmueller]
> \[0]: 
> https://issues.apache.org/jira/browse/OAK-4401?focusedCommentId=15299857=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15299857



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

[jira] [Commented] (OAK-7182) Make it possible to update Guava

[Robert Munteanu (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-7182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443757#comment-16443757
 ] 

Robert Munteanu commented on OAK-7182:
--

With {{Conditional-Package}} external callers would no longer be able to access 
those APIs. And I guess it's bundling most of Guava, so that explains the size 
increase.

> Make it possible to update Guava
> 
>
> Key: OAK-7182
> URL: https://issues.apache.org/jira/browse/OAK-7182
> Project: Jackrabbit Oak
>  Issue Type: Wish
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
> Attachments: OAK-7182-guava-21.diff, guava.diff
>
>
> We currently rely on Guava 15, and this affects all users of Oak because they 
> essentially need to use the same version.
> This is an overall issue to investigate what would need to be done in Oak in 
> order to make updates possible.



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

[jira] [Commented] (OAK-7151) Support indexed based excerpts on properties

[Thomas Mueller (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-7151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443740#comment-16443740
 ] 

Thomas Mueller commented on OAK-7151:
-

Working on a patch for the above problem, plus some test cases for this problem.

> Support indexed based excerpts on properties
> 
>
> Key: OAK-7151
> URL: https://issues.apache.org/jira/browse/OAK-7151
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: lucene
>Reporter: Vikas Saurabh
>Assignee: Vikas Saurabh
>Priority: Major
> Fix For: 1.10
>
> Attachments: OAK-7151.patch, OAK-7151.xpath-new-syntax.patch, 
> OAK-7151.xpath.patch
>
>
> As discovered in OAK-4401 we fallback to {{SimpleExcerptProvider}} when 
> requesting excerpts for properties.
> The issue as highlighted in [~teofili]'s comment \[0] is that we at time of 
> query we don't have information about which all columns/fields would be 
> required for excerpts.
> A possible approach is that the query specified explicitly which columns 
> would be required in facets (of course, node level excerpt would still be 
> supported). This issue is to track that improvement.
> Note: this is *not* a substitute for OAK-4401 which is about doing saner 
> highlighting when {{SimpleExcerptProvider}} comes into play e.g. despite this 
> issue excerpt for non-stored fields (properties which aren't configured with 
> {{useInExcerpt}} in the index definition}, we'd need to fallback to 
> {{SimpleExcerptProvider}}.
> /[~tmueller]
> \[0]: 
> https://issues.apache.org/jira/browse/OAK-4401?focusedCommentId=15299857=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15299857



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

[jira] [Commented] (OAK-7151) Support indexed based excerpts on properties

[Thomas Mueller (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-7151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443738#comment-16443738
 ] 

Thomas Mueller commented on OAK-7151:
-

This no longer works:

{noformat}
/jcr:root/tmp/test//element(*, nt:base)[jcr:contains(., 
'hello')]/(rep:excerpt())
{noformat}


> Support indexed based excerpts on properties
> 
>
> Key: OAK-7151
> URL: https://issues.apache.org/jira/browse/OAK-7151
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: lucene
>Reporter: Vikas Saurabh
>Assignee: Vikas Saurabh
>Priority: Major
> Fix For: 1.10
>
> Attachments: OAK-7151.patch, OAK-7151.xpath-new-syntax.patch, 
> OAK-7151.xpath.patch
>
>
> As discovered in OAK-4401 we fallback to {{SimpleExcerptProvider}} when 
> requesting excerpts for properties.
> The issue as highlighted in [~teofili]'s comment \[0] is that we at time of 
> query we don't have information about which all columns/fields would be 
> required for excerpts.
> A possible approach is that the query specified explicitly which columns 
> would be required in facets (of course, node level excerpt would still be 
> supported). This issue is to track that improvement.
> Note: this is *not* a substitute for OAK-4401 which is about doing saner 
> highlighting when {{SimpleExcerptProvider}} comes into play e.g. despite this 
> issue excerpt for non-stored fields (properties which aren't configured with 
> {{useInExcerpt}} in the index definition}, we'd need to fallback to 
> {{SimpleExcerptProvider}}.
> /[~tmueller]
> \[0]: 
> https://issues.apache.org/jira/browse/OAK-4401?focusedCommentId=15299857=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15299857



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

[jira] [Commented] (OAK-6209) The benchmark runner should produce machine-friendly output

[Maksim Kviatkouski (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-6209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443614#comment-16443614
 ] 

Maksim Kviatkouski commented on OAK-6209:
-

[~frm], I think there is no need now in {{AbstractTest}} implementing 
{{CSVResultGenerator}}. I'll have refactoring and unit tests done in next few 
days.

> The benchmark runner should produce machine-friendly output
> ---
>
> Key: OAK-6209
> URL: https://issues.apache.org/jira/browse/OAK-6209
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: benchmarks
>Reporter: Francesco Mari
>Assignee: Francesco Mari
>Priority: Major
> Attachments: oak-6209.patch, oak-6209.patch, 
> sample-machine-readable-output.txt
>
>
> The benchmark runner currently produce output in the following format.
> {noformat}
> Apache Jackrabbit Oak 1.8-SNAPSHOT
> # LoginTestC min 10% 50% 90% max  
>  N 
> Oak-Segment-Tar1 472 494 522 552 631  
>115
> # LoginLogoutTest  C min 10% 50% 90% max  
>  N 
> Oak-Segment-Tar1 472 479 513 543 568  
>118
> {noformat}
> While this format is well formatted and easy to read, it's a pain to process 
> with standard command line utilities. The benchmark runner should give the 
> possibility to produce machine-friendly output, like the following.
> {noformat}
> LoginTest,Oak-Segment-Tar,1,472,494,522,552,631,115
> LoginLogoutTest,Oak-Segment-Tar,1,472,479,513,543,568,118
> {noformat}



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