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

+1 On Thu, Oct 12, 2017 at 4:34 PM, Stefan Seifert wrote: > +1 > > >

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

On Thu, Oct 12, 2017 at 4:42 PM Stefan Seifert wrote: > >BTW, not sure what the access rule for users@infra are, but you should > >be able to access https://lists.apache.org/list.html?users@infra.apache > >.org and then log in with your ASF credentials. I think it works

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

>BTW, not sure what the access rule for users@infra are, but you should >be able to access https://lists.apache.org/list.html?users@infra.apache >.org and then log in with your ASF credentials. I think it works for >committers. even if i login: i cannot access

[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

Hi, Apache Sling Servlet Helpers 1.0.2 (3 issues) https://issues.apache.org/jira/browse/SLING/fixforversion/12340953 Apache Sling Servlet Helpers 1.1.2 (3 issues) https://issues.apache.org/jira/browse/SLING/fixforversion/12338261 Apache Sling Testing JCR Mock 1.3.2 (1 issue)

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

+1

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

Hi Stefan, On Thu, 2017-10-12 at 16:18 +, Stefan Seifert wrote: > if i get it correctly the git migration is still suspended - and all > commits can go to svn as usual. > > a discussion about the huge number of sling git repos was started in >

Re: [VOTE] Release Apache Sling Discovery Oak 1.2.22

+1 On Wed, Oct 11, 2017 at 3:27 PM, Stefan Seifert wrote: > +1 > > >

[jira] [Resolved] (SLING-7195) Sling Mock Oak not working with AEM uber-jar 6.3.0

[ https://issues.apache.org/jira/browse/SLING-7195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert resolved SLING-7195. --- Resolution: Not A Problem > Sling Mock Oak not working with AEM uber-jar 6.3.0 >

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

if i get it correctly the git migration is still suspended - and all commits can go to svn as usual. a discussion about the huge number of sling git repos was started in https://issues.apache.org/jira/browse/INFRA-15229 but then continued on users@infra list - afaik i've no access on this

[jira] [Commented] (SLING-7195) Sling Mock Oak not working with AEM uber-jar 6.3.0

[ https://issues.apache.org/jira/browse/SLING-7195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16202193#comment-16202193 ] Jens Lauterbach commented on SLING-7195: Just for other people finding this: Even if you fix the

[jira] [Resolved] (SLING-7196) sling-mock: Make sure SlingContext.registerAdapter can overlay built-in adaptions

[ https://issues.apache.org/jira/browse/SLING-7196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert resolved SLING-7196. --- Resolution: Fixed Completed: At revision: 1811988 > sling-mock: Make sure

[jira] [Created] (SLING-7196) sling-mock: Make sure SlingContext.registerAdapter can overlay built-in adaptions

Stefan Seifert created SLING-7196: - Summary: sling-mock: Make sure SlingContext.registerAdapter can overlay built-in adaptions Key: SLING-7196 URL: https://issues.apache.org/jira/browse/SLING-7196

[jira] [Commented] (SLING-7195) Sling Mock Oak not working with AEM uber-jar 6.3.0

[ https://issues.apache.org/jira/browse/SLING-7195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16202137#comment-16202137 ] Jens Lauterbach commented on SLING-7195: Ok. I found out how to fix this with {{aem-mock}}. It did

[jira] [Comment Edited] (SLING-7195) Sling Mock Oak not working with AEM uber-jar 6.3.0

[ https://issues.apache.org/jira/browse/SLING-7195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16202121#comment-16202121 ] Jens Lauterbach edited comment on SLING-7195 at 10/12/17 3:48 PM: -- I just

[jira] [Resolved] (SLING-7193) osgi-mock: MockServiceReferences.compareTo reverses ordering

[ https://issues.apache.org/jira/browse/SLING-7193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert resolved SLING-7193. --- Resolution: Fixed Fix Version/s: Testing OSGi Mock 2.3.4 Testing

[jira] [Commented] (SLING-7195) Sling Mock Oak not working with AEM uber-jar 6.3.0

[ https://issues.apache.org/jira/browse/SLING-7195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16202125#comment-16202125 ] Stefan Seifert commented on SLING-7195: --- that's no problem, just give it a try (with dependency to

[jira] [Comment Edited] (SLING-7195) Sling Mock Oak not working with AEM uber-jar 6.3.0

[ https://issues.apache.org/jira/browse/SLING-7195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16202121#comment-16202121 ] Jens Lauterbach edited comment on SLING-7195 at 10/12/17 3:45 PM: -- I just

[jira] [Commented] (SLING-7195) Sling Mock Oak not working with AEM uber-jar 6.3.0

[ https://issues.apache.org/jira/browse/SLING-7195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16202121#comment-16202121 ] Jens Lauterbach commented on SLING-7195: I just checked the poms for

[jira] [Updated] (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 updated SLING-7144: -- Fix Version/s: JCR Resource 3.0.6 > JcrSystemUserValidator should identify disabled users as invalid >

[jira] [Updated] (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 updated SLING-7144: -- Affects Version/s: JCR Resource 3.0.4 > JcrSystemUserValidator should identify disabled users as

Re: Depending on Oak 1.7.x

Hi, I’m curious to explore the reasoning behind the general principle of only having dependencies on stable Oak releases. Of course I understand the importance of keeping the codebase on a solid foundation and thus to want stable releases for dependencies. My question is, what exactly is meant

Re: Build failed in Jenkins: sling-launchpad-builder-1.8 #10656

On Thu, 2017-10-12 at 15:21 +, Apache Jenkins Server wrote: > Updating https://svn.apache.org/repos/asf/sling/trunk/launchpad/build > er at revision '2017-10-12T15:21:10.206 +' > ERROR: Failed to update https://svn.apache.org/repos/asf/sling/trunk/ > launchpad/builder >

[jira] [Commented] (SLING-7195) Sling Mock Oak not working with AEM uber-jar 6.3.0

[ https://issues.apache.org/jira/browse/SLING-7195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16202102#comment-16202102 ] Stefan Seifert commented on SLING-7195: --- if you are working with AEM i recommend to directly use

[jira] [Updated] (SLING-7195) Sling Mock Oak not working with AEM uber-jar 6.3.0

[ https://issues.apache.org/jira/browse/SLING-7195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jens Lauterbach updated SLING-7195: --- Description: When running unit tests using the Sling Mock Oak repository the tests will fail

[jira] [Updated] (SLING-7195) Sling Mock Oak not working with AEM uber-jar 6.3.0

[ https://issues.apache.org/jira/browse/SLING-7195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jens Lauterbach updated SLING-7195: --- Attachment: sling-7195-demo.zip Added demo project to help reproduce error. > Sling Mock Oak

[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=16202099#comment-16202099 ] angela commented on SLING-7144: --- [~marett], ping :-) If the Sling community is not fixing this bug I will

[jira] [Updated] (SLING-7195) Sling Mock Oak not working with AEM uber-jar 6.3.0

[ https://issues.apache.org/jira/browse/SLING-7195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jens Lauterbach updated SLING-7195: --- Description: When running unit tests using the Sling Mock Oak repository the tests will fail

[adapter] wrong service ranking in AdapterManager implementation

see https://issues.apache.org/jira/browse/SLING-7194 for details. does anyone has a clue if the current implementation that favors services with lowest ranking when picking the adapter factory if multiple exists was done by intention? i would assume the same logic which is done by

[jira] [Created] (SLING-7195) Sling Mock Oak not working with AEM uber-jar 6.3.0

Jens Lauterbach created SLING-7195: -- Summary: Sling Mock Oak not working with AEM uber-jar 6.3.0 Key: SLING-7195 URL: https://issues.apache.org/jira/browse/SLING-7195 Project: Sling Issue

[jira] [Created] (SLING-7194) AdapterManager sorts AdapterFactory implementations lowest ranking first

Stefan Seifert created SLING-7194: - Summary: AdapterManager sorts AdapterFactory implementations lowest ranking first Key: SLING-7194 URL: https://issues.apache.org/jira/browse/SLING-7194 Project:

[GitHub] sling pull request #254: Fixed build broken by missing SNAPSHOTS.

Github user rombert closed the pull request at: https://github.com/apache/sling/pull/254 ---

[GitHub] sling pull request #254: Fixed build broken by missing SNAPSHOTS.

GitHub user ieb opened a pull request: https://github.com/apache/sling/pull/254 Fixed build broken by missing SNAPSHOTS. Take 2 Able to merge. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ieb/sling brokenBuild Alternatively

[GitHub] sling pull request #253: Fixes a broken build caused by missing SNAPSHOT bui...

Github user ieb closed the pull request at: https://github.com/apache/sling/pull/253 ---

[jira] [Created] (SLING-7193) osgi-mock: MockServiceReferences.compareTo reverses ordering

Stefan Seifert created SLING-7193: - Summary: osgi-mock: MockServiceReferences.compareTo reverses ordering Key: SLING-7193 URL: https://issues.apache.org/jira/browse/SLING-7193 Project: Sling

Re: Depending on Oak 1.7.x

Hi, Here is a patch to make Sling work with Oak 1.7.8. Once I fixed a full build (just did a pull request) it passes a full IT build. The patch updates the paxexam setup so IT tests that uses that will test against Oak 1.7.8. I also tested with 1.8-SNAPSHOT so this should be good for anything

[GitHub] sling pull request #253: Fixes a broken build caused by missing SNAPSHOT bui...

GitHub user ieb opened a pull request: https://github.com/apache/sling/pull/253 Fixes a broken build caused by missing SNAPSHOT builds. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ieb/sling brokenBuild Alternatively you can

Re: [sling-site] branch master updated: Avoid encoding issues

I guess AddDefaultEncoding is just not allowed in the .htaccess file. So we could either ask INFRA to set that globally for the Sling Website or rely on the meta tag http-equiv like Apache Ant is doing: http://ant.apache.org/. That would also have the advantage that the local preview would work

Re: Sling build broken for me.

On Thu, 2017-10-12 at 12:54 +0100, Ian Boston wrote: > > I'll set the Jenkins jobs to also build regularly. Note that a full > > reactor build is not something I am keen on doing since: > > > > - it takes a long time > > - if one module in the reactor fails the build is aborted > > > > Would

Re: Sling build broken for me.

Hi, On 12 October 2017 at 11:52, Robert Munteanu wrote: > Hi Ian, > > On Thu, 2017-10-12 at 11:26 +0100, Ian Boston wrote: > > Hi, > > 2 observations going through the upgrade process from Oak 1.6 to Oak > > 1.7/1.8 using the full build to verify. > > > > Most of the build

Re: [sling-site] branch master updated: Avoid encoding issues

According to https://reference.apache.org/committer/website there should be a .revision file at the root of the site, but I couldn't find it. So most probably you have to open an INFRA ticket to ask why the change in .htaccess is not having any effect. Konrad > On 12. Oct 2017, at 13:20, Julian

[jira] [Resolved] (SLING-7191) Configure build jobs to also build periodically

[ https://issues.apache.org/jira/browse/SLING-7191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-7191. Resolution: Fixed Fixed in https://svn.apache.org/r1811938 > Configure build jobs to also

Re: [sling-site] branch master updated: Avoid encoding issues

On Thu, Oct 12, 2017 at 12:08 PM, Konrad Windszus wrote: > ...If we are really afraid that those characters are messed up by editors > which assume the wrong encoding, we can > enforce the encoding with > http://www.mojohaus.org/extra-enforcer-rules/requireEncoding.html

[jira] [Resolved] (SLING-7192) Move testing/samples to samples/testing

[ https://issues.apache.org/jira/browse/SLING-7192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-7192. Resolution: Fixed Done in https://svn.apache.org/r1811942 > Move testing/samples to

[jira] [Created] (SLING-7192) Move testing/samples to samples/testing

Robert Munteanu created SLING-7192: -- Summary: Move testing/samples to samples/testing Key: SLING-7192 URL: https://issues.apache.org/jira/browse/SLING-7192 Project: Sling Issue Type:

Re: [sling-site] branch master updated: Avoid encoding issues

I expected my change to cause the Content-Type header of HTML pages being set to "text/html;charset=utf-8", which is not (yet) the case. DO we have any way to know if a change has made it to the live site, or looking at what Apache httpd is doing with out .htacess file? @Konrad: I also saw the

Re: Sling build broken for me.

Hi Ian, On Thu, 2017-10-12 at 11:26 +0100, Ian Boston wrote: > Hi, > 2 observations going through the upgrade process from Oak 1.6 to Oak > 1.7/1.8 using the full build to verify. > > Most of the build breakages are due to a bundle being release but its > reference not being updated, some are

[jira] [Created] (SLING-7191) Configure build jobs to also build periodically

Robert Munteanu created SLING-7191: -- Summary: Configure build jobs to also build periodically Key: SLING-7191 URL: https://issues.apache.org/jira/browse/SLING-7191 Project: Sling Issue

Re: Sling build broken for me.

On Wed, 2017-10-11 at 21:56 +0200, Karl Pauls wrote: > > Would it help if we added weekly builds for all modules, > > irrespective > > if any changes are present? > > Yes, I think that would be a good start. Ultimately, I still think we > should get this "run integration tests with all bundles

[jira] [Comment Edited] (SLING-7190) i18n translations not updated unless bundle is restarted

[ https://issues.apache.org/jira/browse/SLING-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16201762#comment-16201762 ] Konrad Windszus edited comment on SLING-7190 at 10/12/17 10:27 AM: --- If I

[jira] [Commented] (SLING-7190) i18n translations not updated unless bundle is restarted

[ https://issues.apache.org/jira/browse/SLING-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16201762#comment-16201762 ] Konrad Windszus commented on SLING-7190: If I understand correctly, it used to work with Sling

Re: Sling build broken for me.

Hi, 2 observations going through the upgrade process from Oak 1.6 to Oak 1.7/1.8 using the full build to verify. Most of the build breakages are due to a bundle being release but its reference not being updated, some are subtle. The 9-SNAPSHOT that started this thread is obvious but hard to

Re: [sling-site] branch master updated: Avoid encoding issues

I would also be in very strong favour of not using strange escape sequences and instead directly use UTF-8 sources. I guess the default encoding for the templates is anyhow UTF-8, but we can also set that explicitly (http://jbake.org/docs/2.4.0/#default_encoding_for_templates). If we are

Re: [VOTE] Release Apache Sling Maven Sling Plugin 2.3.4

On Wed, 2017-10-11 at 19:23 +, Stefan Seifert wrote: > Please vote to approve this release: +1 Robert signature.asc Description: This is a digitally signed message part

Re: [sling-site] branch master updated: Avoid encoding issues

Hi Bertrand Fair enough, I'll leave the template as-is. Personally, I prefer UTF-8 across the whole stack, in good old WYSIWYG manner ;) I have pushed a change only to .htaccess now. Regards Julian On Wed, Oct 11, 2017 at 2:29 PM, Bertrand Delacretaz wrote: > Hi