[jira] [Assigned] (SLING-6250) Importing packages with large headers fails

[ https://issues.apache.org/jira/browse/SLING-6250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili reassigned SLING-6250: -- Assignee: Tommaso Teofili (was: Julian Sedding) > Importing packages with large

[jira] [Resolved] (SLING-6439) Filesystem Resource Provider does not support "overlaying" nodes from repository

[ https://issues.apache.org/jira/browse/SLING-6439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert resolved SLING-6439. --- Resolution: Fixed Completed: At revision: 1779048 i've replaced the reference to the (now

[jira] [Resolved] (SLING-6470) Web Console should use "read" service user

[ https://issues.apache.org/jira/browse/SLING-6470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-6470. - Resolution: Fixed Fixed in rev 1779045 > Web Console should use "read" service user >

[jira] [Created] (SLING-6470) Web Console should use "read" service user

Carsten Ziegeler created SLING-6470: --- Summary: Web Console should use "read" service user Key: SLING-6470 URL: https://issues.apache.org/jira/browse/SLING-6470 Project: Sling Issue Type:

[jira] [Updated] (SLING-6469) Resource Resolver Factory does not start if updating from an older version

[ https://issues.apache.org/jira/browse/SLING-6469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-6469: Component/s: ResourceResolver > Resource Resolver Factory does not start if updating from

[jira] [Resolved] (SLING-6469) Resource Resolver Factory does not start if updating from an older version

[ https://issues.apache.org/jira/browse/SLING-6469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-6469. - Resolution: Fixed If such a configuration entry is found it is not converted into the new

[jira] [Created] (SLING-6469) Resource Resolver Factory does not start if updating from an older version

Carsten Ziegeler created SLING-6469: --- Summary: Resource Resolver Factory does not start if updating from an older version Key: SLING-6469 URL: https://issues.apache.org/jira/browse/SLING-6469

[jira] [Commented] (SLING-6466) Rename system user sling-readall and sub service read

[ https://issues.apache.org/jira/browse/SLING-6466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15824154#comment-15824154 ] Carsten Ziegeler commented on SLING-6466: - [~olli] I think keeping separate users is the better

Re: Moving to oak-segment-tar with Oak 1.6?

What happens if a Sling instance using the new format is started on a repository in the old format? Oak won't start but throw an org.apache.jackrabbit.oak.segment.file.InvalidFileStoreVersionException with a message pointing to some more details. Michael A loud & fast failure would have

[jira] [Resolved] (SLING-6468) Improve code coverage for Sling Inventory Printer

[ https://issues.apache.org/jira/browse/SLING-6468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothee Maret resolved SLING-6468. --- Resolution: Fixed > Improve code coverage for Sling Inventory Printer >

[jira] [Commented] (SLING-6468) Improve code coverage for Sling Inventory Printer

[ https://issues.apache.org/jira/browse/SLING-6468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15823994#comment-15823994 ] Timothee Maret commented on SLING-6468: --- Added tests in {{r1779030}} > Improve code coverage for

[jira] [Created] (SLING-6468) Improve code coverage for Sling Inventory Printer

Timothee Maret created SLING-6468: - Summary: Improve code coverage for Sling Inventory Printer Key: SLING-6468 URL: https://issues.apache.org/jira/browse/SLING-6468 Project: Sling Issue

Re: Moving to oak-segment-tar with Oak 1.6?

Hi, On Mon, Jan 16, 2017 at 11:56 AM, Robert Munteanu wrote: > ...I would suggest moving to oak-segment-tar with our current setup,... +1 in general > ...The only downside is that the repository formats are not compatible,... What happens if a Sling instance using the new

Re: [RESULT] [VOTE] Release Apache Sling Tenant version 1.1.0

> > I will copy this release to the Sling dist directory and > promote the artifacts to the central Maven repository. > Actually, could someone from the PMC please copy the release to the Sling dist repository ? Regards, Timothee

[RESULT] [VOTE] Release Apache Sling Tenant version 1.1.0

Hi, The vote has passed with the following result : +1 (binding): Stefan Seifert, Carsten Ziegler, Chetan Mehrotra I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository. Regards, Timothee

Re: Moving to oak-segment-tar with Oak 1.6?

IIUC it is the evolution of oak-segment, but was moved to a separate code-base to give the developers greater (perceived?) freedom to make breaking changes. Correct. The main reason for the new module is to simplify migration where we need to run both versions from the same tool in

Re: [RESULT] [VOTE] Release Apache Sling JSP 2.2.4

Thanks! On Mon, Jan 16, 2017 at 12:12 PM, Robert Munteanu wrote: > On Mon, 2017-01-16 at 12:06 +0100, Julian Sedding wrote: >> @any PMC member: please copy this release to the Sling dist >> directory. > > Done in r17820. > > Robert

Re: Moving to oak-segment-tar with Oak 1.6?

+1 on moving to oak-segment-tar. IIUC it is the evolution of oak-segment, but was moved to a separate code-base to give the developers greater (perceived?) freedom to make breaking changes. As Robert mentions the repository's persistence format has changed and requires a migration. However, these

Re: [VOTE] Release Apache Sling Scripting HTL Compiler 1.0.6, Apache Sling Scripting HTL Java Compiler 1.0.8, Apache Sling Scripting HTL Engine 1.0.30, Apache Sling HTL Maven Plugin 1.0.6

On Fri, 2017-01-13 at 11:56 +, Radu Cotescu wrote: > Please vote to approve this release: +1 Robert signature.asc Description: This is a digitally signed message part

Re: [RESULT] [VOTE] Release Apache Sling JSP 2.2.4

On Mon, 2017-01-16 at 12:06 +0100, Julian Sedding wrote: > @any PMC member: please copy this release to the Sling dist > directory. Done in r17820. Robert

[jira] [Updated] (SLING-6462) Filter Isolated jcr:content nodes (by includes) are not deployed

[ https://issues.apache.org/jira/browse/SLING-6462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-6462: --- Fix Version/s: Sling Eclipse IDE 1.2.0 > Filter Isolated jcr:content nodes (by includes) are

[jira] [Resolved] (SLING-6461) Isolate jcr:content with filter.xml include is not pushed to Server

[ https://issues.apache.org/jira/browse/SLING-6461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-6461. Resolution: Duplicate > Isolate jcr:content with filter.xml include is not pushed to Server

Re: Null checking annotatins for IDE tooling (was: Build failed in Jenkins: sling-ide #88)

On Fri, 2017-01-13 at 12:05 -0800, Andreas Schaefer Sr. wrote: > This is not limited to API. > > There is the issue with impl-vlt that uses the Activator to obtain > the Plugin Logger. > IntelliJ for example is not OSGi based and this caused me some > headaches (and still does). > > But there is

Re: [VOTE] Release Apache Sling Scripting HTL Compiler 1.0.6, Apache Sling Scripting HTL Java Compiler 1.0.8, Apache Sling Scripting HTL Engine 1.0.30, Apache Sling HTL Maven Plugin 1.0.6

+1 On Fri, 13 Jan 2017 at 12:56 Radu Cotescu wrote: > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] 0 Don't care > [ ] -1 Don't release, because ... > > This majority vote is open for at least 72 hours. > > Cheers, > Radu >

[RESULT] [VOTE] Release Apache Sling JSP 2.2.4

Hi all, The vote has passed with the following result: +1 (binding): Robert Munteanu, Carsten Ziegeler, Justin Edelson +1 (non binding): Julian Sedding Thanks for voting. I will promote the artifacts to the central Maven repository and update the news page. @any PMC member: please copy this

Re: [VOTE] Release Apache Sling JSP 2.2.4

+1 (non-binding) Regards Julian On Tue, Jan 10, 2017 at 12:27 PM, Justin Edelson wrote: > +1 > > On Tue, Jan 10, 2017 at 7:34 PM Carsten Ziegeler > wrote: > >> +1 >> >> >> >> >> -- >> Carsten Ziegeler >> Adobe Research Switzerland >>

Moving to oak-segment-tar with Oak 1.6?

Hi, I the Oak 1.6 release cycle a new file-based persistence was introduced, spun off from oak-segment. It's called oak-segment-tar, and to my knowledge it's supposed to be 'oak-segment, but done better'. oak-segment is also deprecated now. I would suggest moving to oak-segment-tar with our

[jira] [Comment Edited] (SLING-6423) Allow for specifying ACL merge mode (ACHandling) in repoinit

[ https://issues.apache.org/jira/browse/SLING-6423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15823765#comment-15823765 ] Bertrand Delacretaz edited comment on SLING-6423 at 1/16/17 10:52 AM: --

[jira] [Commented] (SLING-6423) Allow for specifying ACL merge mode (ACHandling) in repoinit

[ https://issues.apache.org/jira/browse/SLING-6423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15823765#comment-15823765 ] Bertrand Delacretaz commented on SLING-6423: Thanks very much for your contributions! I have

[jira] [Updated] (SLING-6467) Upgrade Oak to 1.6

[ https://issues.apache.org/jira/browse/SLING-6467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-6467: Issue Type: Sub-task (was: Task) Parent: SLING-6194 > Upgrade Oak to 1.6 >

[jira] [Created] (SLING-6467) Upgrade Oak to 1.6

Oliver Lietz created SLING-6467: --- Summary: Upgrade Oak to 1.6 Key: SLING-6467 URL: https://issues.apache.org/jira/browse/SLING-6467 Project: Sling Issue Type: Task Components: JCR,

Re: Jenkins build is still unstable: sling-ide #92

On Tue, 2017-01-10 at 19:23 -0500, Konrad Windszus wrote: > I fixed the previous testing errors in for the sling-ide build 91, > but build 92 fails now in > > org.eclipse.swtbot.swt.finder.widgets.TimeoutException: Timeout > after: 5000 ms.: Could not find auto complete proposal using matcher >

Re: [VOTE] Release Apache Sling Tenant version 1.1.0

+1 Chetan Mehrotra On Thu, Jan 12, 2017 at 7:52 PM, Timothee Maret wrote: > Hi, > > We solved 4 issues in this release: > https://issues.apache.org/jira/browse/SLING/fixforversion/12327647 > > There is still one outstanding issue, SLING-4207, which will be postponed > to the

Re: [VOTE] Release Apache Sling Tenant version 1.1.0

Hi, So far, this issue got two +1 binding votes. Anyone else interested to look at this ? Regards, Timothee 2017-01-12 15:22 GMT+01:00 Timothee Maret : > Hi, > > We solved 4 issues in this release: > https://issues.apache.org/jira/browse/SLING/fixforversion/12327647 > >