[jira] [Commented] (SLING-8704) Build PRs from non-committers
[ https://issues.apache.org/jira/browse/SLING-8704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17161729#comment-17161729 ] Konrad Windszus commented on SLING-8704: With ASF migrating to Cloudbees (SLING-9594) this may be supported OOTB... > Build PRs from non-committers > - > > Key: SLING-8704 > URL: https://issues.apache.org/jira/browse/SLING-8704 > Project: Sling > Issue Type: Improvement > Components: Build and Source Control >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > > As outlined in > https://issues.apache.org/jira/browse/INFRA-18748?focusedCommentId=16885091&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16885091 > and discussed in > https://lists.apache.org/thread.html/7ba9424ae1cadd61363a5c6e7d12dec9f5b424b1f68e27915032fbab@%3Cprivate.infra.apache.org%3E > it is no longer allowed to automatically build PRs from non-committers on > ASF infra. > Therefore another solution needs to be found to be able to validate PRs from > contributors. This validation should include at least a Maven build and the > validation of SonarQube rules. > Several options come to my mind > # Use CloudBees Code Ship https://app.codeship.com/home. Currently it is > unclear whether there is a dedicated ASF account. I asked about it in > https://issues.apache.org/jira/browse/INFRA-18973. Preferred option as > probably the Jenkinsfile can be reused. > # Use Travis CI. There is a dedicated ASF account but it a) needs to be > enabled by INFRA per project and b) requires to maintain another build script > next to the Jenkinsfile we already have > # Use another 3rd party build provider > This was also discussed during the Sling Hackathon 2019 > (https://lists.apache.org/thread.html/fb675eda239779450943623490e5a232786464df1dfb1feac5ec4ee0@%3Cdev.sling.apache.org%3E). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (SLING-9594) Move Sling builds to ci-builds.apache.org
[ https://issues.apache.org/jira/browse/SLING-9594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17161726#comment-17161726 ] Konrad Windszus commented on SLING-9594: I requested creation of a folder for Sling in https://lists.apache.org/x/thread.html/rbac05aa7a5b8d00f601d4bd1f2faf655f7f307681bb73f7c39fcbd6a@%3Cbuilds.apache.org%3E > Move Sling builds to ci-builds.apache.org > - > > Key: SLING-9594 > URL: https://issues.apache.org/jira/browse/SLING-9594 > Project: Sling > Issue Type: Task > Components: Build and Source Control >Reporter: Robert Munteanu >Priority: Critical > > The ASF Jenkins infrastructure is moving to to a new > Cloudbees based Client Master called https://ci-builds.apache.org, see > https://lists.apache.org/thread.html/re974eed417a1bc294694701d5c91b4bf92689fcf32a4c91f169be87d%40%3Cbuilds.apache.org%3E > . The migrations of all jobs needs to be done before the switch off date of > 15th August 2020, so we have a maximum about three weeks from now to make the > move. > There is no automatic way of migrating the jobs, but thankfully our current > set up is very much automated and reasonably well documented at > https://cwiki.apache.org/confluence/display/SLING/Sling+Jenkins+Setup . > It very well may be that we can simply set up another GitHub org on the new > Jenkins master, provide the secrets and be done with it. But it needs > investigation though. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [sling-org-apache-sling-feature-analyser] sonarcloud[bot] commented on pull request #23: SLING-9597 Feature Analyser should substitute {dollar} before passing properties to framework
sonarcloud[bot] commented on pull request #23: URL: https://github.com/apache/sling-org-apache-sling-feature-analyser/pull/23#issuecomment-661226165 Kudos, SonarCloud Quality Gate passed! [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-analyser&pullRequest=23&resolved=false&types=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-analyser&pullRequest=23&resolved=false&types=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-analyser&pullRequest=23&resolved=false&types=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-analyser&pullRequest=23&resolved=false&types=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-analyser&pullRequest=23&resolved=false&types=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-analyser&pullRequest=23&resolved=false&types=VULNERABILITY) (and [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-analyser&pullRequest=23&reso lved=false&types=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-analyser&pullRequest=23&resolved=false&types=SECURITY_HOTSPOT) to review) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-analyser&pullRequest=23&resolved=false&types=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-analyser&pullRequest=23&resolved=false&types=CODE_SMELL) [1 Code Smell](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-analyser&pullRequest=23&resolved=false&types=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-feature-analyser&pullRequest=23&metric=new_coverage&view=list) [100.0% Coverage](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-feature-analyser&pullRequest=23&metric=new_coverage&view=list) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-feature-analyser&pullRequest=23&metric=new_duplicated_lines_density&view=list) [0.0% Duplication](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-feature-analyser&pullRequest=23&metric=new_duplicated_lines_density&view=list) The version of Java (1.8.0_252) you have used to run this analysis is deprecated and we will stop accepting it from October 2020. Please update to at least Java 11. Read more [here](https://sonarcloud.io/documentation/upcoming/) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-feature-analyser] bosschaert opened a new pull request #23: SLING-9597 Feature Analyser should substitute {dollar} before passing properties to framework
bosschaert opened a new pull request #23: URL: https://github.com/apache/sling-org-apache-sling-feature-analyser/pull/23 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (SLING-9597) Feature Analyser should substitute {dollar} before passing properties to framework
[
https://issues.apache.org/jira/browse/SLING-9597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
A. J. David Bosschaert updated SLING-9597:
--
Description: The feature model launcher substitutes the placeholder
\{dollar} into a {{$}} before it passes framework properties to the framework.
The analyser does not do this yet when it launches the framework. It should
behave the same. (was: The feature model launcher substitutes the placeholder
{{{dollar}}} into a {{$}} before it passes framework properties to the
framework. The analyser does not do this yet when it launches the framework. It
should behave the same.)
> Feature Analyser should substitute {dollar} before passing properties to
> framework
> --
>
> Key: SLING-9597
> URL: https://issues.apache.org/jira/browse/SLING-9597
> Project: Sling
> Issue Type: Bug
> Components: Feature Model Analyser
>Affects Versions: Feature Model Analyser 1.3.2
>Reporter: A. J. David Bosschaert
>Assignee: A. J. David Bosschaert
>Priority: Major
> Fix For: Feature Model Analyser 1.3.4
>
>
> The feature model launcher substitutes the placeholder \{dollar} into a {{$}}
> before it passes framework properties to the framework. The analyser does not
> do this yet when it launches the framework. It should behave the same.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (SLING-9597) Feature Analyser should substitute {dollar} before passing properties to framework
[
https://issues.apache.org/jira/browse/SLING-9597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
A. J. David Bosschaert reassigned SLING-9597:
-
Assignee: A. J. David Bosschaert
> Feature Analyser should substitute {dollar} before passing properties to
> framework
> --
>
> Key: SLING-9597
> URL: https://issues.apache.org/jira/browse/SLING-9597
> Project: Sling
> Issue Type: Bug
> Components: Feature Model Analyser
>Affects Versions: Feature Model Analyser 1.3.2
>Reporter: A. J. David Bosschaert
>Assignee: A. J. David Bosschaert
>Priority: Major
> Fix For: Feature Model Analyser 1.3.4
>
>
> The feature model launcher substitutes the placeholder {{{dollar}}} into a
> {{$}} before it passes framework properties to the framework. The analyser
> does not do this yet when it launches the framework. It should behave the
> same.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (SLING-9597) Feature Analyser should substitute {dollar} before passing properties to framework
A. J. David Bosschaert created SLING-9597:
-
Summary: Feature Analyser should substitute {dollar} before
passing properties to framework
Key: SLING-9597
URL: https://issues.apache.org/jira/browse/SLING-9597
Project: Sling
Issue Type: Bug
Components: Feature Model Analyser
Affects Versions: Feature Model Analyser 1.3.2
Reporter: A. J. David Bosschaert
Fix For: Feature Model Analyser 1.3.4
The feature model launcher substitutes the placeholder {{{dollar}}} into a
{{$}} before it passes framework properties to the framework. The analyser does
not do this yet when it launches the framework. It should behave the same.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (SLING-9595) Fully switch starter build to the feature model
[ https://issues.apache.org/jira/browse/SLING-9595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-9595: --- Description: Fully switch starter to feature model: - The feature model converter will be used to create individual feature files out of the provisioning model files - Feature model aggregates will be defined for the current run modes: oak_tar and oak_mongo - Feature model analysers will be configured for the main aggregates - Produce feature archives for oak_tar and oak_mongo - Produce a kickstart jar was: Fully switch starter to provisioning model: - The feature model converter will be used to create individual feature files out of the provisioning model files - Feature model aggregates will be defined for the current run modes: oak_tar and oak_mongo - Feature model analysers will be configured for the main aggregates - Produce feature archives for oak_tar and oak_mongo - Produce a kickstart jar > Fully switch starter build to the feature model > --- > > Key: SLING-9595 > URL: https://issues.apache.org/jira/browse/SLING-9595 > Project: Sling > Issue Type: Sub-task > Components: Starter >Reporter: Robert Munteanu >Assignee: Robert Munteanu >Priority: Major > Fix For: Starter 12 > > > Fully switch starter to feature model: > - The feature model converter will be used to create individual feature files > out of the provisioning model files > - Feature model aggregates will be defined for the current run modes: oak_tar > and oak_mongo > - Feature model analysers will be configured for the main aggregates > - Produce feature archives for oak_tar and oak_mongo > - Produce a kickstart jar -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SLING-9595) Fully switch starter build to the feature model
[ https://issues.apache.org/jira/browse/SLING-9595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-9595: --- Summary: Fully switch starter build to the feature model (was: Switch Starter to the Provisioning model) > Fully switch starter build to the feature model > --- > > Key: SLING-9595 > URL: https://issues.apache.org/jira/browse/SLING-9595 > Project: Sling > Issue Type: Sub-task > Components: Starter >Reporter: Robert Munteanu >Assignee: Robert Munteanu >Priority: Major > Fix For: Starter 12 > > > Fully switch starter to provisioning model: > - The feature model converter will be used to create individual feature files > out of the provisioning model files > - Feature model aggregates will be defined for the current run modes: oak_tar > and oak_mongo > - Feature model analysers will be configured for the main aggregates > - Produce feature archives for oak_tar and oak_mongo > - Produce a kickstart jar -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SLING-9596) Switch launchpad-testing to the feature model
Robert Munteanu created SLING-9596: -- Summary: Switch launchpad-testing to the feature model Key: SLING-9596 URL: https://issues.apache.org/jira/browse/SLING-9596 Project: Sling Issue Type: Sub-task Components: Launchpad, Testing Reporter: Robert Munteanu Fix For: Launchpad Testing 12 Switch launchpad testing to provisioning model: - provisioning files switched to feature files - run against the starter using feature model -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SLING-9595) Switch Starter to the Provisioning model
Robert Munteanu created SLING-9595: -- Summary: Switch Starter to the Provisioning model Key: SLING-9595 URL: https://issues.apache.org/jira/browse/SLING-9595 Project: Sling Issue Type: Sub-task Components: Starter Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Starter 12 Fully switch starter to provisioning model: - The feature model converter will be used to create individual feature files out of the provisioning model files - Feature model aggregates will be defined for the current run modes: oak_tar and oak_mongo - Feature model analysers will be configured for the main aggregates - Produce feature archives for oak_tar and oak_mongo - Produce a kickstart jar -- This message was sent by Atlassian Jira (v8.3.4#803005)
[Jenkins] Sling » sling-org-apache-sling-launchpad-testing » master #926 is FIXED
Please see https://builds.apache.org/job/Sling/job/sling-org-apache-sling-launchpad-testing/job/master/926/ for details. No further emails will be sent until the status of the build is changed.
[jira] [Closed] (SLING-9425) Analyser fails when bundle requires Java 11
[
https://issues.apache.org/jira/browse/SLING-9425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
A. J. David Bosschaert closed SLING-9425.
-
> Analyser fails when bundle requires Java 11
> ---
>
> Key: SLING-9425
> URL: https://issues.apache.org/jira/browse/SLING-9425
> Project: Sling
> Issue Type: Bug
> Components: Feature Model Analyser
>Reporter: Robert Munteanu
>Assignee: A. J. David Bosschaert
>Priority: Major
> Fix For: Feature Model Analyser 1.3.2
>
>
> I am trying to build an app with the feature model and Java 11. The app is a
> a single project which produces the bundle and the feature model.
> When building the app the analyser fails with
> {noformat}[ERROR] Artifact FOO requires [FOO] osgi.ee;
> filter:="(&(osgi.ee=JavaSE)(version=11))" in start level 0 but no artifact is
> providing a matching capability in this start level.{noformat}
> I was able to cheat my way out of this by providing a static capability for
> the framework:
> {noformat}org.osgi.framework.system.capabilities": "osgi.ee;
> osgi.ee=\"JavaSE\";version:List=\"1.0,1.1,1.2,1.3,1.4,1.5,1.6,1.7,1.8,9,10,11\"{noformat}
> but there should be better ways.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (SLING-9575) Existing API Regions with factory Pids are not found
[ https://issues.apache.org/jira/browse/SLING-9575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. J. David Bosschaert closed SLING-9575. - > Existing API Regions with factory Pids are not found > > > Key: SLING-9575 > URL: https://issues.apache.org/jira/browse/SLING-9575 > Project: Sling > Issue Type: Bug > Components: Feature Model >Affects Versions: Feature Model API Regions Runtime Fragment 1.1.4 >Reporter: A. J. David Bosschaert >Assignee: A. J. David Bosschaert >Priority: Major > Fix For: Feature Model API Regions Runtime Fragment 1.1.6 > > > Configuration for the API Regions fragment can be dynamically provided > through factory configurations. > On restart the API Regions fragment looks these configurations up to re-apply > them. This lookup on restart always fails. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (SLING-9566) Allow to specify classifier for source artifact
[ https://issues.apache.org/jira/browse/SLING-9566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. J. David Bosschaert closed SLING-9566. - > Allow to specify classifier for source artifact > --- > > Key: SLING-9566 > URL: https://issues.apache.org/jira/browse/SLING-9566 > Project: Sling > Issue Type: Improvement > Components: Feature Model, Maven Plugins and Archetypes >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Major > Fix For: slingfeature-maven-plugin 1.3.10 > > > To get the sources for the api generation, the standard Maven classifier > "sources" is used. However, some projects use a different classifier like > "source-release", or "source" etc. > We can add a configuration to allow to change just the classifier -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (SLING-9565) Add framework from execution environment to repository
[ https://issues.apache.org/jira/browse/SLING-9565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. J. David Bosschaert closed SLING-9565. - > Add framework from execution environment to repository > -- > > Key: SLING-9565 > URL: https://issues.apache.org/jira/browse/SLING-9565 > Project: Sling > Issue Type: Improvement > Components: Feature Model, Maven Plugins and Archetypes >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Major > Fix For: slingfeature-maven-plugin 1.3.10 > > > With the new extension for the execution environment, we should also add the > framework artifact (if specified) to the repository created by the repository > goal -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (SLING-9568) Enhance package report to include package version and artifact
[ https://issues.apache.org/jira/browse/SLING-9568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. J. David Bosschaert closed SLING-9568. - > Enhance package report to include package version and artifact > -- > > Key: SLING-9568 > URL: https://issues.apache.org/jira/browse/SLING-9568 > Project: Sling > Issue Type: Improvement > Components: Feature Model, Maven Plugins and Archetypes >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Major > Fix For: slingfeature-maven-plugin 1.3.10 > > > The package report currently only reports package names. We should add > package version and the source (artifact) the package is exported from -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (SLING-9570) jarStartOrder can only be set for FMs in the source folder
[ https://issues.apache.org/jira/browse/SLING-9570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. J. David Bosschaert closed SLING-9570. - > jarStartOrder can only be set for FMs in the source folder > -- > > Key: SLING-9570 > URL: https://issues.apache.org/jira/browse/SLING-9570 > Project: Sling > Issue Type: Bug > Components: Maven Plugins and Archetypes >Reporter: amin abromand >Assignee: Carsten Ziegeler >Priority: Minor > Fix For: slingfeature-maven-plugin 1.3.10 > > > During include-artifact mojo execution the start level for the attached > jar/bundle can be set through jarStartOrder. > This is only working for FM files inside the source folder. For created FMs > the jar/bundle does not receive the jarStartOrder. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (SLING-9567) NullPointerException in info mojo
[ https://issues.apache.org/jira/browse/SLING-9567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. J. David Bosschaert closed SLING-9567. - > NullPointerException in info mojo > - > > Key: SLING-9567 > URL: https://issues.apache.org/jira/browse/SLING-9567 > Project: Sling > Issue Type: Bug > Components: Maven Plugins and Archetypes >Affects Versions: slingfeature-maven-plugin 1.3.8 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Major > Fix For: slingfeature-maven-plugin 1.3.10 > > > When the info mojo is used in standalone mode, the following > NullPointerException occurs: > Caused by: java.lang.NullPointerException > at org.apache.sling.feature.maven.mojos.InfoMojo.readFeature > (InfoMojo.java:299) > at org.apache.sling.feature.maven.mojos.InfoMojo.selectFeatures > (InfoMojo.java:258) > at org.apache.sling.feature.maven.mojos.InfoMojo.execute > (InfoMojo.java:156) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo > (DefaultBuildPluginManager.java:137) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:210) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:156) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:148) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:117) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:81) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build > (SingleThreadedBuilder.java:56) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute > (LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) > at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) > at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (SLING-9587) Content-packages ref not ordered by dependencies for nested packages
[ https://issues.apache.org/jira/browse/SLING-9587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. J. David Bosschaert closed SLING-9587. - > Content-packages ref not ordered by dependencies for nested packages > > > Key: SLING-9587 > URL: https://issues.apache.org/jira/browse/SLING-9587 > Project: Sling > Issue Type: Bug > Components: Content-Package to Feature Model Converter >Affects Versions: Content-Package to Feature Model Converter 1.0.10 >Reporter: Dominik Süß >Assignee: Karl Pauls >Priority: Critical > Fix For: Content-Package to Feature Model Converter 1.0.12 > > > The order logic of the cp converter currently only considers the highest > level packages passed into the converter - installing the identified packages > of type content based on the content-refs subsequently can fail if the > packages as picked up by traversal are not in the order of their > dependencies. > As the order can be calculated via DependencyUtil the output just needs to be > ordered after all entries have been calculated instead of passing to the > writer right away. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (SLING-9521) Packages exported in earlier API Regions are not available to later API Regions
[
https://issues.apache.org/jira/browse/SLING-9521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
A. J. David Bosschaert closed SLING-9521.
-
> Packages exported in earlier API Regions are not available to later API
> Regions
> ---
>
> Key: SLING-9521
> URL: https://issues.apache.org/jira/browse/SLING-9521
> Project: Sling
> Issue Type: Bug
> Components: Feature Model
>Affects Versions: Feature Model API Regions Runtime Fragment 1.1.4
>Reporter: A. J. David Bosschaert
>Assignee: A. J. David Bosschaert
>Priority: Major
> Fix For: Feature Model API Regions Extension 1.1.6, Feature Model
> API Regions Runtime Fragment 1.1.6
>
>
> The API Regions documentation states that "Exports declared earlier in the
> api-regions array also apply to later elements in the array, so the platform
> region also contains all exports declared for the global region" [0]
> However the API Regions runtime fragment doesn't honour this.
> As a test case take 2 feature models:
> Feature Model A:
> * exports package {{foo.bar}} into region r1.
> * exports package {{foo.test}} into region r2.
> Note that according to the documentation mentioned above this means that
> {{foo.bar}} is also implicitly exported into region r2.
> Feature Model B:
> * exports package {{test.abc}} into region r2.
> Note that feature model B does not explicitly opt into region r1.
> Feature Model B also contains a bundle that imports {{foo.bar}}. However
> running these feature models together, the API Regions runtime fragment
> prevents Feature Model B from seeing the {{foo.bar}} package.
> [0]
> https://github.com/apache/sling-org-apache-sling-feature-extension-apiregions/blob/master/docs/api-regions.md#visibility-of-api
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (SLING-9213) Region order is not respected when merging
[ https://issues.apache.org/jira/browse/SLING-9213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. J. David Bosschaert closed SLING-9213. - > Region order is not respected when merging > -- > > Key: SLING-9213 > URL: https://issues.apache.org/jira/browse/SLING-9213 > Project: Sling > Issue Type: Bug > Components: Feature Flags >Affects Versions: Feature Model API Regions Extension 1.1.4 >Reporter: Carsten Ziegeler >Assignee: A. J. David Bosschaert >Priority: Blocker > Fix For: Feature Model API Regions Extension 1.1.6 > > > The regions of the source are always put in front of the regions of the > target. If the source is using less regions than the target, this might > change the ordering of regions. > Example: source has a single region M, target has three regions T,M,B - after > merging the result should still be T, M, B. But right now it is M, T, B > This breaks then the second feature - and potentially other features merged > in afterwards. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (SLING-9592) Update apis-jar analyser to check all api metadata
[ https://issues.apache.org/jira/browse/SLING-9592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. J. David Bosschaert closed SLING-9592. - > Update apis-jar analyser to check all api metadata > -- > > Key: SLING-9592 > URL: https://issues.apache.org/jira/browse/SLING-9592 > Project: Sling > Issue Type: Improvement > Components: Feature Model Analyser >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Major > Fix For: Feature Model Analyser 1.3.2 > > > Besides source-ids there are other metadata properties used by the api jar > generation mojo. We should check all of them and do basic validation -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (SLING-9576) Provide an analyser checking for native code
[ https://issues.apache.org/jira/browse/SLING-9576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. J. David Bosschaert closed SLING-9576. - > Provide an analyser checking for native code > > > Key: SLING-9576 > URL: https://issues.apache.org/jira/browse/SLING-9576 > Project: Sling > Issue Type: Improvement > Components: Feature Model Analyser >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Major > Fix For: Feature Model Analyser 1.3.2 > > > A new analyser checking for the Bundle-NativeCode header and issuing an error > if found -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (SLING-9536) Add analyser checking for duplicate symbolic names
[ https://issues.apache.org/jira/browse/SLING-9536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. J. David Bosschaert closed SLING-9536. - > Add analyser checking for duplicate symbolic names > -- > > Key: SLING-9536 > URL: https://issues.apache.org/jira/browse/SLING-9536 > Project: Sling > Issue Type: New Feature > Components: Feature Model Analyser >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Major > Fix For: Feature Model Analyser 1.3.2 > > > A new analyser could check for duplicate symbolic names in the bundles and > report an error -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (SLING-9591) Add method to get all configurations for a factory pid
[ https://issues.apache.org/jira/browse/SLING-9591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. J. David Bosschaert closed SLING-9591. - > Add method to get all configurations for a factory pid > -- > > Key: SLING-9591 > URL: https://issues.apache.org/jira/browse/SLING-9591 > Project: Sling > Issue Type: Improvement > Components: Feature Model >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Major > Fix For: Feature Model 1.2.4 > > > Add a new method that allows to get all configurations matching a factory pid -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (SLING-9248) Feature model variables are not resolved for array elements
[
https://issues.apache.org/jira/browse/SLING-9248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
A. J. David Bosschaert closed SLING-9248.
-
> Feature model variables are not resolved for array elements
> ---
>
> Key: SLING-9248
> URL: https://issues.apache.org/jira/browse/SLING-9248
> Project: Sling
> Issue Type: Bug
> Components: Feature Model
>Affects Versions: Feature Model 1.1.4
>Reporter: A. J. David Bosschaert
>Assignee: Carsten Ziegeler
>Priority: Major
> Fix For: Feature Model 1.2.4
>
>
> Feature model variables are not resolved for array elements.
> Let's say the following variable is defined:
> {code}
> "variables" : {
> "foo": "b"
> }
> {code}
> Then this variable should be substituted in configuration values that are an
> array:
> {code}
> "configkey" : ["a": "${foo}"]
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (SLING-9590) Add ability to specify java version and options in execution environment
[ https://issues.apache.org/jira/browse/SLING-9590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. J. David Bosschaert closed SLING-9590. - > Add ability to specify java version and options in execution environment > > > Key: SLING-9590 > URL: https://issues.apache.org/jira/browse/SLING-9590 > Project: Sling > Issue Type: Improvement > Components: Feature Model >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Major > Fix For: Feature Model 1.2.4 > > > We should support setting the required java version (OSGi Version object) and > java options in the execution environment -- This message was sent by Atlassian Jira (v8.3.4#803005)
[Jenkins] Sling » sling-org-apache-sling-launchpad-testing » master #925 is BROKEN
Please see
https://builds.apache.org/job/Sling/job/sling-org-apache-sling-launchpad-testing/job/master/925/
for details.
No further emails will be sent until the status of the build is changed.
Build log follows below:
[...truncated 2343 lines...]
[withMaven] using Maven installation 'Maven (latest)'
[Pipeline] {
[Pipeline] sh
+ mvn -U clean verify sonar:sonar -Dsonar.host.url=https://sonarcloud.io
-Dsonar.organization=apache
-Dsonar.projectKey=apache_sling-org-apache-sling-launchpad-testing
-Pjacoco-report
-Dsonar.coverage.jacoco.xmlReportPaths=target/site/jacoco-merged/jacoco.xml
- withMaven Wrapper script -
Picked up JAVA_TOOL_OPTIONS:
-Dmaven.ext.class.path="/home/jenkins/jenkins-slave/workspace/e-sling-launchpad-testing_master@tmp/withMavenecb096f6/pipeline-maven-spy.jar"
-Dorg.jenkinsci.plugins.pipeline.maven.reportsFolder="/home/jenkins/jenkins-slave/workspace/e-sling-launchpad-testing_master@tmp/withMavenecb096f6"
Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: /home/jenkins/tools/maven/latest
Java version: 1.8.0_252, vendor: Oracle Corporation, runtime:
/usr/local/asfpackages/java/openjdk-8u252-b09/jre
Default locale: en_US, platform encoding: ISO-8859-1
OS name: "linux", version: "4.15.0-74-generic", arch: "amd64", family: "unix"
[INFO] [jenkins-event-spy] Generate
/home/jenkins/jenkins-slave/workspace/e-sling-launchpad-testing_master@tmp/withMavenecb096f6/maven-spy-20200720-133705-3872653064942482646262.log.tmp
...
[INFO] Scanning for projects...
[INFO] Downloading from Nexus:
http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.launchpad.test-bundles/12-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded from Nexus:
http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.launchpad.test-bundles/12-SNAPSHOT/maven-metadata.xml
(1.0 kB at 1.6 kB/s)
[INFO] Downloading from Nexus:
http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.starter/12-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded from Nexus:
http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.starter/12-SNAPSHOT/maven-metadata.xml
(5.4 kB at 16 kB/s)
[INFO] Extended Maven classpath (scope 'provided') by the dependencies
extracted from the Sling model.
[INFO] Downloading from Nexus:
http://repository.apache.org/snapshots/org/apache/maven/plugins/maven-metadata.xml
[INFO] Downloading from central:
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml
[INFO] Downloading from Nexus:
http://repository.apache.org/snapshots/org/codehaus/mojo/maven-metadata.xml
[INFO] Downloading from central:
https://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml
[INFO] Downloaded from Nexus:
http://repository.apache.org/snapshots/org/apache/maven/plugins/maven-metadata.xml
(8.5 kB at 25 kB/s)
[INFO] Downloaded from central:
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml
(14 kB at 28 kB/s)
[INFO] Downloaded from central:
https://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml (20
kB at 41 kB/s)
[INFO] Downloading from Nexus:
http://repository.apache.org/snapshots/org/codehaus/mojo/sonar-maven-plugin/maven-metadata.xml
[INFO] Downloading from central:
https://repo.maven.apache.org/maven2/org/codehaus/mojo/sonar-maven-plugin/maven-metadata.xml
[INFO] Downloaded from central:
https://repo.maven.apache.org/maven2/org/codehaus/mojo/sonar-maven-plugin/maven-metadata.xml
(1.2 kB at 50 kB/s)
[INFO]
[INFO] < org.apache.sling:org.apache.sling.launchpad.testing >-
[INFO] Building Apache Sling Launchpad Testing 12-SNAPSHOT
[INFO] -[ slingstart ]-
[INFO] Downloading from Nexus:
http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.launchpad.integration-tests/12-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded from Nexus:
http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.launchpad.integration-tests/12-SNAPSHOT/maven-metadata.xml
(1.0 kB at 2.0 kB/s)
[INFO] Downloading from Nexus:
http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.launchpad.test-services/12-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded from Nexus:
http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.launchpad.test-services/12-SNAPSHOT/maven-metadata.xml
(1.0 kB at 3.0 kB/s)
[INFO] Downloading from Nexus:
http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.launchpad.test-fragment/12-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded from Nexus:
http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.launchpad.test-fragment/12-SNAPSHOT/maven-metadata.xml
(1.0 kB at 3.0 kB/s)
[INFO]
[INFO] --- maven-clean-plugin:3.0.0:clean (default-clean) @
org.apache.sling.launchpad.testing ---
[INFO] Deletin
[jira] [Commented] (SLING-9587) Content-packages ref not ordered by dependencies for nested packages
[ https://issues.apache.org/jira/browse/SLING-9587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17161247#comment-17161247 ] Robert Munteanu commented on SLING-9587: [~dsuess] - the rules are SonarCloud defaults and it's up to each reviewer to say that it's ok (or not) for the code coverage gate to fail. > Content-packages ref not ordered by dependencies for nested packages > > > Key: SLING-9587 > URL: https://issues.apache.org/jira/browse/SLING-9587 > Project: Sling > Issue Type: Bug > Components: Content-Package to Feature Model Converter >Affects Versions: Content-Package to Feature Model Converter 1.0.10 >Reporter: Dominik Süß >Assignee: Karl Pauls >Priority: Critical > Fix For: Content-Package to Feature Model Converter 1.0.12 > > > The order logic of the cp converter currently only considers the highest > level packages passed into the converter - installing the identified packages > of type content based on the content-refs subsequently can fail if the > packages as picked up by traversal are not in the order of their > dependencies. > As the order can be calculated via DependencyUtil the output just needs to be > ordered after all entries have been calculated instead of passing to the > writer right away. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: [VOTE] Release Apache Sling JUnit Core 1.0.30, Apache Sling JUnit Tests Teleporter 1.0.22
On Thu, 2020-07-16 at 12:04 +, Radu Cotescu wrote: > Please vote to approve this release: +1 Robert signature.asc Description: This is a digitally signed message part
[jira] [Commented] (SLING-9211) Startup detection not working reliable anymore
[ https://issues.apache.org/jira/browse/SLING-9211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17161216#comment-17161216 ] Robert Munteanu commented on SLING-9211: That is good to hear. > Startup detection not working reliable anymore > -- > > Key: SLING-9211 > URL: https://issues.apache.org/jira/browse/SLING-9211 > Project: Sling > Issue Type: Improvement > Components: Starter >Reporter: Georg Henzler >Assignee: Georg Henzler >Priority: Major > Attachments: > startup-ServiceUnavailableFilter-2nd-startup-works-fine.log, > startup-ServiceUnavailableFilter-first-startup-feature-launcher.log, > startup-ServiceUnavailableFilter-too-late-registered.log > > > It seems with SLING-8418 the 503 responses are not as reliable as with the > previous custom solution. > To be checked with script in > https://issues.apache.org/jira/browse/FELIX-6097?focusedCommentId=16813130&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16813130 -- This message was sent by Atlassian Jira (v8.3.4#803005)
Moving Sling CI jobs to a new Jenkins setup
Hi, I just became aware that the ASF infra team will retire the current Jenkins setup and will move to a new one. The deadline for the switch is Aug 15th. I have created a Jira issue to track this [1] and it would be great if someone could pick this up. Thanks, Robert [1]: https://issues.apache.org/jira/browse/SLING-9594
[jira] [Created] (SLING-9594) Move Sling builds to ci-builds.apache.org
Robert Munteanu created SLING-9594: -- Summary: Move Sling builds to ci-builds.apache.org Key: SLING-9594 URL: https://issues.apache.org/jira/browse/SLING-9594 Project: Sling Issue Type: Task Components: Build and Source Control Reporter: Robert Munteanu The ASF Jenkins infrastructure is moving to to a new Cloudbees based Client Master called https://ci-builds.apache.org, see https://lists.apache.org/thread.html/re974eed417a1bc294694701d5c91b4bf92689fcf32a4c91f169be87d%40%3Cbuilds.apache.org%3E . The migrations of all jobs needs to be done before the switch off date of 15th August 2020, so we have a maximum about three weeks from now to make the move. There is no automatic way of migrating the jobs, but thankfully our current set up is very much automated and reasonably well documented at https://cwiki.apache.org/confluence/display/SLING/Sling+Jenkins+Setup . It very well may be that we can simply set up another GitHub org on the new Jenkins master, provide the secrets and be done with it. But it needs investigation though. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (SLING-9211) Startup detection not working reliable anymore
[
https://issues.apache.org/jira/browse/SLING-9211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17161186#comment-17161186
]
Georg Henzler commented on SLING-9211:
--
So I checked with
{code}
java -jar org.apache.sling.feature.launcher-1.1.4.jar -f
target/slingfeature-tmp/feature-oak_tar.json
{code}
that produced the log file
[^startup-ServiceUnavailableFilter-first-startup-feature-launcher.log]. It
works well and the ServiceUnavailableFilter is correctly activated at start
level 5 on first start already.
> Startup detection not working reliable anymore
> --
>
> Key: SLING-9211
> URL: https://issues.apache.org/jira/browse/SLING-9211
> Project: Sling
> Issue Type: Improvement
> Components: Starter
>Reporter: Georg Henzler
>Assignee: Georg Henzler
>Priority: Major
> Attachments:
> startup-ServiceUnavailableFilter-2nd-startup-works-fine.log,
> startup-ServiceUnavailableFilter-first-startup-feature-launcher.log,
> startup-ServiceUnavailableFilter-too-late-registered.log
>
>
> It seems with SLING-8418 the 503 responses are not as reliable as with the
> previous custom solution.
> To be checked with script in
> https://issues.apache.org/jira/browse/FELIX-6097?focusedCommentId=16813130&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16813130
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (SLING-9211) Startup detection not working reliable anymore
[ https://issues.apache.org/jira/browse/SLING-9211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Georg Henzler updated SLING-9211: - Attachment: startup-ServiceUnavailableFilter-first-startup-feature-launcher.log > Startup detection not working reliable anymore > -- > > Key: SLING-9211 > URL: https://issues.apache.org/jira/browse/SLING-9211 > Project: Sling > Issue Type: Improvement > Components: Starter >Reporter: Georg Henzler >Assignee: Georg Henzler >Priority: Major > Attachments: > startup-ServiceUnavailableFilter-2nd-startup-works-fine.log, > startup-ServiceUnavailableFilter-first-startup-feature-launcher.log, > startup-ServiceUnavailableFilter-too-late-registered.log > > > It seems with SLING-8418 the 503 responses are not as reliable as with the > previous custom solution. > To be checked with script in > https://issues.apache.org/jira/browse/FELIX-6097?focusedCommentId=16813130&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16813130 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (SLING-9211) Startup detection not working reliable anymore
[ https://issues.apache.org/jira/browse/SLING-9211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17161126#comment-17161126 ] Robert Munteanu commented on SLING-9211: [~ghenzler] - the current plan is to ship Starter 12 based on the feature model. We are done with Phase 1 as defined in https://cwiki.apache.org/confluence/display/SLING/Migrating+the+Sling+Starter+to+the+Feature+Model and I will start defining tasks for Phase 2 this week. > Startup detection not working reliable anymore > -- > > Key: SLING-9211 > URL: https://issues.apache.org/jira/browse/SLING-9211 > Project: Sling > Issue Type: Improvement > Components: Starter >Reporter: Georg Henzler >Assignee: Georg Henzler >Priority: Major > Attachments: > startup-ServiceUnavailableFilter-2nd-startup-works-fine.log, > startup-ServiceUnavailableFilter-too-late-registered.log > > > It seems with SLING-8418 the 503 responses are not as reliable as with the > previous custom solution. > To be checked with script in > https://issues.apache.org/jira/browse/FELIX-6097?focusedCommentId=16813130&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16813130 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (SLING-9211) Startup detection not working reliable anymore
[ https://issues.apache.org/jira/browse/SLING-9211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17161126#comment-17161126 ] Robert Munteanu edited comment on SLING-9211 at 7/20/20, 10:33 AM: --- [~ghenzler] - the current plan is to ship Starter 12 based on the feature model. We are done with Phase 1 as defined in https://cwiki.apache.org/confluence/display/SLING/Migrating+the+Sling+Starter+to+the+Feature+Model and I will start creating Jira issues for Phase 2 this week. was (Author: rombert): [~ghenzler] - the current plan is to ship Starter 12 based on the feature model. We are done with Phase 1 as defined in https://cwiki.apache.org/confluence/display/SLING/Migrating+the+Sling+Starter+to+the+Feature+Model and I will start defining tasks for Phase 2 this week. > Startup detection not working reliable anymore > -- > > Key: SLING-9211 > URL: https://issues.apache.org/jira/browse/SLING-9211 > Project: Sling > Issue Type: Improvement > Components: Starter >Reporter: Georg Henzler >Assignee: Georg Henzler >Priority: Major > Attachments: > startup-ServiceUnavailableFilter-2nd-startup-works-fine.log, > startup-ServiceUnavailableFilter-too-late-registered.log > > > It seems with SLING-8418 the 503 responses are not as reliable as with the > previous custom solution. > To be checked with script in > https://issues.apache.org/jira/browse/FELIX-6097?focusedCommentId=16813130&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16813130 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (SLING-9211) Startup detection not working reliable anymore
[ https://issues.apache.org/jira/browse/SLING-9211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17161122#comment-17161122 ] Georg Henzler commented on SLING-9211: -- [~rombert] I think at the moment the feature model variant is marked as experimental README.md - but if we swap over soon we obviously don't need to fix "the old world" (I think the problem described is more in project org.apache.sling.launchpad.installer than in OSGi installer, but also that will be deprecated soon I suppose). I'm testing now the experimental feature model variant > Startup detection not working reliable anymore > -- > > Key: SLING-9211 > URL: https://issues.apache.org/jira/browse/SLING-9211 > Project: Sling > Issue Type: Improvement > Components: Starter >Reporter: Georg Henzler >Assignee: Georg Henzler >Priority: Major > Attachments: > startup-ServiceUnavailableFilter-2nd-startup-works-fine.log, > startup-ServiceUnavailableFilter-too-late-registered.log > > > It seems with SLING-8418 the 503 responses are not as reliable as with the > previous custom solution. > To be checked with script in > https://issues.apache.org/jira/browse/FELIX-6097?focusedCommentId=16813130&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16813130 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (SLING-9211) Startup detection not working reliable anymore
[ https://issues.apache.org/jira/browse/SLING-9211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17161122#comment-17161122 ] Georg Henzler edited comment on SLING-9211 at 7/20/20, 10:28 AM: - [~rombert] I think at the moment the feature model variant is marked as experimental in README.md - but if we swap over soon we obviously don't need to fix "the old world" (I think the problem described is more in project org.apache.sling.launchpad.installer than in OSGi installer, but also that will be deprecated soon I suppose). I'm testing now the experimental feature model variant was (Author: henzlerg): [~rombert] I think at the moment the feature model variant is marked as experimental README.md - but if we swap over soon we obviously don't need to fix "the old world" (I think the problem described is more in project org.apache.sling.launchpad.installer than in OSGi installer, but also that will be deprecated soon I suppose). I'm testing now the experimental feature model variant > Startup detection not working reliable anymore > -- > > Key: SLING-9211 > URL: https://issues.apache.org/jira/browse/SLING-9211 > Project: Sling > Issue Type: Improvement > Components: Starter >Reporter: Georg Henzler >Assignee: Georg Henzler >Priority: Major > Attachments: > startup-ServiceUnavailableFilter-2nd-startup-works-fine.log, > startup-ServiceUnavailableFilter-too-late-registered.log > > > It seems with SLING-8418 the 503 responses are not as reliable as with the > previous custom solution. > To be checked with script in > https://issues.apache.org/jira/browse/FELIX-6097?focusedCommentId=16813130&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16813130 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (SLING-9211) Startup detection not working reliable anymore
[
https://issues.apache.org/jira/browse/SLING-9211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17160960#comment-17160960
]
Georg Henzler edited comment on SLING-9211 at 7/20/20, 10:24 AM:
-
See attached [^startup-ServiceUnavailableFilter-too-late-registered.log] on
what is happening (the result of {{cat sling/logs/error.log | grep -E
"(ServiceUnavailable|health|Health)"}}). The only difference to the current
committed version is that I added a bundle with
org.apache.sling.starter.startup.impl.EventLogger that logs OSGi events
together with current start level.
See also [^startup-ServiceUnavailableFilter-2nd-startup-works-fine.log] on how
everything works fine (on second startup bundles start at start level 5 and
configs become correctly active)
[~cziegeler] So I'm pretty sure the expected behaviour is currently broken...
maybe you can have a look?
was (Author: henzlerg):
See attached [^startup-ServiceUnavailableFilter-too-late-registered.log] on
what is happening (the result of {{cat sling/logs/error.log | grep -E
"(ServiceUnavailable|health|Health)"}}). The only difference to the current
committed version is that I added a bundle with
org.apache.sling.starter.startup.impl.EventLogger that logs OSGi events
together with current startlevel.
[~cziegeler] So I'm pretty sure the expected behaviour is currently broken...
maybe you can have a look?
> Startup detection not working reliable anymore
> --
>
> Key: SLING-9211
> URL: https://issues.apache.org/jira/browse/SLING-9211
> Project: Sling
> Issue Type: Improvement
> Components: Starter
>Reporter: Georg Henzler
>Assignee: Georg Henzler
>Priority: Major
> Attachments:
> startup-ServiceUnavailableFilter-2nd-startup-works-fine.log,
> startup-ServiceUnavailableFilter-too-late-registered.log
>
>
> It seems with SLING-8418 the 503 responses are not as reliable as with the
> previous custom solution.
> To be checked with script in
> https://issues.apache.org/jira/browse/FELIX-6097?focusedCommentId=16813130&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16813130
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (SLING-9211) Startup detection not working reliable anymore
[ https://issues.apache.org/jira/browse/SLING-9211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Georg Henzler updated SLING-9211: - Attachment: startup-ServiceUnavailableFilter-2nd-startup-works-fine.log > Startup detection not working reliable anymore > -- > > Key: SLING-9211 > URL: https://issues.apache.org/jira/browse/SLING-9211 > Project: Sling > Issue Type: Improvement > Components: Starter >Reporter: Georg Henzler >Assignee: Georg Henzler >Priority: Major > Attachments: > startup-ServiceUnavailableFilter-2nd-startup-works-fine.log, > startup-ServiceUnavailableFilter-too-late-registered.log > > > It seems with SLING-8418 the 503 responses are not as reliable as with the > previous custom solution. > To be checked with script in > https://issues.apache.org/jira/browse/FELIX-6097?focusedCommentId=16813130&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16813130 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SLING-9575) Existing API Regions with factory Pids are not found
[ https://issues.apache.org/jira/browse/SLING-9575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. J. David Bosschaert updated SLING-9575: -- Fix Version/s: (was: Feature Model API Regions Extension 1.1.6) Feature Model API Regions Runtime Fragment 1.1.6 > Existing API Regions with factory Pids are not found > > > Key: SLING-9575 > URL: https://issues.apache.org/jira/browse/SLING-9575 > Project: Sling > Issue Type: Bug > Components: Feature Model >Affects Versions: Feature Model API Regions Runtime Fragment 1.1.4 >Reporter: A. J. David Bosschaert >Assignee: A. J. David Bosschaert >Priority: Major > Fix For: Feature Model API Regions Runtime Fragment 1.1.6 > > > Configuration for the API Regions fragment can be dynamically provided > through factory configurations. > On restart the API Regions fragment looks these configurations up to re-apply > them. This lookup on restart always fails. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (SLING-9593) Abstract out binary handling to allow plugging of different stores
[ https://issues.apache.org/jira/browse/SLING-9593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17161090#comment-17161090 ] Amit Jain commented on SLING-9593: -- PRs: * [https://github.com/apache/sling-org-apache-sling-distribution-journal-messages/pull/4] * [https://github.com/apache/sling-org-apache-sling-distribution-journal/pull/54] [~cschneider] Please review the proposed changes. > Abstract out binary handling to allow plugging of different stores > -- > > Key: SLING-9593 > URL: https://issues.apache.org/jira/browse/SLING-9593 > Project: Sling > Issue Type: Improvement > Components: Content Distribution >Reporter: Amit Jain >Priority: Major > > Currently, package binaries with size over a certain limit are stored in jcr. > This issue is to allow plugging in different backends for storing package > handling and also any strategizing on what can be stored. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (SLING-9211) Startup detection not working reliable anymore
[
https://issues.apache.org/jira/browse/SLING-9211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17161009#comment-17161009
]
Robert Munteanu commented on SLING-9211:
I see the OSGi installer being mentioned. Perhaps with the migration to the
feature model ( SLING-8350 ) this is no longer such an important an issue? This
can be tested with the feature model aggregates generated locally by the
started with {{mvn clean install}}.
{noformat}
...
[INFO] Installing
/home/robert/sources/apache/sling/org-apache-sling-starter/target/slingfeature-tmp/feature-oak_tar.json
to
/home/robert/.m2/repository/org/apache/sling/org.apache.sling.starter/12-SNAPSHOT/org.apache.sling.starter-12-SNAPSHOT-oak_tar.slingosgifeature
...
{noformat}
> Startup detection not working reliable anymore
> --
>
> Key: SLING-9211
> URL: https://issues.apache.org/jira/browse/SLING-9211
> Project: Sling
> Issue Type: Improvement
> Components: Starter
>Reporter: Georg Henzler
>Assignee: Georg Henzler
>Priority: Major
> Attachments: startup-ServiceUnavailableFilter-too-late-registered.log
>
>
> It seems with SLING-8418 the 503 responses are not as reliable as with the
> previous custom solution.
> To be checked with script in
> https://issues.apache.org/jira/browse/FELIX-6097?focusedCommentId=16813130&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16813130
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (SLING-9211) Startup detection not working reliable anymore
[
https://issues.apache.org/jira/browse/SLING-9211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17160960#comment-17160960
]
Georg Henzler commented on SLING-9211:
--
See attached [^startup-ServiceUnavailableFilter-too-late-registered.log] on
what is happening (the result of {{cat sling/logs/error.log | grep -E
"(ServiceUnavailable|health|Health)"}}). The only difference to the current
committed version is that I added a bundle with
org.apache.sling.starter.startup.impl.EventLogger that logs OSGi events
together with current startlevel.
[~cziegeler] So I'm pretty sure the expected behaviour is currently broken...
maybe you can have a look?
> Startup detection not working reliable anymore
> --
>
> Key: SLING-9211
> URL: https://issues.apache.org/jira/browse/SLING-9211
> Project: Sling
> Issue Type: Improvement
> Components: Starter
>Reporter: Georg Henzler
>Assignee: Georg Henzler
>Priority: Major
> Attachments: startup-ServiceUnavailableFilter-too-late-registered.log
>
>
> It seems with SLING-8418 the 503 responses are not as reliable as with the
> previous custom solution.
> To be checked with script in
> https://issues.apache.org/jira/browse/FELIX-6097?focusedCommentId=16813130&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16813130
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
