[jira] [Resolved] (SLING-8485) Feature Launcher should keep order of features

[ https://issues.apache.org/jira/browse/SLING-8485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-8485. - Resolution: Fixed > Feature Launcher should keep order of features >

[jira] [Commented] (SLING-8485) Feature Launcher should keep order of features

[ https://issues.apache.org/jira/browse/SLING-8485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16862734#comment-16862734 ] Carsten Ziegeler commented on SLING-8485: - Added an additional fix in e65f12d to keep the

[jira] [Reopened] (SLING-8485) Feature Launcher should keep order of features

[ https://issues.apache.org/jira/browse/SLING-8485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reopened SLING-8485: - > Feature Launcher should keep order of features >

[jira] [Resolved] (SLING-8485) Feature Launcher should keep order of features

[ https://issues.apache.org/jira/browse/SLING-8485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved SLING-8485. --- Resolution: Fixed Done in 3c7c413..9c1494a > Feature Launcher should keep order of features >

[jira] [Created] (SLING-8486) Insights Broken with New Sling Engine

Dan Klco created SLING-8486: --- Summary: Insights Broken with New Sling Engine Key: SLING-8486 URL: https://issues.apache.org/jira/browse/SLING-8486 Project: Sling Issue Type: Bug Affects

[jira] [Created] (SLING-8485) Feature Launcher should keep order of features

Karl Pauls created SLING-8485: - Summary: Feature Launcher should keep order of features Key: SLING-8485 URL: https://issues.apache.org/jira/browse/SLING-8485 Project: Sling Issue Type: Bug

[GitHub] [sling-org-apache-sling-scripting-sightly-models-provider] paul-bjorkstrand opened a new pull request #1: Allow an adaptable argument

paul-bjorkstrand opened a new pull request #1: Allow an adaptable argument URL: https://github.com/apache/sling-org-apache-sling-scripting-sightly-models-provider/pull/1 Allows for the argument `adaptable` to be specified in the use-block, to force the sling model creation to use a

[jira] [Commented] (SLING-7935) Consolidate all 'launchpad-testing' modules into a single git repository

[ https://issues.apache.org/jira/browse/SLING-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16862368#comment-16862368 ] Oliver Lietz commented on SLING-7935: - [~rombert], can we please switch back to individual versions

Sling Feature CP Converter Usage

Hi For now the Content Package Converter worked for me to get a CP based project converted into a FM based Sling instance. That said for the future I am wondering where the CP Converter is heading to. As far as I understand the FM idea is to re-create a Sling instance on every deployment and

[GitHub] [sling-whiteboard] rombert opened a new pull request #35: Added support for okhttp

rombert opened a new pull request #35: Added support for okhttp URL: https://github.com/apache/sling-whiteboard/pull/35 This is an automated message from the Apache Git Service. To respond to the message, please log on to

Re: June board report draft

I kind of missed those steps as well in the past. I thought that this would be automatically done as soon as you push something to dist. Can we aim for a better automation here? Also from the script https://github.com/apache/sling-tooling-release/blob/master/update_reporter.sh

[GitHub] [sling-whiteboard] rombert merged pull request #34: URL connection agent cleanups

rombert merged pull request #34: URL connection agent cleanups URL: https://github.com/apache/sling-whiteboard/pull/34 This is an automated message from the Apache Git Service. To respond to the message, please log on to

Re: June board report draft

Hi Robert, Assuming the latest report was published on March 20th 2019 [0], then the following releases may need to be included. - Testing Sling Mock Oak 2.1.6 - Webconsole Security Provider 1.2.2 - Sling Maven Plugin 2.4.2 - Testing PaxExam 3.0.0 - Sling Default POST Servlets 2.3.30 - Sling

[GitHub] [sling-org-apache-sling-feature-launcher] bosschaert commented on issue #12: SLING-8484 Fail the launcher if not all bundles could be launched

bosschaert commented on issue #12: SLING-8484 Fail the launcher if not all bundles could be launched URL: https://github.com/apache/sling-org-apache-sling-feature-launcher/pull/12#issuecomment-501286863 As discussed on https://issues.apache.org/jira/browse/SLING-8484 we are not doing

[GitHub] [sling-org-apache-sling-feature-launcher] bosschaert closed pull request #12: SLING-8484 Fail the launcher if not all bundles could be launched

bosschaert closed pull request #12: SLING-8484 Fail the launcher if not all bundles could be launched URL: https://github.com/apache/sling-org-apache-sling-feature-launcher/pull/12 This is an automated message from the

[jira] [Resolved] (SLING-8484) Fail the launcher if not all bundles could be launched

[ https://issues.apache.org/jira/browse/SLING-8484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bosschaert resolved SLING-8484. - Resolution: Won't Fix Ok - won't fix then. :) > Fail the launcher if not all bundles

Re: June board report draft

Hi Timothee, On Wed, 2019-06-12 at 15:30 +0200, Timothee Maret wrote: > Hi Robert, > > I am not sure if this is expected or even relevant but the list of > releases > does not seem to include all the items from > https://sling.apache.org/releases.html We should include all releases in the

[jira] [Comment Edited] (SLING-8484) Fail the launcher if not all bundles could be launched

[ https://issues.apache.org/jira/browse/SLING-8484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16862104#comment-16862104 ] Carsten Ziegeler edited comment on SLING-8484 at 6/12/19 1:37 PM: -- I

[jira] [Commented] (SLING-8484) Fail the launcher if not all bundles could be launched

[ https://issues.apache.org/jira/browse/SLING-8484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16862104#comment-16862104 ] Carsten Ziegeler commented on SLING-8484: - I wouldn't recommend launching anything without

[jira] [Comment Edited] (SLING-8484) Fail the launcher if not all bundles could be launched

[ https://issues.apache.org/jira/browse/SLING-8484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16862104#comment-16862104 ] Carsten Ziegeler edited comment on SLING-8484 at 6/12/19 1:35 PM: -- I

Re: June board report draft

Hi Robert, I am not sure if this is expected or even relevant but the list of releases does not seem to include all the items from https://sling.apache.org/releases.html Regards, Timothee Le mer. 12 juin 2019 à 09:56, Robert Munteanu a écrit : > Hi, > > Please find the draft board report

[jira] [Commented] (SLING-8484) Fail the launcher if not all bundles could be launched

[ https://issues.apache.org/jira/browse/SLING-8484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16862091#comment-16862091 ] David Bosschaert commented on SLING-8484: -  {quote} but what situations does the analyzer and the

[jira] [Commented] (SLING-8484) Fail the launcher if not all bundles could be launched

[ https://issues.apache.org/jira/browse/SLING-8484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16862036#comment-16862036 ] Karl Pauls commented on SLING-8484: --- framework start will wait until the beginning startlevel is

[jira] [Commented] (SLING-8484) Fail the launcher if not all bundles could be launched

[ https://issues.apache.org/jira/browse/SLING-8484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16862039#comment-16862039 ] Carsten Ziegeler commented on SLING-8484: - but what situations does the analyzer *and* the system

[jira] [Commented] (SLING-8484) Fail the launcher if not all bundles could be launched

[ https://issues.apache.org/jira/browse/SLING-8484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16862033#comment-16862033 ] David Bosschaert commented on SLING-8484: - I could be wrong, but looking at the documentation of

[jira] [Comment Edited] (SLING-8484) Fail the launcher if not all bundles could be launched

[ https://issues.apache.org/jira/browse/SLING-8484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16862012#comment-16862012 ] Carsten Ziegeler edited comment on SLING-8484 at 6/12/19 11:39 AM: --- I'm

[jira] [Comment Edited] (SLING-8484) Fail the launcher if not all bundles could be launched

[ https://issues.apache.org/jira/browse/SLING-8484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16862007#comment-16862007 ] David Bosschaert edited comment on SLING-8484 at 6/12/19 11:22 AM: --- My

[jira] [Commented] (SLING-8484) Fail the launcher if not all bundles could be launched

[ https://issues.apache.org/jira/browse/SLING-8484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16862012#comment-16862012 ] Carsten Ziegeler commented on SLING-8484: - I'm wondering if this works - I don't think

[jira] [Comment Edited] (SLING-8484) Fail the launcher if not all bundles could be launched

[ https://issues.apache.org/jira/browse/SLING-8484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16862007#comment-16862007 ] David Bosschaert edited comment on SLING-8484 at 6/12/19 11:21 AM: --- My

[jira] [Commented] (SLING-8484) Fail the launcher if not all bundles could be launched

[ https://issues.apache.org/jira/browse/SLING-8484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16862007#comment-16862007 ] David Bosschaert commented on SLING-8484: - My initial implementation checks that after

[GitHub] [sling-org-apache-sling-feature-launcher] bosschaert opened a new pull request #12: SLING-8484 Fail the launcher if not all bundles could be launched

bosschaert opened a new pull request #12: SLING-8484 Fail the launcher if not all bundles could be launched URL: https://github.com/apache/sling-org-apache-sling-feature-launcher/pull/12 This is an automated message from

[jira] [Commented] (SLING-8484) Fail the launcher if not all bundles could be launched

[ https://issues.apache.org/jira/browse/SLING-8484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16861994#comment-16861994 ] Carsten Ziegeler commented on SLING-8484: - My understanding of this issue is that the launcher

[jira] [Commented] (SLING-8484) Fail the launcher if not all bundles could be launched

[ https://issues.apache.org/jira/browse/SLING-8484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16861988#comment-16861988 ] Karl Pauls commented on SLING-8484: --- The important thing for me is that it should be optional as I'm

[jira] [Commented] (SLING-8484) Fail the launcher if not all bundles could be launched

[ https://issues.apache.org/jira/browse/SLING-8484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16861956#comment-16861956 ] Carsten Ziegeler commented on SLING-8484: - Why should it not be the default? > Fail the launcher

[jira] [Commented] (SLING-8481) Caching of Feature Model Analyser Metadata

[ https://issues.apache.org/jira/browse/SLING-8481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16861954#comment-16861954 ] Carsten Ziegeler commented on SLING-8481: - I'm not really worried about the size. Your point

[jira] [Created] (SLING-8484) Fail the launcher if not all bundles could be launched

David Bosschaert created SLING-8484: --- Summary: Fail the launcher if not all bundles could be launched Key: SLING-8484 URL: https://issues.apache.org/jira/browse/SLING-8484 Project: Sling

[jira] [Commented] (SLING-8481) Caching of Feature Model Analyser Metadata

[ https://issues.apache.org/jira/browse/SLING-8481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16861945#comment-16861945 ] David Bosschaert commented on SLING-8481: - On using extensions to record this extra data. I think

[jira] [Comment Edited] (SLING-8481) Caching of Feature Model Analyser Metadata

[ https://issues.apache.org/jira/browse/SLING-8481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16861945#comment-16861945 ] David Bosschaert edited comment on SLING-8481 at 6/12/19 9:39 AM: -- On

[jira] [Commented] (SLING-8251) Support checking dependencies for content packages

[ https://issues.apache.org/jira/browse/SLING-8251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16861867#comment-16861867 ] Simone Tripodi commented on SLING-8251: --- {{slingfeature-maven-plugin}} integration added in

June board report draft

Hi, Please find the draft board report below. I plan to submit it this afternoon (CEST), comments welcome. Thanks, Robert ## Description: Apache Sling™ is a framework for RESTful web-applications based on an extensible content tree. ## Issues: There are no issues requiring board

Re: [RESULT] [VOTE] Release Apache Sling Content Distribution Journal Core 0.1.2 and Content Distribution Journal Kafka 0.1.2

Yes, I think that should be enough. Thanks, Robert On Wed, 2019-06-12 at 09:38 +0200, Carsten Ziegeler wrote: > Ups, it seems I just send it to Timothee and not the list :( > > > Attached is my mail I send, I hope that solves the issue > > > Regards > > Carsten > > > Robert Munteanu

Re: [RESULT] [VOTE] Release Apache Sling Content Distribution Journal Core 0.1.2 and Content Distribution Journal Kafka 0.1.2

Ups, it seems I just send it to Timothee and not the list :( Attached is my mail I send, I hope that solves the issue Regards Carsten Robert Munteanu wrote Hi Timothee, On Mon, 2019-06-10 at 09:54 +0200, Timothee Maret wrote: +1 (binding): Daniel Klco, Carsten Ziegeler, Stefan Seifert

Re: [RESULT] [VOTE] Release Apache Sling Content Distribution Journal Core 0.1.2 and Content Distribution Journal Kafka 0.1.2

Hi Timothee, On Mon, 2019-06-10 at 09:54 +0200, Timothee Maret wrote: > +1 (binding): Daniel Klco, Carsten Ziegeler, Stefan Seifert I do not see an email from Carsten voting for this release, neither in my email client nor at [1]. Robert [1]: