[jira] [Commented] (SLING-7276) Sling Maven Archetype for a Bundle / Content Package project

[ https://issues.apache.org/jira/browse/SLING-7276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16284651#comment-16284651 ] Konrad Windszus commented on SLING-7276: The filevault-package-maven-plugin does no longer require

[jira] [Commented] (SLING-7277) Sling Maven Archetype for a Wrapper Content Package with a Content and Bundle

[ https://issues.apache.org/jira/browse/SLING-7277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16284647#comment-16284647 ] Konrad Windszus commented on SLING-7277: bq. After cleaning up my POMs, further testing and

[jira] [Commented] (SLING-7276) Sling Maven Archetype for a Bundle / Content Package project

[ https://issues.apache.org/jira/browse/SLING-7276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16284455#comment-16284455 ] Andreas Schaefer commented on SLING-7276: - Updated this repository with the merge of

[jira] [Commented] (SLING-7277) Sling Maven Archetype for a Wrapper Content Package with a Content and Bundle

[ https://issues.apache.org/jira/browse/SLING-7277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16284451#comment-16284451 ] Andreas Schaefer commented on SLING-7277: - Pushed all the requested changes to this repo:

[jira] [Commented] (SLING-7277) Sling Maven Archetype for a Wrapper Content Package with a Content and Bundle

[ https://issues.apache.org/jira/browse/SLING-7277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16284412#comment-16284412 ] Andreas Schaefer commented on SLING-7277: - After cleaning up my POMs, further testing and

[jira] [Commented] (SLING-7277) Sling Maven Archetype for a Wrapper Content Package with a Content and Bundle

[ https://issues.apache.org/jira/browse/SLING-7277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16284369#comment-16284369 ] Andreas Schaefer commented on SLING-7277: - Please disregard (for now) my comments above. This

[jira] [Updated] (SLING-7277) Sling Maven Archetype for a Wrapper Content Package with a Content and Bundle

[ https://issues.apache.org/jira/browse/SLING-7277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer updated SLING-7277: Attachment: pom.xml > Sling Maven Archetype for a Wrapper Content Package with a Content

[jira] [Commented] (SLING-7277) Sling Maven Archetype for a Wrapper Content Package with a Content and Bundle

[ https://issues.apache.org/jira/browse/SLING-7277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16284343#comment-16284343 ] Andreas Schaefer commented on SLING-7277: - There is an issue with the Jackrabbit Filevault Package

[jira] [Updated] (SLING-7234) ServiceFactory.getService() resulted in a cycle in sling karaf

[ https://issues.apache.org/jira/browse/SLING-7234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-7234: Attachment: grep-errors.log [~karlpauls], see [^grep-errors.log] – the errors look similar at least

[jira] [Comment Edited] (SLING-7234) ServiceFactory.getService() resulted in a cycle in sling karaf

[ https://issues.apache.org/jira/browse/SLING-7234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16284129#comment-16284129 ] Oliver Lietz edited comment on SLING-7234 at 12/8/17 10:06 PM: --- Scripting

Re: NPE in Oak with PaxExam IT

On Friday 08 December 2017 17:28:27 Konrad Windszus wrote: > I see the following error when executing a test with paxexam > > org.ops4j.pax.exam.TestContainerException: There are unresolved bundles. See > previous ERROR log messages for details. > > The testing.log exposes only one error, namely

[jira] [Commented] (SLING-7234) ServiceFactory.getService() resulted in a cycle in sling karaf

[ https://issues.apache.org/jira/browse/SLING-7234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16284206#comment-16284206 ] Karl Pauls commented on SLING-7234: --- [~olli], hard to say. We did some changes to the classloading so it

[jira] [Commented] (SLING-7234) ServiceFactory.getService() resulted in a cycle in sling karaf

[ https://issues.apache.org/jira/browse/SLING-7234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16284129#comment-16284129 ] Oliver Lietz commented on SLING-7234: - Scripting Core > 2.0.48 is broken and fails on Karaf (update

[jira] [Assigned] (SLING-7234) ServiceFactory.getService() resulted in a cycle in sling karaf

[ https://issues.apache.org/jira/browse/SLING-7234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz reassigned SLING-7234: --- Assignee: Oliver Lietz > ServiceFactory.getService() resulted in a cycle in sling karaf >

NPE in Oak with PaxExam IT

I see the following error when executing a test with paxexam org.ops4j.pax.exam.TestContainerException: There are unresolved bundles. See previous ERROR log messages for details. The testing.log exposes only one error, namely 2017-12-08 17:20:00,138 ERROR [Apache Sling Repository Startup

[jira] [Resolved] (SLING-7010) Switch from configfile to external config

[ https://issues.apache.org/jira/browse/SLING-7010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz resolved SLING-7010. - Resolution: Done > Switch from configfile to external config >

RE: [VOTE] Release Apache Sling Models Impl version 1.4.6

+1

RE: [VOTE] Release Apache Sling Servlets Resolver 2.4.22

+1

[VOTE] Release Apache Sling Models Impl version 1.4.6

Hi, We solved 6 issues in this release: https://issues.apache.org/jira/projects/SLING/versions/12341409 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1831/ You can use this UNIX script to download the release and verify the signatures:

[jira] [Updated] (SLING-7293) testing/tools not migrated to git

[ https://issues.apache.org/jira/browse/SLING-7293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-7293: --- Description: The previous location was

Re: Git repo for sling testing tools?

Created https://issues.apache.org/jira/browse/SLING-7293 to track that. @Robert: Can you have a look? > On 8. Dec 2017, at 16:26, Konrad Windszus wrote: > > > It seems that during the migration also the sling testing tools

[jira] [Created] (SLING-7293) testing/tools not migrated to git

Konrad Windszus created SLING-7293: -- Summary: testing/tools not migrated to git Key: SLING-7293 URL: https://issues.apache.org/jira/browse/SLING-7293 Project: Sling Issue Type: Sub-task

[jira] [Resolved] (SLING-7292) Only add model object to disposal registry if it is not empty

[ https://issues.apache.org/jira/browse/SLING-7292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson resolved SLING-7292. --- Resolution: Fixed Fixed with 56acddf62e55653283d750a938228aea3030b78b > Only add model

Git repo for sling testing tools?

It seems that during the migration also the sling testing tools have not been migrated (sling-org-apache-sling-testing-tools). Originally they have been here: https://github.com/apache/sling-old-svn-mirror/blob/trunk/testing/tools/pom.xml

[jira] [Created] (SLING-7292) Only add model object to disposal registry if it is not empty

Justin Edelson created SLING-7292: - Summary: Only add model object to disposal registry if it is not empty Key: SLING-7292 URL: https://issues.apache.org/jira/browse/SLING-7292 Project: Sling

[jira] [Resolved] (SLING-5668) Models: Leverage ServletRequestListener.requestDestroyed for calling DisposalCallback in case the model was created from a request

[ https://issues.apache.org/jira/browse/SLING-5668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson resolved SLING-5668. --- Resolution: Fixed Assignee: Justin Edelson > Models: Leverage

[GitHub] justinedelson closed pull request #1: SLING-5668 - Leverage ServletRequestListener.requestDestroyed for cal?

justinedelson closed pull request #1: SLING-5668 - Leverage ServletRequestListener.requestDestroyed for cal? URL: https://github.com/apache/sling-org-apache-sling-models-impl/pull/1 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed

[jira] [Commented] (SLING-5668) Models: Leverage ServletRequestListener.requestDestroyed for calling DisposalCallback in case the model was created from a request

[ https://issues.apache.org/jira/browse/SLING-5668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283709#comment-16283709 ] ASF GitHub Bot commented on SLING-5668: --- justinedelson closed pull request #1: SLING-5668 - Leverage

[jira] [Updated] (SLING-5668) Models: Leverage ServletRequestListener.requestDestroyed for calling DisposalCallback in case the model was created from a request

[ https://issues.apache.org/jira/browse/SLING-5668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-5668: -- Fix Version/s: Sling Models Impl 1.4.6 > Models: Leverage

[jira] [Updated] (SLING-7291) HTL to Java compilation might fail under heavy load

[ https://issues.apache.org/jira/browse/SLING-7291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-7291: Description: When there's a high number of concurrent threads accessing the same HTL script that

[jira] [Created] (SLING-7291) HTL to Java compilation might fail under heavy load

Radu Cotescu created SLING-7291: --- Summary: HTL to Java compilation might fail under heavy load Key: SLING-7291 URL: https://issues.apache.org/jira/browse/SLING-7291 Project: Sling Issue Type:

Re: [VOTE] Release Apache Sling Servlets Resolver 2.4.22

+1 regards, Karl On Fri, Dec 8, 2017 at 2:53 PM, Radu Cotescu wrote: > Hi, > > We solved 1 issue in this release: > https://issues.apache.org/jira/projects/SLING/versions/12342287 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-1830

[VOTE] Release Apache Sling Servlets Resolver 2.4.22

Hi, We solved 1 issue in this release: https://issues.apache.org/jira/projects/SLING/versions/12342287 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1830 You can use this UNIX script to download the release and verify the signatures:

[jira] [Closed] (SLING-7287) htl-maven-plugin:validate fails with windows path names

[ https://issues.apache.org/jira/browse/SLING-7287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert closed SLING-7287. - > htl-maven-plugin:validate fails with windows path names >

[jira] [Closed] (SLING-7286) JavaEscapeUtils.makeJavaPackage does not work with windows paths

[ https://issues.apache.org/jira/browse/SLING-7286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert closed SLING-7286. - > JavaEscapeUtils.makeJavaPackage does not work with windows paths >

[RESULT] [VOTE] Release Apache Sling Scripting HTL Java Compiler 1.0.18, HTL Maven Plugin 1.1.2

Hi, The vote has passed with the following result : +1 (binding): Stefan Seifert, Radu Cotescu, Robert Munteanu I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository. stefan

[jira] [Commented] (SLING-7277) Sling Maven Archetype for a Wrapper Content Package with a Content and Bundle

[ https://issues.apache.org/jira/browse/SLING-7277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283246#comment-16283246 ] Stefan Seifert commented on SLING-7277: --- bq. Do I understand that correctly that I still need the