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

[Apache Jenkins Server]

The Apache Jenkins build system has built Jackrabbit Oak (build #450)

Status: Still Failing

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

Changes:
[frm] OAK-6325 - Turn CacheWeightsTest into a command-line utility

 

Test results:
1 tests failed.
FAILED:  
org.apache.jackrabbit.oak.segment.CompactionAndCleanupIT.testCancelCompaction

Error Message:
null

Stack Trace:
java.lang.NullPointerException

BUILD FAILURE: Jackrabbit Oak - Build # 449 - Failure

[Apache Jenkins Server]

The Apache Jenkins build system has built Jackrabbit Oak (build #449)

Status: Failure

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

Changes:
[frm] OAK-6378 - Move the SegmentWriter API to its own interface

 

Test results:
1 tests failed.
FAILED:  
org.apache.jackrabbit.oak.segment.CompactionAndCleanupIT.testCancelCompaction

Error Message:
null

Stack Trace:
java.lang.NullPointerException

[jira] [Created] (JCR-4153) Switch to OSGi annotations

[Julian Reschke (JIRA)]

Julian Reschke created JCR-4153:
---

 Summary: Switch to OSGi annotations
 Key: JCR-4153
 URL: https://issues.apache.org/jira/browse/JCR-4153
 Project: Jackrabbit Content Repository
  Issue Type: Task
Reporter: Julian Reschke






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

[jira] [Updated] (JCR-4153) Switch to OSGi annotations

[Julian Reschke (JIRA)]

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

Julian Reschke updated JCR-4153:

Description: 
The felix scr annotations are deprecated and it is time to switch to the OSGi 
R6 annotations.


> Switch to OSGi annotations
> --
>
> Key: JCR-4153
> URL: https://issues.apache.org/jira/browse/JCR-4153
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>Reporter: Julian Reschke
>
> The felix scr annotations are deprecated and it is time to switch to the OSGi 
> R6 annotations.



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

native clauses, index selection and sort clauses

[Alvaro Cabrerizo]

Hello,

When using a native query clause the index plan, of the selected index,
does not include sorting capabilities although the index can. I'm not sure
if this is the expected result.

For example, using the next query:

/jcr:root/content/dam/store//element(*, dam:Asset)[*rep:native('myIndex',
'myProp:myValue')*] order by jcr:content/metadata/@sortableProp

The plan I get is:

{ costPerExecution : 1.0, costPerEntry : 50.0, estimatedEntryCount : 1,
filter : Filter(query=select [jcr:path], [jcr:score], * from [dam:Asset] as
a where native(a, 'myIndex', '*:*') ...order by
[jcr:content/metadata/sortableProp]
/..., isDelayed : true, isFulltextIndex : true, includesNodeData :
false, *sortOrder
: null*, definition : null, propertyRestriction : null, pathPrefix :  }


Keeping in mind plan that the index defines the sortableProp as sortable:

oak:index
|_myIndex (functionName=myIndex)
   |_indexRules
  |_dam:Asset
 |_properties
|_sortableProp* (ordered = true)*


Basically it is not clear why (the rationale behind)
org.apache.jackrabbit.oak.plugins.index.lucene.IndexPlanner.java returns
the planner when the query contains a function that matches and index
funtionName before adding the rest of the index capabilities to the plan.
Thus, the plan does not describe all the index capabilities (e.g. sort) and
when the query is performed through the LucenePropertyIndex I can't not
take advantage of it. Furthermore, what I can see executing the query is
that after retrieving a batch of documents from the index, they are
validated one by one, against all the query conditions, which is an
incredible amount of effort and waste of time as the lucene index was
defined to do all this tasks.
 I guess that rewriting the query should avoid this situation, but not sure
how.

Regards

[ANNOUNCE] Apache Jackrabbit Oak ${version} released

[Davide Giannella]

The Apache Jackrabbit community is pleased to announce the release of
Apache Jackrabbit Oak. 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 Oak -- Version 1.7.2

Introduction


Jackrabbit Oak is a scalable, high-performance hierarchical content
repository designed for use as the foundation of modern world-class
web sites and other demanding content applications.

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

The Oak effort is a part of the Apache Jackrabbit project.
Apache Jackrabbit is a project of the Apache Software Foundation.

Changes in Oak 1.7.2
-

Technical task

[OAK-6248] - Enable use of pre extracted text cache
[OAK-6286] - Use BlobStore in read only mode by default unless
read-write mode enabled

Bug

[OAK-6294] - The "missing" node cache value breaks the
DocumentNodeStore#applyChanges
[OAK-6314] - ActiveDeletedBlobCollectorTest.multiThreadedCommits
is failing intermittently for a few users
[OAK-6321] - oak-blob-plugins exports all packages
[OAK-6335] - Baseline check fails in oak-api
[OAK-6338] - AbstractCompositeProviderTest reverse order flag is
ignored
[OAK-6365] - oak-store-spi fails on javadoc

Improvement

[OAK-3381] - Provide Common Ancestor To ConflictHandler
[OAK-4637] - Property index: include/exclude key pattern list
[OAK-6295] - Move constants from oak.query.QueryImpl to
oak.spi.query.QueryConstants
[OAK-6323] - Remove StandbyTest
[OAK-6324] - Remove SegmentNodeStoreFactoryTest#nodeStoreProvider
[OAK-6326] - Remove unused field SegmentNodeStore.reader
[OAK-6327] - Convert FileStore.maxFileSize fiels into local
variable
[OAK-6328] - Declare StandbyStoreService.closer final
[OAK-6329] - Declare immutable field of FileStore.CompactionResult
final
[OAK-6330] - LockBasedScheduler.execute declares exception that is
never thrown
[OAK-6331] - Closeable.close in StandbyStoreService declares
exception that is never thrown
[OAK-6332] - Add missing @Nonnull annotations
[OAK-6348] - Active deletion of blobs should have larger queue for
blobs being deleted
[OAK-6349] - Randomized permission tests
[OAK-6351] - Invalidate cache entries when getChildNodes() is
aborted
[OAK-6354] - Move DocumentNodeStoreMBean implementation in
separate file
[OAK-6361] - Oak run tika command should connect to NodeStore in
read only mode
[OAK-6362] - Use NodeStoreFixtureProvider in tika command of
oak-run
[OAK-6363] - BlobStoreFixtureProvider should support '.cfg' files
also
[OAK-6364] - BlobStoreFixtureProvider should configure a default
'secret' value if none specified

New Feature

[OAK-3712] - Clean up uncommitted changes

Task

[OAK-6304] - Cyclic dependency between oak.spi.query an
oak.query.*
[OAK-6311] - Move generic part of PropertyStateValue and
PropertyValues to oak-store-spi
[OAK-6343] - Add replacement for deprecated
RootFactory.createSystemRoot

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

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

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

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.md 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
http://www.apache.org/dist/jackrabbit/KEYS.

About Apache Jackrabbit Oak
---

Jackrabbit Oak is a scalable, high-performance hierarchical content
repository designed for use as the foundation of modern world-class
web sites and other demanding content applications.

The Oak effort is a part of the Apache Jackrabbit project.
Apache Jackrabbit is a project of the Apache Software Foundation.

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

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 

[ANNOUNCE] Apache Jackrabbit Oak ${version} released

[Davide Giannella]

The Apache Jackrabbit community is pleased to announce the release of
Apache Jackrabbit Oak. 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 Oak -- Version 1.7.2

Introduction


Jackrabbit Oak is a scalable, high-performance hierarchical content
repository designed for use as the foundation of modern world-class
web sites and other demanding content applications.

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

The Oak effort is a part of the Apache Jackrabbit project.
Apache Jackrabbit is a project of the Apache Software Foundation.

Changes in Oak 1.7.2
-

Technical task

[OAK-6248] - Enable use of pre extracted text cache
[OAK-6286] - Use BlobStore in read only mode by default unless
read-write mode enabled

Bug

[OAK-6294] - The "missing" node cache value breaks the
DocumentNodeStore#applyChanges
[OAK-6314] - ActiveDeletedBlobCollectorTest.multiThreadedCommits
is failing intermittently for a few users
[OAK-6321] - oak-blob-plugins exports all packages
[OAK-6335] - Baseline check fails in oak-api
[OAK-6338] - AbstractCompositeProviderTest reverse order flag is
ignored
[OAK-6365] - oak-store-spi fails on javadoc

Improvement

[OAK-3381] - Provide Common Ancestor To ConflictHandler
[OAK-4637] - Property index: include/exclude key pattern list
[OAK-6295] - Move constants from oak.query.QueryImpl to
oak.spi.query.QueryConstants
[OAK-6323] - Remove StandbyTest
[OAK-6324] - Remove SegmentNodeStoreFactoryTest#nodeStoreProvider
[OAK-6326] - Remove unused field SegmentNodeStore.reader
[OAK-6327] - Convert FileStore.maxFileSize fiels into local
variable
[OAK-6328] - Declare StandbyStoreService.closer final
[OAK-6329] - Declare immutable field of FileStore.CompactionResult
final
[OAK-6330] - LockBasedScheduler.execute declares exception that is
never thrown
[OAK-6331] - Closeable.close in StandbyStoreService declares
exception that is never thrown
[OAK-6332] - Add missing @Nonnull annotations
[OAK-6348] - Active deletion of blobs should have larger queue for
blobs being deleted
[OAK-6349] - Randomized permission tests
[OAK-6351] - Invalidate cache entries when getChildNodes() is
aborted
[OAK-6354] - Move DocumentNodeStoreMBean implementation in
separate file
[OAK-6361] - Oak run tika command should connect to NodeStore in
read only mode
[OAK-6362] - Use NodeStoreFixtureProvider in tika command of
oak-run
[OAK-6363] - BlobStoreFixtureProvider should support '.cfg' files
also
[OAK-6364] - BlobStoreFixtureProvider should configure a default
'secret' value if none specified

New Feature

[OAK-3712] - Clean up uncommitted changes

Task

[OAK-6304] - Cyclic dependency between oak.spi.query an
oak.query.*
[OAK-6311] - Move generic part of PropertyStateValue and
PropertyValues to oak-store-spi
[OAK-6343] - Add replacement for deprecated
RootFactory.createSystemRoot

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

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

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

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.md 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
http://www.apache.org/dist/jackrabbit/KEYS.

About Apache Jackrabbit Oak
---

Jackrabbit Oak is a scalable, high-performance hierarchical content
repository designed for use as the foundation of modern world-class
web sites and other demanding content applications.

The Oak effort is a part of the Apache Jackrabbit project.
Apache Jackrabbit is a project of the Apache Software Foundation.

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

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 

[RESULT][VOTE] Release Apache Jackrabbit Oak 1.7.2

[Davide Giannella]

Hello Team,

the vote passes as follows:

+1 Alex Deparvu
+1 Julian Reschke
+1 Davide Giannella

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

-- Davide

Jackrabbit 2.15.4 Release Plan

[Julian Reschke]

Hi,

I'd like to cut Jackrabbit 2.15.4 early next week.

The list of open issues scheduled for 2.15.4 is empty:

https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%202.15.4%20AND%20project%20%3D%20JCR%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC

The candidate release notes are here:

https://svn.apache.org/repos/asf/jackrabbit/trunk/RELEASE-NOTES.txt

If there are any objections please let me know.

Best regards, Julian

[jira] [Created] (JCR-4152) Release Jackrabbit 2.15.4

[Julian Reschke (JIRA)]

Julian Reschke created JCR-4152:
---

 Summary: Release Jackrabbit 2.15.4
 Key: JCR-4152
 URL: https://issues.apache.org/jira/browse/JCR-4152
 Project: Jackrabbit Content Repository
  Issue Type: Task
Reporter: Julian Reschke
Assignee: Julian Reschke
Priority: Minor






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

[jira] [Updated] (JCR-4147) clirr profile needs to use sensible baselines

[Julian Reschke (JIRA)]

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

Julian Reschke updated JCR-4147:

Fix Version/s: (was: 2.15.4)

> clirr profile needs to use sensible baselines
> -
>
> Key: JCR-4147
> URL: https://issues.apache.org/jira/browse/JCR-4147
> Project: Jackrabbit Content Repository
>  Issue Type: Bug
>  Components: jackrabbit-parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>
> For the "clirr" profile, we currently use a baseline of Jackrabbit 2.2.0 
> throughout. This doesn't make any sense, it should be the previous stable 
> release.



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

[jira] [Resolved] (JCR-4147) clirr profile needs to use sensible baselines

[Julian Reschke (JIRA)]

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

Julian Reschke resolved JCR-4147.
-
Resolution: Won't Fix

> clirr profile needs to use sensible baselines
> -
>
> Key: JCR-4147
> URL: https://issues.apache.org/jira/browse/JCR-4147
> Project: Jackrabbit Content Repository
>  Issue Type: Bug
>  Components: jackrabbit-parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
> Fix For: 2.15.4
>
>
> For the "clirr" profile, we currently use a baseline of Jackrabbit 2.2.0 
> throughout. This doesn't make any sense, it should be the previous stable 
> release.



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

[jira] [Resolved] (JCR-4151) remove clirr profile in branches where bundle:baseline is used

[Julian Reschke (JIRA)]

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

Julian Reschke resolved JCR-4151.
-
   Resolution: Fixed
Fix Version/s: 2.15.4

> remove clirr profile in branches where bundle:baseline is used
> --
>
> Key: JCR-4151
> URL: https://issues.apache.org/jira/browse/JCR-4151
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Trivial
>  Labels: candidate_jcr_2_14
> Fix For: 2.16, 2.15.4
>
>




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

[jira] [Updated] (JCR-4151) remove clirr profile in branches where bundle:baseline is used

[Julian Reschke (JIRA)]

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

Julian Reschke updated JCR-4151:

Labels: candidate_jcr_2_14  (was: )

> remove clirr profile in branches where bundle:baseline is used
> --
>
> Key: JCR-4151
> URL: https://issues.apache.org/jira/browse/JCR-4151
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Trivial
>  Labels: candidate_jcr_2_14
> Fix For: 2.16
>
>




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

[jira] [Created] (JCR-4151) remove clirr profile in branches where bundle:baseline is used

[Julian Reschke (JIRA)]

Julian Reschke created JCR-4151:
---

 Summary: remove clirr profile in branches where bundle:baseline is 
used
 Key: JCR-4151
 URL: https://issues.apache.org/jira/browse/JCR-4151
 Project: Jackrabbit Content Repository
  Issue Type: Task
  Components: parent
Reporter: Julian Reschke
Assignee: Julian Reschke
Priority: Trivial
 Fix For: 2.16






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

[jira] [Commented] (JCR-4149) change to drop SHA-1 requires version change

[Julian Reschke (JIRA)]

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

Julian Reschke commented on JCR-4149:
-

trunk: [r1799538|http://svn.apache.org/r1799538]
2.14: [r1799566|http://svn.apache.org/r1799566]


> change to drop SHA-1 requires version change
> 
>
> Key: JCR-4149
> URL: https://issues.apache.org/jira/browse/JCR-4149
> Project: Jackrabbit Content Repository
>  Issue Type: Bug
>  Components: jackrabbit-data
>Affects Versions: 2.15.3
>Reporter: Julian Reschke
>Assignee: Julian Reschke
> Fix For: 2.16, 2.14.2, 2.15.4
>
> Attachments: JCR_4149.patch
>
>
> The change for JCR-4115 for 2.14 causes a problem report by the bundle plugin:
> {noformat}
> [INFO] 
> ---
> [INFO] * org.apache.jackrabbit.core.data.db major  2.13.5 
> 2.13.5 3.0.0  Version increase required
> [INFO]  > class org.apache.jackrabbit.core.data.db.DbDataStore
> [INFO]  > field java.lang.String DIGEST
> [INFO]  - access final
> [INFO]  - access static
> [INFO]  - constant SHA-1
> [INFO]  > class org.apache.jackrabbit.core.data.db.DerbyDataStore
> [INFO]  > field java.lang.String DIGEST
> [INFO]  - access final
> [INFO]  - access static
> [INFO]  - constant SHA-1
> {noformat}
> Reverting [r1797148|http://svn.apache.org/r1797148] for now. but we also need 
> to solve this for trunk where the change wasn't noticed before a release.



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

[jira] [Issue Comment Deleted] (JCR-4149) change to drop SHA-1 requires version change

[Julian Reschke (JIRA)]

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

Julian Reschke updated JCR-4149:

Comment: was deleted

(was: [~amitjain] - thanks. Please wait with the backport to 2.14 until we have 
baseline checks enabled over there as well.)

> change to drop SHA-1 requires version change
> 
>
> Key: JCR-4149
> URL: https://issues.apache.org/jira/browse/JCR-4149
> Project: Jackrabbit Content Repository
>  Issue Type: Bug
>  Components: jackrabbit-data
>Affects Versions: 2.15.3
>Reporter: Julian Reschke
>Assignee: Julian Reschke
> Fix For: 2.16, 2.14.2, 2.15.4
>
> Attachments: JCR_4149.patch
>
>
> The change for JCR-4115 for 2.14 causes a problem report by the bundle plugin:
> {noformat}
> [INFO] 
> ---
> [INFO] * org.apache.jackrabbit.core.data.db major  2.13.5 
> 2.13.5 3.0.0  Version increase required
> [INFO]  > class org.apache.jackrabbit.core.data.db.DbDataStore
> [INFO]  > field java.lang.String DIGEST
> [INFO]  - access final
> [INFO]  - access static
> [INFO]  - constant SHA-1
> [INFO]  > class org.apache.jackrabbit.core.data.db.DerbyDataStore
> [INFO]  > field java.lang.String DIGEST
> [INFO]  - access final
> [INFO]  - access static
> [INFO]  - constant SHA-1
> {noformat}
> Reverting [r1797148|http://svn.apache.org/r1797148] for now. but we also need 
> to solve this for trunk where the change wasn't noticed before a release.



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

[jira] [Resolved] (JCR-4149) change to drop SHA-1 requires version change

[Julian Reschke (JIRA)]

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

Julian Reschke resolved JCR-4149.
-
Resolution: Fixed

> change to drop SHA-1 requires version change
> 
>
> Key: JCR-4149
> URL: https://issues.apache.org/jira/browse/JCR-4149
> Project: Jackrabbit Content Repository
>  Issue Type: Bug
>  Components: jackrabbit-data
>Affects Versions: 2.15.3
>Reporter: Julian Reschke
>Assignee: Julian Reschke
> Fix For: 2.16, 2.14.2, 2.15.4
>
> Attachments: JCR_4149.patch
>
>
> The change for JCR-4115 for 2.14 causes a problem report by the bundle plugin:
> {noformat}
> [INFO] 
> ---
> [INFO] * org.apache.jackrabbit.core.data.db major  2.13.5 
> 2.13.5 3.0.0  Version increase required
> [INFO]  > class org.apache.jackrabbit.core.data.db.DbDataStore
> [INFO]  > field java.lang.String DIGEST
> [INFO]  - access final
> [INFO]  - access static
> [INFO]  - constant SHA-1
> [INFO]  > class org.apache.jackrabbit.core.data.db.DerbyDataStore
> [INFO]  > field java.lang.String DIGEST
> [INFO]  - access final
> [INFO]  - access static
> [INFO]  - constant SHA-1
> {noformat}
> Reverting [r1797148|http://svn.apache.org/r1797148] for now. but we also need 
> to solve this for trunk where the change wasn't noticed before a release.



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

[jira] [Issue Comment Deleted] (JCR-4149) change to drop SHA-1 requires version change

[Julian Reschke (JIRA)]

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

Julian Reschke updated JCR-4149:

Comment: was deleted

(was: (taking over for 2.14))

> change to drop SHA-1 requires version change
> 
>
> Key: JCR-4149
> URL: https://issues.apache.org/jira/browse/JCR-4149
> Project: Jackrabbit Content Repository
>  Issue Type: Bug
>  Components: jackrabbit-data
>Affects Versions: 2.15.3
>Reporter: Julian Reschke
>Assignee: Julian Reschke
> Fix For: 2.16, 2.14.2, 2.15.4
>
> Attachments: JCR_4149.patch
>
>
> The change for JCR-4115 for 2.14 causes a problem report by the bundle plugin:
> {noformat}
> [INFO] 
> ---
> [INFO] * org.apache.jackrabbit.core.data.db major  2.13.5 
> 2.13.5 3.0.0  Version increase required
> [INFO]  > class org.apache.jackrabbit.core.data.db.DbDataStore
> [INFO]  > field java.lang.String DIGEST
> [INFO]  - access final
> [INFO]  - access static
> [INFO]  - constant SHA-1
> [INFO]  > class org.apache.jackrabbit.core.data.db.DerbyDataStore
> [INFO]  > field java.lang.String DIGEST
> [INFO]  - access final
> [INFO]  - access static
> [INFO]  - constant SHA-1
> {noformat}
> Reverting [r1797148|http://svn.apache.org/r1797148] for now. but we also need 
> to solve this for trunk where the change wasn't noticed before a release.



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

[jira] [Updated] (JCR-4149) change to drop SHA-1 requires version change

[Julian Reschke (JIRA)]

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

Julian Reschke updated JCR-4149:

Fix Version/s: 2.16

> change to drop SHA-1 requires version change
> 
>
> Key: JCR-4149
> URL: https://issues.apache.org/jira/browse/JCR-4149
> Project: Jackrabbit Content Repository
>  Issue Type: Bug
>  Components: jackrabbit-data
>Affects Versions: 2.15.3
>Reporter: Julian Reschke
>Assignee: Julian Reschke
> Fix For: 2.16, 2.14.2, 2.15.4
>
> Attachments: JCR_4149.patch
>
>
> The change for JCR-4115 for 2.14 causes a problem report by the bundle plugin:
> {noformat}
> [INFO] 
> ---
> [INFO] * org.apache.jackrabbit.core.data.db major  2.13.5 
> 2.13.5 3.0.0  Version increase required
> [INFO]  > class org.apache.jackrabbit.core.data.db.DbDataStore
> [INFO]  > field java.lang.String DIGEST
> [INFO]  - access final
> [INFO]  - access static
> [INFO]  - constant SHA-1
> [INFO]  > class org.apache.jackrabbit.core.data.db.DerbyDataStore
> [INFO]  > field java.lang.String DIGEST
> [INFO]  - access final
> [INFO]  - access static
> [INFO]  - constant SHA-1
> {noformat}
> Reverting [r1797148|http://svn.apache.org/r1797148] for now. but we also need 
> to solve this for trunk where the change wasn't noticed before a release.



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

[jira] [Commented] (JCR-4115) Don't use SHA-1 for new DataStore binaries (Jackrabbit)

[Julian Reschke (JIRA)]

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

Julian Reschke commented on JCR-4115:
-

trunk: [r1785225|http://svn.apache.org/r1785225]
2.14: [r1799566|http://svn.apache.org/r1799566] 
[r1799202|http://svn.apache.org/r1799202] 
[r1797148|http://svn.apache.org/r1797148]


> Don't use SHA-1 for new DataStore binaries (Jackrabbit)
> ---
>
> Key: JCR-4115
> URL: https://issues.apache.org/jira/browse/JCR-4115
> Project: Jackrabbit Content Repository
>  Issue Type: Improvement
>Reporter: Thomas Mueller
>Assignee: Amit Jain
>  Labels: candidate_jcr_2_10, candidate_jcr_2_12, 
> candidate_jcr_2_4, candidate_jcr_2_6, candidate_jcr_2_8
> Fix For: 2.16, 2.15.1, 2.14.2
>
> Attachments: JCR-4115b.patch, JCR-4115c.patch, JCR-4115.patch
>
>
> A collision for SHA-1 has been published. We still use SHA-1 for the 
> FileDataStore, and I believe the S3 DataStore right now. Given there is a 
> collision, we should switch to a stronger algorithm, for example SHA-256, for 
> new binaries.



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

[jira] [Issue Comment Deleted] (JCR-4115) Don't use SHA-1 for new DataStore binaries (Jackrabbit)

[Julian Reschke (JIRA)]

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

Julian Reschke updated JCR-4115:

Comment: was deleted

(was: trunk: [r1785225|http://svn.apache.org/r1785225]
2.14: [r1797148|http://svn.apache.org/r1797148]
)

> Don't use SHA-1 for new DataStore binaries (Jackrabbit)
> ---
>
> Key: JCR-4115
> URL: https://issues.apache.org/jira/browse/JCR-4115
> Project: Jackrabbit Content Repository
>  Issue Type: Improvement
>Reporter: Thomas Mueller
>Assignee: Amit Jain
>  Labels: candidate_jcr_2_10, candidate_jcr_2_12, 
> candidate_jcr_2_4, candidate_jcr_2_6, candidate_jcr_2_8
> Fix For: 2.16, 2.15.1, 2.14.2
>
> Attachments: JCR-4115b.patch, JCR-4115c.patch, JCR-4115.patch
>
>
> A collision for SHA-1 has been published. We still use SHA-1 for the 
> FileDataStore, and I believe the S3 DataStore right now. Given there is a 
> collision, we should switch to a stronger algorithm, for example SHA-256, for 
> new binaries.



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

[jira] [Issue Comment Deleted] (JCR-4115) Don't use SHA-1 for new DataStore binaries (Jackrabbit)

[Julian Reschke (JIRA)]

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

Julian Reschke updated JCR-4115:

Comment: was deleted

(was: 2.14 change reverted in [r1799202|http://svn.apache.org/r1799202])

> Don't use SHA-1 for new DataStore binaries (Jackrabbit)
> ---
>
> Key: JCR-4115
> URL: https://issues.apache.org/jira/browse/JCR-4115
> Project: Jackrabbit Content Repository
>  Issue Type: Improvement
>Reporter: Thomas Mueller
>Assignee: Amit Jain
>  Labels: candidate_jcr_2_10, candidate_jcr_2_12, 
> candidate_jcr_2_4, candidate_jcr_2_6, candidate_jcr_2_8
> Fix For: 2.16, 2.15.1, 2.14.2
>
> Attachments: JCR-4115b.patch, JCR-4115c.patch, JCR-4115.patch
>
>
> A collision for SHA-1 has been published. We still use SHA-1 for the 
> FileDataStore, and I believe the S3 DataStore right now. Given there is a 
> collision, we should switch to a stronger algorithm, for example SHA-256, for 
> new binaries.



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

[jira] [Updated] (JCR-4115) Don't use SHA-1 for new DataStore binaries (Jackrabbit)

[Julian Reschke (JIRA)]

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

Julian Reschke updated JCR-4115:

Fix Version/s: 2.14.2

> Don't use SHA-1 for new DataStore binaries (Jackrabbit)
> ---
>
> Key: JCR-4115
> URL: https://issues.apache.org/jira/browse/JCR-4115
> Project: Jackrabbit Content Repository
>  Issue Type: Improvement
>Reporter: Thomas Mueller
>Assignee: Amit Jain
>  Labels: candidate_jcr_2_10, candidate_jcr_2_12, 
> candidate_jcr_2_4, candidate_jcr_2_6, candidate_jcr_2_8
> Fix For: 2.16, 2.15.1, 2.14.2
>
> Attachments: JCR-4115b.patch, JCR-4115c.patch, JCR-4115.patch
>
>
> A collision for SHA-1 has been published. We still use SHA-1 for the 
> FileDataStore, and I believe the S3 DataStore right now. Given there is a 
> collision, we should switch to a stronger algorithm, for example SHA-256, for 
> new binaries.



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

[jira] [Updated] (JCR-4115) Don't use SHA-1 for new DataStore binaries (Jackrabbit)

[Julian Reschke (JIRA)]

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

Julian Reschke updated JCR-4115:

Labels: candidate_jcr_2_10 candidate_jcr_2_12 candidate_jcr_2_4 
candidate_jcr_2_6 candidate_jcr_2_8  (was: candidate_jcr_2_10 
candidate_jcr_2_12 candidate_jcr_2_14 candidate_jcr_2_4 candidate_jcr_2_6 
candidate_jcr_2_8)

> Don't use SHA-1 for new DataStore binaries (Jackrabbit)
> ---
>
> Key: JCR-4115
> URL: https://issues.apache.org/jira/browse/JCR-4115
> Project: Jackrabbit Content Repository
>  Issue Type: Improvement
>Reporter: Thomas Mueller
>Assignee: Amit Jain
>  Labels: candidate_jcr_2_10, candidate_jcr_2_12, 
> candidate_jcr_2_4, candidate_jcr_2_6, candidate_jcr_2_8
> Fix For: 2.16, 2.15.1
>
> Attachments: JCR-4115b.patch, JCR-4115c.patch, JCR-4115.patch
>
>
> A collision for SHA-1 has been published. We still use SHA-1 for the 
> FileDataStore, and I believe the S3 DataStore right now. Given there is a 
> collision, we should switch to a stronger algorithm, for example SHA-256, for 
> new binaries.



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

Jackrabbit-trunk - Build # 2502 - Fixed

[Apache Jenkins Server]

The Apache Jenkins build system has built Jackrabbit-trunk (build #2502)

Status: Fixed

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

[jira] [Commented] (JCR-4149) change to drop SHA-1 requires version change

[Julian Reschke (JIRA)]

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

Julian Reschke commented on JCR-4149:
-

(taking over for 2.14)

> change to drop SHA-1 requires version change
> 
>
> Key: JCR-4149
> URL: https://issues.apache.org/jira/browse/JCR-4149
> Project: Jackrabbit Content Repository
>  Issue Type: Bug
>  Components: jackrabbit-data
>Affects Versions: 2.15.3
>Reporter: Julian Reschke
>Assignee: Julian Reschke
> Fix For: 2.14.2, 2.15.4
>
> Attachments: JCR_4149.patch
>
>
> The change for JCR-4115 for 2.14 causes a problem report by the bundle plugin:
> {noformat}
> [INFO] 
> ---
> [INFO] * org.apache.jackrabbit.core.data.db major  2.13.5 
> 2.13.5 3.0.0  Version increase required
> [INFO]  > class org.apache.jackrabbit.core.data.db.DbDataStore
> [INFO]  > field java.lang.String DIGEST
> [INFO]  - access final
> [INFO]  - access static
> [INFO]  - constant SHA-1
> [INFO]  > class org.apache.jackrabbit.core.data.db.DerbyDataStore
> [INFO]  > field java.lang.String DIGEST
> [INFO]  - access final
> [INFO]  - access static
> [INFO]  - constant SHA-1
> {noformat}
> Reverting [r1797148|http://svn.apache.org/r1797148] for now. but we also need 
> to solve this for trunk where the change wasn't noticed before a release.



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

[jira] [Assigned] (JCR-4149) change to drop SHA-1 requires version change

[Julian Reschke (JIRA)]

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

Julian Reschke reassigned JCR-4149:
---

Assignee: Julian Reschke  (was: Amit Jain)

> change to drop SHA-1 requires version change
> 
>
> Key: JCR-4149
> URL: https://issues.apache.org/jira/browse/JCR-4149
> Project: Jackrabbit Content Repository
>  Issue Type: Bug
>  Components: jackrabbit-data
>Affects Versions: 2.15.3
>Reporter: Julian Reschke
>Assignee: Julian Reschke
> Fix For: 2.14.2, 2.15.4
>
> Attachments: JCR_4149.patch
>
>
> The change for JCR-4115 for 2.14 causes a problem report by the bundle plugin:
> {noformat}
> [INFO] 
> ---
> [INFO] * org.apache.jackrabbit.core.data.db major  2.13.5 
> 2.13.5 3.0.0  Version increase required
> [INFO]  > class org.apache.jackrabbit.core.data.db.DbDataStore
> [INFO]  > field java.lang.String DIGEST
> [INFO]  - access final
> [INFO]  - access static
> [INFO]  - constant SHA-1
> [INFO]  > class org.apache.jackrabbit.core.data.db.DerbyDataStore
> [INFO]  > field java.lang.String DIGEST
> [INFO]  - access final
> [INFO]  - access static
> [INFO]  - constant SHA-1
> {noformat}
> Reverting [r1797148|http://svn.apache.org/r1797148] for now. but we also need 
> to solve this for trunk where the change wasn't noticed before a release.



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

[jira] [Comment Edited] (JCR-4150) enable bundle:baseline check

[Julian Reschke (JIRA)]

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

Julian Reschke edited comment on JCR-4150 at 6/22/17 11:30 AM:
---

trunk: [r1799549|http://svn.apache.org/r1799549]
2.14: [r1799564|http://svn.apache.org/r1799564]



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


> enable bundle:baseline check
> 
>
> Key: JCR-4150
> URL: https://issues.apache.org/jira/browse/JCR-4150
> Project: Jackrabbit Content Repository
>  Issue Type: Bug
>  Components: jackrabbit-parent
>Affects Versions: 2.15.3
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>  Labels: candidate_jcr_2_10, candidate_jcr_2_12, 
> candidate_jcr_2_6, candidate_jcr_2_8
> Fix For: 2.16, 2.14.2, 2.15.4
>
> Attachments: JCR-4150.diff
>
>
> We should enable baseline checks to detect unintended API changes.



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

[jira] [Updated] (JCR-4150) enable bundle:baseline check

[Julian Reschke (JIRA)]

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

Julian Reschke updated JCR-4150:

Labels: candidate_jcr_2_10 candidate_jcr_2_12 candidate_jcr_2_6 
candidate_jcr_2_8  (was: candidate_jcr_2_10 candidate_jcr_2_12 
candidate_jcr_2_14 candidate_jcr_2_6 candidate_jcr_2_8)

> enable bundle:baseline check
> 
>
> Key: JCR-4150
> URL: https://issues.apache.org/jira/browse/JCR-4150
> Project: Jackrabbit Content Repository
>  Issue Type: Bug
>  Components: jackrabbit-parent
>Affects Versions: 2.15.3
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>  Labels: candidate_jcr_2_10, candidate_jcr_2_12, 
> candidate_jcr_2_6, candidate_jcr_2_8
> Fix For: 2.16, 2.14.2, 2.15.4
>
> Attachments: JCR-4150.diff
>
>
> We should enable baseline checks to detect unintended API changes.



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

[jira] [Comment Edited] (JCR-4128) update maven plugins and require Maven 3.2.1

[Julian Reschke (JIRA)]

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

Julian Reschke edited comment on JCR-4128 at 6/22/17 10:20 AM:
---

trunk: [r1792113|http://svn.apache.org/r1792113] 
[r1792105|http://svn.apache.org/r1792105] 
[r1792100|http://svn.apache.org/r1792100]
2.14: [r1799558|http://svn.apache.org/r1799558]



was (Author: reschke):
trunk: [r1792113|http://svn.apache.org/r1792113] 
[r1792105|http://svn.apache.org/r1792105] 
[r1792100|http://svn.apache.org/r1792100]


> update maven plugins and require Maven 3.2.1
> 
>
> Key: JCR-4128
> URL: https://issues.apache.org/jira/browse/JCR-4128
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>  Labels: candidate_jcr_2_12
> Fix For: 2.16, 2.15.2, 2.14.2
>
>
> As suggested by:
> {noformat}
> mvn versions:display-plugin-updates
> {noformat}



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

[jira] [Updated] (JCR-4128) update maven plugins and require Maven 3.2.1

[Julian Reschke (JIRA)]

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

Julian Reschke updated JCR-4128:

Fix Version/s: 2.14.2

> update maven plugins and require Maven 3.2.1
> 
>
> Key: JCR-4128
> URL: https://issues.apache.org/jira/browse/JCR-4128
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>  Labels: candidate_jcr_2_12
> Fix For: 2.16, 2.15.2, 2.14.2
>
>
> As suggested by:
> {noformat}
> mvn versions:display-plugin-updates
> {noformat}



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

[jira] [Updated] (JCR-4128) update maven plugins and require Maven 3.2.1

[Julian Reschke (JIRA)]

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

Julian Reschke updated JCR-4128:

Labels: candidate_jcr_2_12  (was: candidate_jcr_2_14)

> update maven plugins and require Maven 3.2.1
> 
>
> Key: JCR-4128
> URL: https://issues.apache.org/jira/browse/JCR-4128
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>  Labels: candidate_jcr_2_12
> Fix For: 2.16, 2.15.2, 2.14.2
>
>
> As suggested by:
> {noformat}
> mvn versions:display-plugin-updates
> {noformat}



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

[jira] [Updated] (JCR-4144) JackrabbitAccessControlList should have an API boolean isMultiValueRestriction(restrictionName)

[angela (JIRA)]

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

angela updated JCR-4144:

Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed revision 1799557.


> JackrabbitAccessControlList should have an API boolean 
> isMultiValueRestriction(restrictionName)
> ---
>
> Key: JCR-4144
> URL: https://issues.apache.org/jira/browse/JCR-4144
> Project: Jackrabbit Content Repository
>  Issue Type: New Feature
>  Components: jackrabbit-api
>Affects Versions: 2.15.3
>Reporter: Nitin Nizhawan
> Fix For: 2.16, 2.15.4
>
> Attachments: JCR-4144.patch
>
>
> JackrabbitAccessControlList \[0\] has a method int getRestrictionType(String 
> restrictionName).
> This method returns the type of the restriction specified restrictionName. 
> Although, it does not provide enough information to deduce whether 
> restriction is defined to accept single or multiple values. Hence, a method 
> with following signature should be added to this API
> {code}
>   boolean isMultiValueRestriction(String restrictionName)
> {code}
> \[0\] 
> https://jackrabbit.apache.org/api/2.4/org/apache/jackrabbit/api/security/JackrabbitAccessControlList.html



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

[jira] [Commented] (JCR-4144) JackrabbitAccessControlList should have an API boolean isMultiValueRestriction(restrictionName)

[Julian Reschke (JIRA)]

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

Julian Reschke commented on JCR-4144:
-

[~anchela] - now that JCR-4150 is done, should I apply the patch?

> JackrabbitAccessControlList should have an API boolean 
> isMultiValueRestriction(restrictionName)
> ---
>
> Key: JCR-4144
> URL: https://issues.apache.org/jira/browse/JCR-4144
> Project: Jackrabbit Content Repository
>  Issue Type: New Feature
>  Components: jackrabbit-api
>Affects Versions: 2.15.3
>Reporter: Nitin Nizhawan
> Fix For: 2.16, 2.15.4
>
> Attachments: JCR-4144.patch
>
>
> JackrabbitAccessControlList \[0\] has a method int getRestrictionType(String 
> restrictionName).
> This method returns the type of the restriction specified restrictionName. 
> Although, it does not provide enough information to deduce whether 
> restriction is defined to accept single or multiple values. Hence, a method 
> with following signature should be added to this API
> {code}
>   boolean isMultiValueRestriction(String restrictionName)
> {code}
> \[0\] 
> https://jackrabbit.apache.org/api/2.4/org/apache/jackrabbit/api/security/JackrabbitAccessControlList.html



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

[jira] [Updated] (JCR-4144) JackrabbitAccessControlList should have an API boolean isMultiValueRestriction(restrictionName)

[Julian Reschke (JIRA)]

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

Julian Reschke updated JCR-4144:

Fix Version/s: 2.16

> JackrabbitAccessControlList should have an API boolean 
> isMultiValueRestriction(restrictionName)
> ---
>
> Key: JCR-4144
> URL: https://issues.apache.org/jira/browse/JCR-4144
> Project: Jackrabbit Content Repository
>  Issue Type: New Feature
>  Components: jackrabbit-api
>Affects Versions: 2.15.3
>Reporter: Nitin Nizhawan
> Fix For: 2.16, 2.15.4
>
> Attachments: JCR-4144.patch
>
>
> JackrabbitAccessControlList \[0\] has a method int getRestrictionType(String 
> restrictionName).
> This method returns the type of the restriction specified restrictionName. 
> Although, it does not provide enough information to deduce whether 
> restriction is defined to accept single or multiple values. Hence, a method 
> with following signature should be added to this API
> {code}
>   boolean isMultiValueRestriction(String restrictionName)
> {code}
> \[0\] 
> https://jackrabbit.apache.org/api/2.4/org/apache/jackrabbit/api/security/JackrabbitAccessControlList.html



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

Re: [VOTE] Release Apache Jackrabbit Filevault 3.1.40

[Marcel Reutegger]

On 22/06/17 04:14, Tobias Bocanegra wrote:

Please vote on releasing this package as Apache Jackrabbit Filevault 3.1.40.
The vote is open for the next 72 hours and passes if a majority of at
least three +1 Jackrabbit PMC votes are cast.


All checks OK.

+1 Release this package as Apache Jackrabbit Filevault 3.1.40

Regards
 Marcel

Jackrabbit-trunk - Build # 2501 - Failure

[Apache Jenkins Server]

The Apache Jenkins build system has built Jackrabbit-trunk (build #2501)

Status: Failure

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

Re: [VOTE] Release Apache Jackrabbit Filevault 3.1.40

[Tobias Bocanegra]

yes, fixed version in jira is not binding. it is a wish :-)
I removed them from the 3.1.40 version.

regards, toby

On Thu, Jun 22, 2017 at 5:35 PM, Konrad Windszus  wrote:
> According to JIRA there are still three outstanding issues for 3.1.40: 
> https://issues.apache.org/jira/projects/JCRVLT/versions/12339160. Do you want 
> to move those to the next release?
> Konrad
>
>> On 22. Jun 2017, at 04:14, Tobias Bocanegra  wrote:
>>
>> Hi,
>>
>> A candidate for the Jackrabbit Filevault 3.1.40 release is available at:
>>
>> https://dist.apache.org/repos/dist/dev/jackrabbit/filevault/3.1.40/
>>
>> The release candidate is a zip archive of the sources in:
>>
>> https://svn.apache.org/repos/asf/jackrabbit/commons/filevault/tags/jackrabbit-filevault-3.1.40/
>>
>> The SHA1 checksum of the archive is 9ce3ed280c2bb42b1823f9fc7f6ff0e2168ea166.
>>
>> A staged Maven repository is available for review at:
>>
>> https://repository.apache.org/content/repositories/orgapachejackrabbit-1256/
>>
>> Please vote on releasing this package as Apache Jackrabbit Filevault 3.1.40.
>> The vote is open for the next 72 hours and passes if a majority of at
>> least three +1 Jackrabbit PMC votes are cast.
>>
>> [ ] +1 Release this package as Apache Jackrabbit Filevault 3.1.40
>> [ ] -1 Do not release this package because...
>

[jira] [Updated] (JCRVLT-160) Add test for Binaryless Export on Shared Caching DataStore

[Tobias Bocanegra (JIRA)]

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

Tobias Bocanegra updated JCRVLT-160:

Fix Version/s: (was: 3.1.40)

> Add test for Binaryless Export on Shared Caching DataStore 
> ---
>
> Key: JCRVLT-160
> URL: https://issues.apache.org/jira/browse/JCRVLT-160
> Project: Jackrabbit FileVault
>  Issue Type: Test
>  Components: Packaging
>Affects Versions: 3.1.30
>Reporter: Timothee Maret
>
> Oak 1.6.x supports Shared Caching DataStore [0]. Caching of blobs may affect 
> BL exports (importer may not see the blob upon import) and thus an IT test to 
> cover it would be beneficial.
> [0] 
> https://jackrabbit.apache.org/oak/docs/osgi_config.html#Oak_-_AbstractSharedCachingDataStore_OAK_1.6.x



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

[jira] [Updated] (JCRVLT-161) Document FileVault Workspace Property filter

[Tobias Bocanegra (JIRA)]

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

Tobias Bocanegra updated JCRVLT-161:

Fix Version/s: (was: 3.1.40)

> Document FileVault Workspace Property filter
> 
>
> Key: JCRVLT-161
> URL: https://issues.apache.org/jira/browse/JCRVLT-161
> Project: Jackrabbit FileVault
>  Issue Type: Task
>Reporter: Timothee Maret
>
> Since JCRVLT-120, Workspace filters on properties can be defined.
> The documentation at [0] should be updated in order to describe (or at least 
> contain an example) of property filter.
> Example of property filter (excludes properties {{prop1}}):
> {code}
> 
> 
> 
> 
> 
> {code}
> Also, the JavaDoc exported at 
> https://jackrabbit.apache.org/filevault/apidocs/index.html?org/apache/jackrabbit/vault/fs/api/FilterSet.html
>  does not contains the 
> {code}
> DefaultWorkspaceFilter#addPropertyFilterSet(PathFilterSet)
> {code}
> signature and related.
> [0] http://jackrabbit.apache.org/filevault/filter.html



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

[jira] [Updated] (JCRVLT-159) Run FileVault core integration tests on oak-segment-tar

[Tobias Bocanegra (JIRA)]

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

Tobias Bocanegra updated JCRVLT-159:

Fix Version/s: (was: 3.1.40)

> Run FileVault core integration tests on oak-segment-tar
> ---
>
> Key: JCRVLT-159
> URL: https://issues.apache.org/jira/browse/JCRVLT-159
> Project: Jackrabbit FileVault
>  Issue Type: Test
>  Components: Packaging
>Affects Versions: 3.1.30
>Reporter: Timothee Maret
> Attachments: JCRVLT-159.patch
>
>
> Currently the vlt core IT tests run on segment-tar [0]. This issue tracks 
> running the tests on the new segment tar implementation
> {code}
> 
> org.apache.jackrabbit
> oak-segment-tar
> 1.6
> test
> 
> {code}
> [0] 
> https://github.com/apache/jackrabbit-filevault/blob/trunk/vault-core/pom.xml#L216



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

[jira] [Commented] (JCR-4147) clirr profile needs to use sensible baselines

[Julian Reschke (JIRA)]

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

Julian Reschke commented on JCR-4147:
-

bq. I would prefer using the baseline plugin.

Right - any objections to disable clirr once baseline is used?

> clirr profile needs to use sensible baselines
> -
>
> Key: JCR-4147
> URL: https://issues.apache.org/jira/browse/JCR-4147
> Project: Jackrabbit Content Repository
>  Issue Type: Bug
>  Components: jackrabbit-parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>  Labels: candidate_jcr_2_10, candidate_jcr_2_12, 
> candidate_jcr_2_14, candidate_jcr_2_4, candidate_jcr_2_6, candidate_jcr_2_8
> Fix For: 2.15.4
>
>
> For the "clirr" profile, we currently use a baseline of Jackrabbit 2.2.0 
> throughout. This doesn't make any sense, it should be the previous stable 
> release.



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

Re: [VOTE] Release Apache Jackrabbit Filevault 3.1.40

[Konrad Windszus]

According to JIRA there are still three outstanding issues for 3.1.40: 
https://issues.apache.org/jira/projects/JCRVLT/versions/12339160. Do you want 
to move those to the next release?
Konrad

> On 22. Jun 2017, at 04:14, Tobias Bocanegra  wrote:
> 
> Hi,
> 
> A candidate for the Jackrabbit Filevault 3.1.40 release is available at:
> 
> https://dist.apache.org/repos/dist/dev/jackrabbit/filevault/3.1.40/
> 
> The release candidate is a zip archive of the sources in:
> 
> https://svn.apache.org/repos/asf/jackrabbit/commons/filevault/tags/jackrabbit-filevault-3.1.40/
> 
> The SHA1 checksum of the archive is 9ce3ed280c2bb42b1823f9fc7f6ff0e2168ea166.
> 
> A staged Maven repository is available for review at:
> 
> https://repository.apache.org/content/repositories/orgapachejackrabbit-1256/
> 
> Please vote on releasing this package as Apache Jackrabbit Filevault 3.1.40.
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 Jackrabbit PMC votes are cast.
> 
> [ ] +1 Release this package as Apache Jackrabbit Filevault 3.1.40
> [ ] -1 Do not release this package because...

[jira] [Commented] (JCR-4150) enable bundle:baseline check

[Julian Reschke (JIRA)]

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

Julian Reschke commented on JCR-4150:
-

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


> enable bundle:baseline check
> 
>
> Key: JCR-4150
> URL: https://issues.apache.org/jira/browse/JCR-4150
> Project: Jackrabbit Content Repository
>  Issue Type: Bug
>  Components: jackrabbit-parent
>Affects Versions: 2.15.3
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>  Labels: candidate_jcr_2_10, candidate_jcr_2_12, 
> candidate_jcr_2_14, candidate_jcr_2_6, candidate_jcr_2_8
> Fix For: 2.16, 2.15.4
>
> Attachments: JCR-4150.diff
>
>
> We should enable baseline checks to detect unintended API changes.



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

[jira] [Resolved] (JCR-4150) enable bundle:baseline check

[Julian Reschke (JIRA)]

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

Julian Reschke resolved JCR-4150.
-
   Resolution: Fixed
Fix Version/s: 2.15.4
   2.16

> enable bundle:baseline check
> 
>
> Key: JCR-4150
> URL: https://issues.apache.org/jira/browse/JCR-4150
> Project: Jackrabbit Content Repository
>  Issue Type: Bug
>  Components: jackrabbit-parent
>Affects Versions: 2.15.3
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>  Labels: candidate_jcr_2_10, candidate_jcr_2_12, 
> candidate_jcr_2_14, candidate_jcr_2_6, candidate_jcr_2_8
> Fix For: 2.16, 2.15.4
>
> Attachments: JCR-4150.diff
>
>
> We should enable baseline checks to detect unintended API changes.



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

[jira] [Updated] (JCR-4150) enable bundle:baseline check

[Julian Reschke (JIRA)]

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

Julian Reschke updated JCR-4150:

Labels: candidate_jcr_2_10 candidate_jcr_2_12 candidate_jcr_2_14 
candidate_jcr_2_6 candidate_jcr_2_8  (was: )

> enable bundle:baseline check
> 
>
> Key: JCR-4150
> URL: https://issues.apache.org/jira/browse/JCR-4150
> Project: Jackrabbit Content Repository
>  Issue Type: Bug
>  Components: jackrabbit-parent
>Affects Versions: 2.15.3
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>  Labels: candidate_jcr_2_10, candidate_jcr_2_12, 
> candidate_jcr_2_14, candidate_jcr_2_6, candidate_jcr_2_8
> Fix For: 2.16, 2.15.4
>
> Attachments: JCR-4150.diff
>
>
> We should enable baseline checks to detect unintended API changes.



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

[jira] [Commented] (JCR-4150) enable bundle:baseline check

[Marcel Reutegger (JIRA)]

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

Marcel Reutegger commented on JCR-4150:
---

Oh, right. That means we can revert the dependency update in Oak done for 
OAK-3041. I'll create an issue... 

> enable bundle:baseline check
> 
>
> Key: JCR-4150
> URL: https://issues.apache.org/jira/browse/JCR-4150
> Project: Jackrabbit Content Repository
>  Issue Type: Bug
>  Components: jackrabbit-parent
>Affects Versions: 2.15.3
>Reporter: Julian Reschke
>Assignee: Julian Reschke
> Attachments: JCR-4150.diff
>
>
> We should enable baseline checks to detect unintended API changes.



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

[jira] [Commented] (JCR-4150) enable bundle:baseline check

[Julian Reschke (JIRA)]

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

Julian Reschke commented on JCR-4150:
-

bq. Not required right now, but would be good to also include the Bnd update 
done in OAK-3041.

[~mreutegg] - we're on 3.3.0 already, see JCR-4128.

> enable bundle:baseline check
> 
>
> Key: JCR-4150
> URL: https://issues.apache.org/jira/browse/JCR-4150
> Project: Jackrabbit Content Repository
>  Issue Type: Bug
>  Components: jackrabbit-parent
>Affects Versions: 2.15.3
>Reporter: Julian Reschke
>Assignee: Julian Reschke
> Attachments: JCR-4150.diff
>
>
> We should enable baseline checks to detect unintended API changes.



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

[jira] [Updated] (JCR-4128) update maven plugins and require Maven 3.2.1

[Julian Reschke (JIRA)]

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

Julian Reschke updated JCR-4128:

Labels: candidate_jcr_2_14  (was: )

> update maven plugins and require Maven 3.2.1
> 
>
> Key: JCR-4128
> URL: https://issues.apache.org/jira/browse/JCR-4128
> Project: Jackrabbit Content Repository
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>  Labels: candidate_jcr_2_14
> Fix For: 2.16, 2.15.2
>
>
> As suggested by:
> {noformat}
> mvn versions:display-plugin-updates
> {noformat}



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

Re: [VOTE] Release Apache Jackrabbit Filevault 3.1.40

[Timothee Maret]

+1 (non binding)

Regards,

Timothee

2017-06-22 4:14 GMT+02:00 Tobias Bocanegra :

> Hi,
>
> A candidate for the Jackrabbit Filevault 3.1.40 release is available at:
>
> https://dist.apache.org/repos/dist/dev/jackrabbit/filevault/3.1.40/
>
> The release candidate is a zip archive of the sources in:
>
> https://svn.apache.org/repos/asf/jackrabbit/commons/filevaul
> t/tags/jackrabbit-filevault-3.1.40/
>
> The SHA1 checksum of the archive is 9ce3ed280c2bb42b1823f9fc7f6ff0
> e2168ea166.
>
> A staged Maven repository is available for review at:
>
> https://repository.apache.org/content/repositories/orgapache
> jackrabbit-1256/
>
> Please vote on releasing this package as Apache Jackrabbit Filevault
> 3.1.40.
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 Jackrabbit PMC votes are cast.
>
> [ ] +1 Release this package as Apache Jackrabbit Filevault 3.1.40
> [ ] -1 Do not release this package because...
>