[jira] [Commented] (SLING-12351) Create a default implementation for generating the analyser-metadata extension
[
https://issues.apache.org/jira/browse/SLING-12351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17853199#comment-17853199
]
Angela Schreiber commented on SLING-12351:
--
[~rombert], i didn't spot this ticket and that you intend to put it into the
2.0.4 release, which i just cut today. sorry for that.
> Create a default implementation for generating the analyser-metadata extension
> --
>
> Key: SLING-12351
> URL: https://issues.apache.org/jira/browse/SLING-12351
> Project: Sling
> Issue Type: Improvement
> Components: Feature Model Analyser
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>Priority: Major
> Fix For: Feature Model Analyser 2.0.4
>
>
> The feature model analysers contains and use the
> {{AnalyserMetaDataExtension}} -
> https://github.com/apache/sling-org-apache-sling-feature-analyser/blob/c8518ebd7c8fa245781ad8062f2c2d6b52174345/src/main/java/org/apache/sling/feature/analyser/extensions/AnalyserMetaDataExtension.java
> .
> This class is read and used (error reporting, cached manifests) but there is
> currently no automated way of generating the metadata.
> We should provide a default implementation that simplifies the metadata
> generation. The same implementation should also support generating the
> framework capabilities metadata as discussed in SLING-10288 .
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: VOTE] Release Apache Sling Feature Model Analyser 2.0.4
+1 (You might need to update your gpg keys before) Am Fr., 7. Juni 2024 um 14:00 Uhr schrieb ang...@apache.org < ang...@apache.org>: > Hi everyone, > > We solved 4 issues in this release: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710=12353831=Text > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2866/ > > You can use this UNIX script to download the release and verify the > signatures: > > > https://raw.githubusercontent.com/apache/sling-tooling-release/master/check_staged_release.sh > > Usage: > sh check_staged_release.sh 2866 /tmp/sling-staging > > Please vote to approve this release: > >[ ] +1 Approve the release >[ ] 0 Don't care >[ ] -1 Don't release, because ... > > This majority vote is open for at least 72 hours. > > Thanks for voting and kind regards > Angela > -- https://cqdump.joerghoh.de
Re: [PR] SLING-12351 - Create a default implementation for generating the analyser-metadata extension [sling-org-apache-sling-feature-analyser]
sonarcloud[bot] commented on PR #46: URL: https://github.com/apache/sling-org-apache-sling-feature-analyser/pull/46#issuecomment-2154809596 ## [](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-feature-analyser=46) **Quality Gate passed** Issues  [1 New issue](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-analyser=46=false=true)  [0 Accepted issues](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-feature-analyser=46=WONTFIX) Measures  [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-feature-analyser=46=false=true)  [90.5% Coverage on New Code](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-feature-analyser=46=new_coverage=list)  [0.0% Duplication on New Code](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-feature-analyser=46=new_duplicated_lines_density=list) [See analysis details on SonarCloud](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-feature-analyser=46) -- 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. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] SLING-12351 - Create a default implementation for generating the analyser-metadata extension [sling-org-apache-sling-feature-analyser]
rombert opened a new pull request, #46: URL: https://github.com/apache/sling-org-apache-sling-feature-analyser/pull/46 (no comment) -- 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. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: VOTE] Release Apache Sling Feature Model Analyser 2.0.4
here is my +1 kind regards angela On 07.06.2024 13:58, ang...@apache.org wrote: Hi everyone, We solved 4 issues in this release: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710=12353831=Text Staging repository: https://repository.apache.org/content/repositories/orgapachesling-2866/ You can use this UNIX script to download the release and verify the signatures: https://raw.githubusercontent.com/apache/sling-tooling-release/master/check_staged_release.sh Usage: sh check_staged_release.sh 2866 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours. Thanks for voting and kind regards Angela
VOTE] Release Apache Sling Feature Model Analyser 2.0.4
Hi everyone, We solved 4 issues in this release: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710=12353831=Text Staging repository: https://repository.apache.org/content/repositories/orgapachesling-2866/ You can use this UNIX script to download the release and verify the signatures: https://raw.githubusercontent.com/apache/sling-tooling-release/master/check_staged_release.sh Usage: sh check_staged_release.sh 2866 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours. Thanks for voting and kind regards Angela
[Jenkins] Sling » Modules » sling-org-apache-sling-starter » master #1402 is BROKEN
/org/apache/maven/maven-artifact-manager/2.2.1/maven-artifact-manager-2.2.1.jar (68 kB at 2.0 MB/s) [INFO] Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-profile/2.2.1/maven-profile-2.2.1.jar [INFO] Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-model/2.2.1/maven-model-2.2.1.jar (88 kB at 1.5 MB/s) [INFO] Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-plugin-registry/2.2.1/maven-plugin-registry-2.2.1.jar [INFO] Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-profile/2.2.1/maven-profile-2.2.1.jar (35 kB at 570 kB/s) [INFO] Downloading from central: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-interpolation/1.11/plexus-interpolation-1.11.jar [INFO] Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-project/2.2.1/maven-project-2.2.1.jar (156 kB at 2.4 MB/s) [INFO] Downloading from central: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-component-annotations/2.1.0/plexus-component-annotations-2.1.0.jar [INFO] Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-settings/2.2.1/maven-settings-2.2.1.jar (49 kB at 766 kB/s) [INFO] Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-plugin-api/2.2.1/maven-plugin-api-2.2.1.jar [INFO] Downloaded from central: https://repo.maven.apache.org/maven2/backport-util-concurrent/backport-util-concurrent/3.1/backport-util-concurrent-3.1.jar (332 kB at 5.1 MB/s) [INFO] Downloading from central: https://repo.maven.apache.org/maven2/org/apache/commons/commons-lang3/3.5/commons-lang3-3.5.jar [INFO] Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-plugin-registry/2.2.1/maven-plugin-registry-2.2.1.jar (30 kB at 338 kB/s) [INFO] Downloaded from central: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-component-annotations/2.1.0/plexus-component-annotations-2.1.0.jar (4.2 kB at 46 kB/s) [INFO] Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-plugin-api/2.2.1/maven-plugin-api-2.2.1.jar (12 kB at 134 kB/s) [INFO] Downloaded from central: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-interpolation/1.11/plexus-interpolation-1.11.jar (51 kB at 542 kB/s) [INFO] Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/commons/commons-lang3/3.5/commons-lang3-3.5.jar (480 kB at 3.9 MB/s) [INFO] Enabled default license matchers. [INFO] Will parse SCM ignores for exclusions... [INFO] Parsing exclusions from /home/jenkins/jenkins-agent/workspace/_org-apache-sling-starter_master/jdk_17_latest/.gitignore [INFO] Finished adding exclusions from SCM ignore files. [INFO] 79 implicit excludes. [INFO] 15 explicit excludes. [INFO] 21 resources included [INFO] Rat check: Summary over all files. Unapproved: 0, unknown: 0, generated: 0, approved: 20 licenses. [INFO] [INFO] --- docker:0.44.0:stop (stop-mongo) @ org.apache.sling.starter --- [INFO] DOCKER> [mongo:4.4.6] "mongo": Stop and removed container baecf2ecf744 after 0 ms [INFO] [INFO] --- failsafe:3.0.0-M5:verify (default) @ org.apache.sling.starter --- [INFO] Failsafe report directory: /home/jenkins/jenkins-agent/workspace/_org-apache-sling-starter_master/jdk_17_latest/target/failsafe-reports [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 07:38 min [INFO] Finished at: 2024-06-07T11:28:29Z [INFO] [INFO] [jenkins-event-spy] Generated /home/jenkins/jenkins-agent/workspace/_org-apache-sling-starter_master/jdk_17_latest@tmp/withMavenf69e660b/maven-spy-20240607-112051-36510261329581714401555.log [ERROR] Failed to execute goal org.apache.maven.plugins:maven-failsafe-plugin:3.0.0-M5:verify (default) on project org.apache.sling.starter: There are test failures. [ERROR] [ERROR] Please refer to /home/jenkins/jenkins-agent/workspace/_org-apache-sling-starter_master/jdk_17_latest/target/failsafe-reports for the individual test results. [ERROR] Please refer to dump files (if any exist) [date].dump, [date]-jvmRun[N].dump and [date].dumpstream. [ERROR] -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-failsafe-plugin:3.0.0-M5:verify (default) on project org.apache.sling.starter: There are test failures. Please refer to /home/jenkins/jenkins-agent/workspace/_org-apache-sling-starter_master/jdk_17_latest/target/failsafe-reports for the individual test results. Please refer to dump files (if any exist) [date].dump, [date]-jvmRun[N].dump and [date].dumpstream. at org.apache.maven.lifecycle.internal.MojoExe
Re: [VOTE] Release Apache Sling Repoinit JCR 1.1.50
+1 - Andrei On Fri, Jun 7, 2024 at 12:20 AM Eric Norman wrote: > +1 > > Regards, > Eric > > On Tue, Jun 4, 2024 at 6:27 AM Julian Sedding wrote: > > > Hi, > > > > We solved 1 issue in this release: > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710=12354758=Text > > > > Staging repository: > > https://repository.apache.org/content/repositories/orgapachesling-2864/ > > > > You can use this UNIX script to download the release and verify the > > signatures: > > > > > https://raw.githubusercontent.com/apache/sling-tooling-release/master/check_staged_release.sh > > > > Usage: > > sh check_staged_release.sh 2864 /tmp/sling-staging > > > > Please vote to approve this release: > > > > [ ] +1 Approve the release > > [ ] 0 Don't care > > [ ] -1 Don't release, because ... > > > > This majority vote is open for at least 72 hours. > > > > Regards > > Julian > > >
[jira] [Commented] (SLING-12349) Unable to set a maximum amount of Sling Jobs in parallel
[ https://issues.apache.org/jira/browse/SLING-12349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17853054#comment-17853054 ] Carsten Ziegeler commented on SLING-12349: -- as far as I remember, that configuration was intended to do what you want > Unable to set a maximum amount of Sling Jobs in parallel > - > > Key: SLING-12349 > URL: https://issues.apache.org/jira/browse/SLING-12349 > Project: Sling > Issue Type: Bug > Components: Event >Reporter: Roy Teeuwen >Priority: Major > > It is possible to set a maximum parallel of sling jobs on a queue > configuration, but in systems where the platform itself already makes 20 > queue's and the customer's code also add's their own queue's, this > configuration makes no sense because it is set per queue and not overall. The > sum of the parallel could be way more than the amount of cores available, > making the system unworkable if the separate queue's all have jobs at the > same time > It would be logical that you can also set a maximum parallel overall for all > queue's combined. Is there a reason that this is not already the case? Would > there be anything against building this in? -- This message was sent by Atlassian Jira (v8.20.10#820010)
