Re: Upgrade to Oak 1.7.9

On Friday 13 October 2017 14:17:03 Ian Boston wrote: > Hi, Hi Ian, > On 13 October 2017 at 13:24, Oliver Lietz wrote: > > On Friday 13 October 2017 10:51:31 Ian Boston wrote: > > > Hi, > > > > Hi, > > > > > I would like to upgrade Sling to depend on Oak 1.7.9 as it was

[jira] [Commented] (SLING-7185) Content Parser: Support for ISO-8601

[ https://issues.apache.org/jira/browse/SLING-7185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203851#comment-16203851 ] Jason E Bailey commented on SLING-7185: --- I found the formatting for the date to be odd and specific

Re: Depending on Oak 1.7.x

Hi, The bundles are Sling API Sling ResourceResolver Sling JCR Resource Sling GET Servlets. given these will probably get fixed between now and when Oak 2.0 is released and could end up in a product I don't think an internal release is a viable low risk option. I think the only viable option is

Re: Depending on Oak 1.7.x

Another possible option can be to branch such bundles which depend on Oak API and do unstable releases for them i.e. only odd version release. This would allow implementing parts in Sling which rely on new features implement in Oak trunk Chetan Mehrotra On Fri, Oct 13, 2017 at 8:25 PM, Ian

Re: Upgrade to Oak 1.7.9

Hi, Please ignore this thread now. Upgrading to 1.7.9 is not safe. Oak 1.7.9 is not stable or close to 1.8 and the Oak team has indicated there will be more changes before 1.8 potentially to exported packages. In fact, so many that a discussion thread for Oak 2.0 thread was just started on

Re: Depending on Oak 1.7.x

Hi, On 13 October 2017 at 15:46, Julian Sedding wrote: > AFAIK Oak does not use semantic versioning for packages within uneven > minor version changes (i.e. 1.8 will be baselined against 1.6). This > gives the Oak dev team freedom to experiment with API changes within > the

Re: Depending on Oak 1.7.x

AFAIK Oak does not use semantic versioning for packages within uneven minor version changes (i.e. 1.8 will be baselined against 1.6). This gives the Oak dev team freedom to experiment with API changes within the uneven "development" version (i.e. currently 1.7). Sling, on the other hand uses

Re: [NOTICE] Getting ready to start the SVN → Git migration

I cannot see users@infra either, issues@infra is visible after login. Regards Julian On Fri, Oct 13, 2017 at 11:52 AM, Robert Munteanu wrote: > On Fri, 2017-10-13 at 09:30 +, Stefan Seifert wrote: >> > > What I see is that when I try to go to >> > >

Re: Upgrade to Oak 1.7.9

Hi, On 13 October 2017 at 13:25, Oliver Lietz wrote: > On Friday 13 October 2017 13:00:53 Ian Boston wrote: > > On 13 October 2017 at 11:16, Robert Munteanu wrote: > > > Hi Ian, > > Hi, > > > > On Fri, 2017-10-13 at 10:51 +0100, Ian Boston wrote: > >

Re: Upgrade to Oak 1.7.9

Hi, On 13 October 2017 at 13:24, Oliver Lietz wrote: > On Friday 13 October 2017 10:51:31 Ian Boston wrote: > > Hi, > > Hi, > > > I would like to upgrade Sling to depend on Oak 1.7.9 as it was just > > released. The patch be the same as [1] with 1.7.8 replaced by 1.7.9. >

[jira] [Resolved] (SLING-7198) Duplicated lookup for mapping without subserviceName

[ https://issues.apache.org/jira/browse/SLING-7198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved SLING-7198. --- Resolution: Fixed [~anchela] - nice catch! I removed it in r1812124. Thanks a lot! > Duplicated

[jira] [Assigned] (SLING-7198) Duplicated lookup for mapping without subserviceName

[ https://issues.apache.org/jira/browse/SLING-7198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls reassigned SLING-7198: - Assignee: Karl Pauls > Duplicated lookup for mapping without subserviceName >

[jira] [Updated] (SLING-7198) Duplicated lookup for mapping without subserviceName

[ https://issues.apache.org/jira/browse/SLING-7198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls updated SLING-7198: -- Fix Version/s: Service User Mapper 1.3.6 > Duplicated lookup for mapping without subserviceName >

Re: Upgrade to Oak 1.7.9

On Friday 13 October 2017 13:00:53 Ian Boston wrote: > On 13 October 2017 at 11:16, Robert Munteanu wrote: > > Hi Ian, Hi, > > On Fri, 2017-10-13 at 10:51 +0100, Ian Boston wrote: > > > Hi, > > > I would like to upgrade Sling to depend on Oak 1.7.9 as it was just > > >

[jira] [Updated] (SLING-7198) Duplicated lookup for mapping without subserviceName

[ https://issues.apache.org/jira/browse/SLING-7198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls updated SLING-7198: -- Affects Version/s: Service User Mapper 1.3.4 > Duplicated lookup for mapping without subserviceName >

Re: Upgrade to Oak 1.7.9

On Friday 13 October 2017 10:51:31 Ian Boston wrote: > Hi, Hi, > I would like to upgrade Sling to depend on Oak 1.7.9 as it was just > released. The patch be the same as [1] with 1.7.8 replaced by 1.7.9. > > Any objections ? I prefer sticking to stable and wait for 1.8.0. Regards, O. > Best

Re: Upgrade to Oak 1.7.9

On 13 October 2017 at 11:16, Robert Munteanu wrote: > Hi Ian, > > On Fri, 2017-10-13 at 10:51 +0100, Ian Boston wrote: > > Hi, > > I would like to upgrade Sling to depend on Oak 1.7.9 as it was just > > released. The patch be the same as [1] with 1.7.8 replaced by 1.7.9. > >

[jira] [Created] (SLING-7199) Improve the JcrSystemUserValidatorTest

Karl Pauls created SLING-7199: - Summary: Improve the JcrSystemUserValidatorTest Key: SLING-7199 URL: https://issues.apache.org/jira/browse/SLING-7199 Project: Sling Issue Type: Test

[jira] [Resolved] (SLING-7144) JcrSystemUserValidator should identify disabled users as invalid

[ https://issues.apache.org/jira/browse/SLING-7144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved SLING-7144. --- Resolution: Fixed I think we can resolve this issue. [~anchela], please reopen this issue if I

[jira] [Commented] (SLING-7144) JcrSystemUserValidator should identify disabled users as invalid

[ https://issues.apache.org/jira/browse/SLING-7144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203434#comment-16203434 ] Karl Pauls commented on SLING-7144: --- [~anchela], I looked at your patch and I think it makes a lot of

[jira] [Created] (SLING-7198) Duplicated lookup for mapping without subserviceName

angela created SLING-7198: - Summary: Duplicated lookup for mapping without subserviceName Key: SLING-7198 URL: https://issues.apache.org/jira/browse/SLING-7198 Project: Sling Issue Type: Bug

[jira] [Assigned] (SLING-7144) JcrSystemUserValidator should identify disabled users as invalid

[ https://issues.apache.org/jira/browse/SLING-7144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls reassigned SLING-7144: - Assignee: Karl Pauls > JcrSystemUserValidator should identify disabled users as invalid >

Re: Upgrade to Oak 1.7.9

Hi Ian, On Fri, 2017-10-13 at 10:51 +0100, Ian Boston wrote: > Hi, > I would like to upgrade Sling to depend on Oak 1.7.9 as it was just > released. The patch be the same as [1] with 1.7.8 replaced by 1.7.9. > > Any objections ? No objections here. Related to the pull request - is it required

Re: Depending on Oak 1.7.x

Hi, My View is that it would be dangerous to depend on 1.11.1 but safe to depend on 1.11.25 if 1.11.25 was known to be near to the branch to 1.12.x. The closer to 1.11.1, the greater the risk of instability, the closer to 1.12.x the less the risk. IIUC Oak have started to discuss the possibility

Re: [NOTICE] Getting ready to start the SVN → Git migration

On Fri, 2017-10-13 at 09:30 +, Stefan Seifert wrote: > > > What I see is that when I try to go to > > > https://lists.apache.org/list.html?us...@infra.apache.org, after > > > authenticating, I end up on > > > https://lists.apache.org/list.html?iss...@infra.apache.org > > > > Just to make sure

Upgrade to Oak 1.7.9

Hi, I would like to upgrade Sling to depend on Oak 1.7.9 as it was just released. The patch be the same as [1] with 1.7.8 replaced by 1.7.9. Any objections ? Best Regards Ian 1 https://github.com/apache/sling/compare/trunk...ieb: upgradeToOak178?expand=1

RE: [NOTICE] Getting ready to start the SVN → Git migration

>> What I see is that when I try to go to >> https://lists.apache.org/list.html?us...@infra.apache.org, after >> authenticating, I end up on >> https://lists.apache.org/list.html?iss...@infra.apache.org > >Just to make sure - did you authenticate with your ASF credentials? yes, i did! (but i did

Re: [NOTICE] Getting ready to start the SVN → Git migration

On Thu, 2017-10-12 at 20:55 +, Justin Edelson wrote: > On Thu, Oct 12, 2017 at 4:42 PM Stefan Seifert e> > wrote: > > > > BTW, not sure what the access rule for users@infra are, but you > > > should > > > be able to access

[jira] [Updated] (SLING-7197) API support to get completed Scheduled Job

[ https://issues.apache.org/jira/browse/SLING-7197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praful Vaishnav updated SLING-7197: --- Description: Scheuled jobs are created as _slingevent:TimedEvent_ under path

[jira] [Updated] (SLING-7197) API support to get completed Scheduled Job

[ https://issues.apache.org/jira/browse/SLING-7197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praful Vaishnav updated SLING-7197: --- Description: Scheuled jobs are created as _slingevent:TimedEvent_ under path

[jira] [Created] (SLING-7197) API support to get completed Scheduled Job

Praful Vaishnav created SLING-7197: -- Summary: API support to get completed Scheduled Job Key: SLING-7197 URL: https://issues.apache.org/jira/browse/SLING-7197 Project: Sling Issue Type: Bug

Re: [VOTE] Release Apache Sling Servlet Helpers 1.0.2, Servlet Helpers 1.1.2, JCR Mock 1.3.2, ResourceResolver Mock 1.1.20, OSGi Mock 1.9.8, OSGi Mock 2.3.4, Sling Mock 1.9.10, Sling Mock 2.2.14

On Thu, 2017-10-12 at 20:33 +, Stefan Seifert wrote: > Please vote to approve this release: +1 Robert signature.asc Description: This is a digitally signed message part