[GitHub] [sling-org-apache-sling-jms] sonarcloud[bot] commented on pull request #3: SLING-11382: Sling update to 47
sonarcloud[bot] commented on PR #3: URL: https://github.com/apache/sling-org-apache-sling-jms/pull/3#issuecomment-1626399373 Kudos, SonarCloud Quality Gate passed! [](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-jms=3) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jms=3=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jms=3=false=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jms=3=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jms=3=false=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jms=3=false=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jms=3=false=VULNERABILITY) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-jms=3=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-jms=3=false=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-jms=3=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jms=3=false=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jms=3=false=CODE_SMELL) [0 Code Smells](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jms=3=false=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-jms=3=coverage=list) No Coverage information [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-jms=3=new_duplicated_lines_density=list) [0.0% Duplication](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-jms=3=new_duplicated_lines_density=list) -- 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
[jira] [Commented] (SLING-11920) Expose Object Type Names in Selected Field
[
https://issues.apache.org/jira/browse/SLING-11920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17741219#comment-17741219
]
Andreas Schaefer commented on SLING-11920:
--
I created a PR
[https://github.com/apache/sling-org-apache-sling-graphql-core/pull/36] that
exposed the Object Type Names to the User.
There is also some cleanup and additional tests to verify the proper handling
of Object Type Names.
> Expose Object Type Names in Selected Field
> --
>
> Key: SLING-11920
> URL: https://issues.apache.org/jira/browse/SLING-11920
> Project: Sling
> Issue Type: Bug
>Affects Versions: GraphQL Core 0.0.20
>Reporter: Andreas Schaefer
>Assignee: Andreas Schaefer
>Priority: Critical
> Fix For: GraphQL Core 0.0.22
>
>
> Intermediary fields are not exposed as Selected Fields in Graphql-java and so
> it was added as list of Object Type Name.
> Now for handling '... on ' we need to expose these Object Type
> Names so that a client can deal with them.
> If we have a query where we have a inline fragments
> ([https://graphql.org/learn/queries/#inline-fragments]) like:
> {code:java}
> {
>image {
> ... on ImageRef {
> type{code}
> Then in the graphql-java 15.0 there is an inlined field called *ImageRef* but
> that is now gone in 20.1. Instead we have a list of Object Type Names in a
> field and in our example *type* would have Objet Type Names:
> {*}["ImageRef"]{*}. So for a client to obtain the type of the inlined
> fragments this data must be exposed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [sling-org-apache-sling-graphql-core] schaefa opened a new pull request, #36: SLING-11920 - Expose Object Type Names as replacement for Inlined Fragments
schaefa opened a new pull request, #36: URL: https://github.com/apache/sling-org-apache-sling-graphql-core/pull/36 There are no more inlined fragments in Graphql-java 20.1 and so we need to use the Object Type Names that come with the field to handle inlined fragments in a query. The Object Type Names were added to the Selected Field but were not exposed to the user. This is fixed with this PR and the SelectedField.isInlined is marked deprecated. I added some further tests to test the object type names. -- 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
[GitHub] [sling-org-apache-sling-datasource] dependabot[bot] opened a new pull request, #3: Bump h2 from 1.4.178 to 2.2.220
dependabot[bot] opened a new pull request, #3: URL: https://github.com/apache/sling-org-apache-sling-datasource/pull/3 Bumps [h2](https://github.com/h2database/h2database) from 1.4.178 to 2.2.220. Release notes Sourced from https://github.com/h2database/h2database/releases;>h2's releases. Version 2.2.220 Changes since 2.1.214 release: ... (truncated) Commits https://github.com/h2database/h2database/commit/66185fbfde24fbe5b2adf06fdaae4f5ffb178813;>66185fb changelog adjustment https://github.com/h2database/h2database/commit/f3c8222f3d77a8e71db2e6a72ea183c1931bfa6d;>f3c8222 version and release date https://github.com/h2database/h2database/commit/087522bbc84c1b26417dd1ea348d8fbf839d5a32;>087522b javadoc https://github.com/h2database/h2database/commit/1ae052a1c0c87c687ac1d312e2bd69a4def652aa;>1ae052a spell-check https://github.com/h2database/h2database/commit/4ac534343ff7bde11bda681da39075cfa34ca440;>4ac5343 Merge pull request https://redirect.github.com/h2database/h2database/issues/3834;>#3834 from katzyn/version https://github.com/h2database/h2database/commit/72f6e983789b0ff413ba110d218c18ded50cb7b8;>72f6e98 Update TestMVStore https://github.com/h2database/h2database/commit/81bac50fed2f8418d83455e8d4c7fbf855bede89;>81bac50 Update changelog https://github.com/h2database/h2database/commit/f047d77085d62cd1867edcf394944de46550d58a;>f047d77 Add 2.0.* and 2.1.* versions to Upgrade utility https://github.com/h2database/h2database/commit/1341fea79e0d82d5967ecd19fba206a740870a69;>1341fea Increase database format version https://github.com/h2database/h2database/commit/581ed18ff9d6b3761d851620ed88a3994a351a0d;>581ed18 Merge pull request https://redirect.github.com/h2database/h2database/issues/3833;>#3833 from katzyn/password Additional commits viewable in https://github.com/h2database/h2database/compare/version-1.4.178...version-2.2.220;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/sling-org-apache-sling-datasource/network/alerts). -- 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
[jira] [Created] (SLING-11939) Update to Sling Bundle Parent 50
Oliver Lietz created SLING-11939: Summary: Update to Sling Bundle Parent 50 Key: SLING-11939 URL: https://issues.apache.org/jira/browse/SLING-11939 Project: Sling Issue Type: Task Components: JCR, Oak Reporter: Oliver Lietz Assignee: Oliver Lietz Fix For: Clam 1.2.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SLING-11938) Update to Sling Bundle Parent 50
Oliver Lietz created SLING-11938: Summary: Update to Sling Bundle Parent 50 Key: SLING-11938 URL: https://issues.apache.org/jira/browse/SLING-11938 Project: Sling Issue Type: Task Components: Testing Reporter: Oliver Lietz Assignee: Oliver Lietz Fix For: Testing PaxExam 4.0.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SLING-11920) Expose Object Type Names in Selected Field
[
https://issues.apache.org/jira/browse/SLING-11920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Schaefer updated SLING-11920:
-
Description:
Intermediary fields are not exposed as Selected Fields in Graphql-java and so
it was added as list of Object Type Name.
Now for handling '... on ' we need to expose these Object Type
Names so that a client can deal with them.
If we have a query where we have a inline fragments
([https://graphql.org/learn/queries/#inline-fragments]) like:
{code:java}
{
image {
... on ImageRef {
type{code}
Then in the graphql-java 15.0 there is an inlined field called *ImageRef* but
that is now gone in 20.1. Instead we have a list of Object Type Names in a
field and in our example *type* would have Objet Type Names:
{*}["ImageRef"]{*}. So for a client to obtain the type of the inlined fragments
this data must be exposed.
was:
Intermediary fields are not exposed as Selected Fields in Graphql-java and so
it was added as list of Object Type Name.
Now for handling '... on ' we need to expose these Object Type
Names so that a client can deal with them.
> Expose Object Type Names in Selected Field
> --
>
> Key: SLING-11920
> URL: https://issues.apache.org/jira/browse/SLING-11920
> Project: Sling
> Issue Type: Bug
>Affects Versions: GraphQL Core 0.0.20
>Reporter: Andreas Schaefer
>Assignee: Andreas Schaefer
>Priority: Critical
> Fix For: GraphQL Core 0.0.22
>
>
> Intermediary fields are not exposed as Selected Fields in Graphql-java and so
> it was added as list of Object Type Name.
> Now for handling '... on ' we need to expose these Object Type
> Names so that a client can deal with them.
> If we have a query where we have a inline fragments
> ([https://graphql.org/learn/queries/#inline-fragments]) like:
> {code:java}
> {
>image {
> ... on ImageRef {
> type{code}
> Then in the graphql-java 15.0 there is an inlined field called *ImageRef* but
> that is now gone in 20.1. Instead we have a list of Object Type Names in a
> field and in our example *type* would have Objet Type Names:
> {*}["ImageRef"]{*}. So for a client to obtain the type of the inlined
> fragments this data must be exposed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (SLING-11254) Make additional authorization on HTTP scan endpoint mandatory
[
https://issues.apache.org/jira/browse/SLING-11254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17636294#comment-17636294
]
Oliver Lietz edited comment on SLING-11254 at 7/7/23 6:52 PM:
--
-switching to Commons Permissions- – no consent for Commons Permissions
was (Author: olli):
switching to Commons Permissions
> Make additional authorization on HTTP scan endpoint mandatory
> -
>
> Key: SLING-11254
> URL: https://issues.apache.org/jira/browse/SLING-11254
> Project: Sling
> Issue Type: Improvement
> Components: JCR, Oak
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
>Priority: Major
> Fix For: Clam 1.2.0
>
>
> caller needs to be member of a configured group (default group:
> {{sling-clam-scan}})
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [VOTE] Release Apache Sling Parent and Bundle Parent version 50
On Wednesday, 5 July 2023 12:34:38 CEST Konrad Windszus wrote: > Hi, > > We solved 9 issues in these releases: > > Parent: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710 > ersion=12352188=Text Bundle Parent: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710 > ersion=12352189=Text > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2761/ 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 2761 /tmp/sling-staging +1 O.
Re: [VOTE] Release Apache Sling Feature Launcher Maven Plugin 0.1.6
+1 Am Fr., 7. Juli 2023 um 12:56 Uhr schrieb Robert Munteanu < romb...@apache.org>: > Hi, > > We solved 1 issue in this release: > https://issues.apache.org/jira/browse/SLING/fixforversion/12352559 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2763/ > > 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 2763 /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, > Robert Munteanu > -- Cheers, Jörg Hoh, https://cqdump.joerghoh.de Twitter: @joerghoh
Re: [VOTE] Release Apache Sling OSGi Feature Maven Plugin 1.7.2
+1 Am Fr., 7. Juli 2023 um 12:53 Uhr schrieb Robert Munteanu < romb...@apache.org>: > Hi, > > We solved 2 issues in this release: > https://issues.apache.org/jira/browse/SLING/fixforversion/12353301 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2762/ > > 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 2762 /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, > Robert Munteanu > -- Cheers, Jörg Hoh, https://cqdump.joerghoh.de Twitter: @joerghoh
RE: Sling Models Integration Tests broken
hello konrad.
yes, that's an important open issue. the ideal solution would be a) switch to
sling 12 + integrate the integration tests in the models impl repository, and
have them automatically executed in jenkins when models impl change.
this probably involves splitting the integration tests in two parts and putting
the exporter-related integration tests into the jacksonexporter repository.
but that's a good deal of work to get this running. i'm lacking the knowledge
in the feature model tooling to get a good start on this.
stefan
> -Original Message-
> From: Konrad Windszus
> Sent: Friday, July 7, 2023 4:57 PM
> To: dev@sling.apache.org
> Subject: Sling Models Integration Tests broken
>
> HI,
> The ITs at https://github.com/apache/sling-org-apache-sling-models-
> integration-tests built through https://ci-
> builds.apache.org/blue/organizations/jenkins/Sling%2Fmodules%2Fsling-org-
> apache-sling-models-integration-tests/activity are failing since quite
> some time and also reference pretty outdated Sling Models bundle versions.
> Seems that the root issue is that even that outdated version of Models
> Impl (1.5.3-SNAPSHOT, https://github.com/apache/sling-org-apache-sling-
> models-integration-
> tests/blob/3a20ea6b8e2cd025e396797be94b8268a240efae/pom.xml#L261C30-
> L261C30) requires a newer version of Sling API than shipped with Sling
> Starter 11:
>
> "06.07.2023 18:29:43.869 *INFO* [OsgiInstallerImpl]
> org.apache.sling.installer.core.impl.tasks.BundleStartTask Could not start
> bundle org.apache.sling.models.impl [147]. Reason: {}. Will retry.
> org.osgi.framework.BundleException: Unable to resolve
> org.apache.sling.models.impl [147](R 147.0): missing requirement
> [org.apache.sling.models.impl [147](R 147.0)] osgi.wiring.package;
> (&(osgi.wiring.package=org.apache.sling.api.resource)(version>=2.12.0)(!(v
> ersion>=3.0.0))) Unresolved requirements: [[org.apache.sling.models.impl
> [147](R 147.0)] osgi.wiring.package;
> (&(osgi.wiring.package=org.apache.sling.api.resource)(version>=2.12.0)(!(v
> ersion>=3.0.0)))]”
>
> Two options come to my mind:
> a) Switch IT to Sling Starter 12 (requires some effort due to the change
> from the Sling Provisioning Model to the OSGi Feature Model)
> b) Tweak Starter 11 with newer versions of particular bundles required for
> Sling Models
>
> We probably need to pay more attention that at least before releasing
> Sling Models the ITs are executed successfully. I admit though that due to
> the distributed nature of the repositories I often forget about those
> myself. Any hints how to make the linking between API, Implementation and
> IT repos more prominent?
>
> Thanks,
> Konrad
Sling Models Integration Tests broken
HI,
The ITs at
https://github.com/apache/sling-org-apache-sling-models-integration-tests built
through
https://ci-builds.apache.org/blue/organizations/jenkins/Sling%2Fmodules%2Fsling-org-apache-sling-models-integration-tests/activity
are failing since quite some time and also reference pretty outdated Sling
Models bundle versions.
Seems that the root issue is that even that outdated version of Models Impl
(1.5.3-SNAPSHOT,
https://github.com/apache/sling-org-apache-sling-models-integration-tests/blob/3a20ea6b8e2cd025e396797be94b8268a240efae/pom.xml#L261C30-L261C30)
requires a newer version of Sling API than shipped with Sling Starter 11:
"06.07.2023 18:29:43.869 *INFO* [OsgiInstallerImpl]
org.apache.sling.installer.core.impl.tasks.BundleStartTask Could not start
bundle org.apache.sling.models.impl [147]. Reason: {}. Will retry.
org.osgi.framework.BundleException: Unable to resolve
org.apache.sling.models.impl [147](R 147.0): missing requirement
[org.apache.sling.models.impl [147](R 147.0)] osgi.wiring.package;
(&(osgi.wiring.package=org.apache.sling.api.resource)(version>=2.12.0)(!(version>=3.0.0)))
Unresolved requirements: [[org.apache.sling.models.impl [147](R 147.0)]
osgi.wiring.package;
(&(osgi.wiring.package=org.apache.sling.api.resource)(version>=2.12.0)(!(version>=3.0.0)))]”
Two options come to my mind:
a) Switch IT to Sling Starter 12 (requires some effort due to the change from
the Sling Provisioning Model to the OSGi Feature Model)
b) Tweak Starter 11 with newer versions of particular bundles required for
Sling Models
We probably need to pay more attention that at least before releasing Sling
Models the ITs are executed successfully. I admit though that due to the
distributed nature of the repositories I often forget about those myself. Any
hints how to make the linking between API, Implementation and IT repos more
prominent?
Thanks,
Konrad
[jira] [Resolved] (SLING-11937) sling-maven-plugin: Unstable ITs: Uninstall bundle returns a 404
[
https://issues.apache.org/jira/browse/SLING-11937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus resolved SLING-11937.
-
Fix Version/s: Sling Maven Plugin 3.0.4
Resolution: Fixed
Fixed with
https://github.com/apache/sling-maven-plugin/commit/5e65bb7aa0bdd63db3dd4a1cd7d7087c27662c80.
> sling-maven-plugin: Unstable ITs: Uninstall bundle returns a 404
>
>
> Key: SLING-11937
> URL: https://issues.apache.org/jira/browse/SLING-11937
> Project: Sling
> Issue Type: Improvement
> Components: Maven Plugins and Archetypes
>Affects Versions: Sling Maven Plugin 3.0.2
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
> Fix For: Sling Maven Plugin 3.0.4
>
>
> The ITs for the sling-maven-plugin are unstable (particularly on Windows).
> They fail with
> {code}
> [INFO] --- sling:3.0.3-SNAPSHOT:install-file (bundle-install) @ example-pom
> ---
> [INFO] Downloading from central:
> https://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.commons.messaging/1.0.2/org.apache.sling.commons.messaging-1.0.2.jar
> [INFO] Downloaded from central:
> https://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.commons.messaging/1.0.2/org.apache.sling.commons.messaging-1.0.2.jar
> (9.1 kB at 27 kB/s)
> [INFO] Resolved artifact to
> F:\jenkins\jenkins-home\712657a4\workspace\odules_sling-maven-plugin_master\jdk_1.8_latest\.repository\org\apache\sling\org.apache.sling.commons.messaging\1.0.2\org.apache.sling.commons.messaging-1.0.2.jar
> [INFO] Installing Bundle
> org.apache.sling.commons.messaging(F:\jenkins\jenkins-home\712657a4\workspace\odules_sling-maven-plugin_master\jdk_1.8_latest\.repository\org\apache\sling\org.apache.sling.commons.messaging\1.0.2\org.apache.sling.commons.messaging-1.0.2.jar)
> to http://localhost:50972/system/console/ via WebConsole...
> [INFO] Bundle installed successfully
> [INFO]
> [INFO] --- sling:3.0.3-SNAPSHOT:uninstall (bundle-uninstall) @ example-pom ---
> [INFO] Uninstalling Bundle org.apache.sling.commons.messaging from
> http://localhost:50972/system/console/ via WebConsole...
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 1.721 s
> [INFO] Finished at: 2023-07-02T02:08:33Z
> [INFO]
>
> [INFO] [jenkins-event-spy] Generated
> F:\jenkins\jenkins-home\712657a4\workspace\odules_sling-maven-plugin_master\jdk_1.8_latest@tmp\withMaven4b5a6f97\maven-spy-20230702-020831-4455121863055328026922.log
> [ERROR] Failed to execute goal
> org.apache.sling:sling-maven-plugin:3.0.3-SNAPSHOT:uninstall
> (bundle-uninstall) on project example-pom: Uninstall from
> http://localhost:50972/system/console/ failed, cause: status code: 404,
> reason phrase: Not Found -> [Help 1]
> {code}
> (https://ci-builds.apache.org/blue/organizations/jenkins/Sling%2Fmodules%2Fsling-maven-plugin/detail/master/195/pipeline/)
> The reason is that the installation happens asynchronously in a background
> thread in
> https://github.com/apache/felix-dev/blob/8e35c940a95c91f3fee09c537dbaf9665e5d027e/webconsole/src/main/java/org/apache/felix/webconsole/internal/core/BundlesServlet.java#L1726,
> so there is a race condition if the uninstall is triggered before the
> installation in the background thread is finished.
> Also the documentation in
> https://sling.apache.org/components/sling-maven-plugin/bundle-installation.html
> currently incorrectly states:
> {quote}
> Felix Web Console
> The plugin by default places an HTTP POST request to the Felix Web Console.
> This will achieve both upload and installation of the bundle in one request
> synchronously.
> {quote}
> In fact this is an asynchronous operation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [sling-maven-plugin] kwin merged pull request #17: add sleep between install und uninstall
kwin merged PR #17: URL: https://github.com/apache/sling-maven-plugin/pull/17 -- 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
[GitHub] [sling-maven-plugin] sonarcloud[bot] commented on pull request #17: add sleep between install und uninstall
sonarcloud[bot] commented on PR #17: URL: https://github.com/apache/sling-maven-plugin/pull/17#issuecomment-1625501995 Kudos, SonarCloud Quality Gate passed! [](https://sonarcloud.io/dashboard?id=apache_sling-maven-plugin=17) [](https://sonarcloud.io/project/issues?id=apache_sling-maven-plugin=17=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-maven-plugin=17=false=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=apache_sling-maven-plugin=17=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-maven-plugin=17=false=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=apache_sling-maven-plugin=17=false=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_sling-maven-plugin=17=false=VULNERABILITY) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-maven-plugin=17=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-maven-plugin=17=false=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-maven-plugin=17=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/issues?id=apache_sling-maven-plugin=17=false=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=apache_sling-maven-plugin=17=false=CODE_SMELL) [0 Code Smells](https://sonarcloud.io/project/issues?id=apache_sling-maven-plugin=17=false=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=apache_sling-maven-plugin=17=coverage=list) No Coverage information [](https://sonarcloud.io/component_measures?id=apache_sling-maven-plugin=17=duplicated_lines_density=list) No Duplication information -- 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
[GitHub] [sling-whiteboard] sonarcloud[bot] commented on pull request #108: Bump jackson-databind from 2.13.3 to 2.13.4.2 in /org.apache.sling.jaxrs/bundle
sonarcloud[bot] commented on PR #108: URL: https://github.com/apache/sling-whiteboard/pull/108#issuecomment-1625494594 Kudos, SonarCloud Quality Gate passed! [](https://sonarcloud.io/dashboard?id=apache_sling-whiteboard=108) [](https://sonarcloud.io/project/issues?id=apache_sling-whiteboard=108=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-whiteboard=108=false=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=apache_sling-whiteboard=108=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-whiteboard=108=false=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=apache_sling-whiteboard=108=false=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_sling-whiteboard=108=false=VULNERABILITY) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-whiteboard=108=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-whiteboard=108=false=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-whiteboard=108=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/issues?id=apache_sling-whiteboard=108=false=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=apache_sling-whiteboard=108=false=CODE_SMELL) [0 Code Smells](https://sonarcloud.io/project/issues?id=apache_sling-whiteboard=108=false=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=apache_sling-whiteboard=108=coverage=list) No Coverage information [](https://sonarcloud.io/component_measures?id=apache_sling-whiteboard=108=duplicated_lines_density=list) No Duplication information -- 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
[GitHub] [sling-whiteboard] sonarcloud[bot] commented on pull request #107: Bump jackson-databind from 2.13.3 to 2.13.4.2 in /org.apache.sling.jaxrs/it
sonarcloud[bot] commented on PR #107: URL: https://github.com/apache/sling-whiteboard/pull/107#issuecomment-1625493860 Kudos, SonarCloud Quality Gate passed! [](https://sonarcloud.io/dashboard?id=apache_sling-whiteboard=107) [](https://sonarcloud.io/project/issues?id=apache_sling-whiteboard=107=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-whiteboard=107=false=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=apache_sling-whiteboard=107=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-whiteboard=107=false=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=apache_sling-whiteboard=107=false=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_sling-whiteboard=107=false=VULNERABILITY) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-whiteboard=107=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-whiteboard=107=false=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-whiteboard=107=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/issues?id=apache_sling-whiteboard=107=false=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=apache_sling-whiteboard=107=false=CODE_SMELL) [0 Code Smells](https://sonarcloud.io/project/issues?id=apache_sling-whiteboard=107=false=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=apache_sling-whiteboard=107=coverage=list) No Coverage information [](https://sonarcloud.io/component_measures?id=apache_sling-whiteboard=107=duplicated_lines_density=list) No Duplication information -- 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
[jira] [Resolved] (SLING-10873) Provide a generic Content Worker module
[ https://issues.apache.org/jira/browse/SLING-10873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz resolved SLING-10873. -- Fix Version/s: (was: Content Worker 1.0.0) Resolution: Won't Do > Provide a generic Content Worker module > --- > > Key: SLING-10873 > URL: https://issues.apache.org/jira/browse/SLING-10873 > Project: Sling > Issue Type: New Feature > Components: JCR, Oak >Reporter: Oliver Lietz >Assignee: Oliver Lietz >Priority: Major > > To support more AV solutions in Sling besides Clam a generic module is > required. > The module will use Commons Content Analyzing and Commons Content Processing > APIs to hook in various solutions including Sling Commons Clam. > The module will target AEMaaCS but stick to Sling and JCR/Oak APIs. > See also [Scanning for Malware in Apache Sling and Adobe Experience > Manager|https://adapt.to/2020/en/schedule/scanning-for-malware-in-apache-sling-and-aem.html] > and [Implement "Anti Virus" (Anti Maleware) scans in AEM Cloud Service > (AEMaaCS) - "Anti-Malware as a Cloud > Service"|https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager-ideas/implement-quot-anti-virus-quot-anti-maleware-scans-in-aem-cloud/idi-p/405511]. > *Mandatory features* > * Jobs > * JCR/Oak Observation > * Command via HTTP (work on demand) > *Optional features* > * Monitoring via HTTP > * Result handling -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-10873) Provide a generic Content Worker module
[ https://issues.apache.org/jira/browse/SLING-10873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz closed SLING-10873. > Provide a generic Content Worker module > --- > > Key: SLING-10873 > URL: https://issues.apache.org/jira/browse/SLING-10873 > Project: Sling > Issue Type: New Feature > Components: JCR, Oak >Reporter: Oliver Lietz >Assignee: Oliver Lietz >Priority: Major > > To support more AV solutions in Sling besides Clam a generic module is > required. > The module will use Commons Content Analyzing and Commons Content Processing > APIs to hook in various solutions including Sling Commons Clam. > The module will target AEMaaCS but stick to Sling and JCR/Oak APIs. > See also [Scanning for Malware in Apache Sling and Adobe Experience > Manager|https://adapt.to/2020/en/schedule/scanning-for-malware-in-apache-sling-and-aem.html] > and [Implement "Anti Virus" (Anti Maleware) scans in AEM Cloud Service > (AEMaaCS) - "Anti-Malware as a Cloud > Service"|https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager-ideas/implement-quot-anti-virus-quot-anti-maleware-scans-in-aem-cloud/idi-p/405511]. > *Mandatory features* > * Jobs > * JCR/Oak Observation > * Command via HTTP (work on demand) > *Optional features* > * Monitoring via HTTP > * Result handling -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-11791) Provide Commons Permissions Sling Option
[ https://issues.apache.org/jira/browse/SLING-11791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz closed SLING-11791. > Provide Commons Permissions Sling Option > > > Key: SLING-11791 > URL: https://issues.apache.org/jira/browse/SLING-11791 > Project: Sling > Issue Type: New Feature > Components: Testing >Reporter: Oliver Lietz >Assignee: Oliver Lietz >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-11341) Provide Commons Permissions API
[
https://issues.apache.org/jira/browse/SLING-11341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz closed SLING-11341.
> Provide Commons Permissions API
> ---
>
> Key: SLING-11341
> URL: https://issues.apache.org/jira/browse/SLING-11341
> Project: Sling
> Issue Type: New Feature
> Components: Commons
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
>Priority: Major
>
> {noformat}
> PermissionsService#hasPermission(principal:Principal,
> permission:String):boolean
> {noformat}
> https://github.com/apache/sling-org-apache-sling-commons-permissions
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (SLING-11341) Provide Commons Permissions API
[
https://issues.apache.org/jira/browse/SLING-11341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz resolved SLING-11341.
--
Fix Version/s: (was: Commons Permissions 1.0.0)
Resolution: Won't Do
> Provide Commons Permissions API
> ---
>
> Key: SLING-11341
> URL: https://issues.apache.org/jira/browse/SLING-11341
> Project: Sling
> Issue Type: New Feature
> Components: Commons
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
>Priority: Major
>
> {noformat}
> PermissionsService#hasPermission(principal:Principal,
> permission:String):boolean
> {noformat}
> https://github.com/apache/sling-org-apache-sling-commons-permissions
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (SLING-11688) Provide Commons Permissions Sling
[ https://issues.apache.org/jira/browse/SLING-11688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz closed SLING-11688. > Provide Commons Permissions Sling > - > > Key: SLING-11688 > URL: https://issues.apache.org/jira/browse/SLING-11688 > Project: Sling > Issue Type: New Feature > Components: Commons, JCR >Reporter: Oliver Lietz >Assignee: Oliver Lietz >Priority: Major > > Implementation of the Sling Commons Permissions API based on Sling Resource > and JCR APIs > https://github.com/apache/sling-org-apache-sling-commons-permissions-sling -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-11790) Provide Commons Permissions Option
[ https://issues.apache.org/jira/browse/SLING-11790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz closed SLING-11790. > Provide Commons Permissions Option > -- > > Key: SLING-11790 > URL: https://issues.apache.org/jira/browse/SLING-11790 > Project: Sling > Issue Type: New Feature > Components: Testing >Reporter: Oliver Lietz >Assignee: Oliver Lietz >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (SLING-11688) Provide Commons Permissions Sling
[ https://issues.apache.org/jira/browse/SLING-11688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz resolved SLING-11688. -- Fix Version/s: (was: Commons Permissions Sling 1.0.0) Resolution: Won't Do > Provide Commons Permissions Sling > - > > Key: SLING-11688 > URL: https://issues.apache.org/jira/browse/SLING-11688 > Project: Sling > Issue Type: New Feature > Components: Commons, JCR >Reporter: Oliver Lietz >Assignee: Oliver Lietz >Priority: Major > > Implementation of the Sling Commons Permissions API based on Sling Resource > and JCR APIs > https://github.com/apache/sling-org-apache-sling-commons-permissions-sling -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (SLING-11791) Provide Commons Permissions Sling Option
[ https://issues.apache.org/jira/browse/SLING-11791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz resolved SLING-11791. -- Fix Version/s: (was: Testing PaxExam 4.0.0) Resolution: Won't Do > Provide Commons Permissions Sling Option > > > Key: SLING-11791 > URL: https://issues.apache.org/jira/browse/SLING-11791 > Project: Sling > Issue Type: New Feature > Components: Testing >Reporter: Oliver Lietz >Assignee: Oliver Lietz >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (SLING-11790) Provide Commons Permissions Option
[ https://issues.apache.org/jira/browse/SLING-11790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz resolved SLING-11790. -- Fix Version/s: (was: Testing PaxExam 4.0.0) Resolution: Won't Do > Provide Commons Permissions Option > -- > > Key: SLING-11790 > URL: https://issues.apache.org/jira/browse/SLING-11790 > Project: Sling > Issue Type: New Feature > Components: Testing >Reporter: Oliver Lietz >Assignee: Oliver Lietz >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [sling-maven-plugin] sonarcloud[bot] commented on pull request #17: add sleep between install und uninstall
sonarcloud[bot] commented on PR #17: URL: https://github.com/apache/sling-maven-plugin/pull/17#issuecomment-1625378029 Kudos, SonarCloud Quality Gate passed! [](https://sonarcloud.io/dashboard?id=apache_sling-maven-plugin=17) [](https://sonarcloud.io/project/issues?id=apache_sling-maven-plugin=17=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-maven-plugin=17=false=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=apache_sling-maven-plugin=17=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-maven-plugin=17=false=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=apache_sling-maven-plugin=17=false=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_sling-maven-plugin=17=false=VULNERABILITY) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-maven-plugin=17=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-maven-plugin=17=false=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-maven-plugin=17=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/issues?id=apache_sling-maven-plugin=17=false=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=apache_sling-maven-plugin=17=false=CODE_SMELL) [0 Code Smells](https://sonarcloud.io/project/issues?id=apache_sling-maven-plugin=17=false=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=apache_sling-maven-plugin=17=coverage=list) No Coverage information [](https://sonarcloud.io/component_measures?id=apache_sling-maven-plugin=17=duplicated_lines_density=list) No Duplication information -- 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
[jira] [Closed] (SLING-11788) Provide Commons Permissions Sling feature
[ https://issues.apache.org/jira/browse/SLING-11788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz closed SLING-11788. > Provide Commons Permissions Sling feature > - > > Key: SLING-11788 > URL: https://issues.apache.org/jira/browse/SLING-11788 > Project: Sling > Issue Type: New Feature > Components: Karaf >Reporter: Oliver Lietz >Assignee: Oliver Lietz >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-11787) Provide Commons Permissions feature
[ https://issues.apache.org/jira/browse/SLING-11787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz closed SLING-11787. > Provide Commons Permissions feature > --- > > Key: SLING-11787 > URL: https://issues.apache.org/jira/browse/SLING-11787 > Project: Sling > Issue Type: New Feature > Components: Karaf >Reporter: Oliver Lietz >Assignee: Oliver Lietz >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (SLING-11788) Provide Commons Permissions Sling feature
[ https://issues.apache.org/jira/browse/SLING-11788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz resolved SLING-11788. -- Fix Version/s: (was: Karaf Features 1.0.0) (was: Karaf Integration Tests 1.0.0) (was: Karaf Distribution 1.0.0) (was: Karaf Configs 1.0.0) Resolution: Won't Do > Provide Commons Permissions Sling feature > - > > Key: SLING-11788 > URL: https://issues.apache.org/jira/browse/SLING-11788 > Project: Sling > Issue Type: New Feature > Components: Karaf >Reporter: Oliver Lietz >Assignee: Oliver Lietz >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (SLING-11787) Provide Commons Permissions feature
[ https://issues.apache.org/jira/browse/SLING-11787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz resolved SLING-11787. -- Fix Version/s: (was: Karaf Features 1.0.0) (was: Karaf Integration Tests 1.0.0) (was: Karaf Distribution 1.0.0) Resolution: Won't Do > Provide Commons Permissions feature > --- > > Key: SLING-11787 > URL: https://issues.apache.org/jira/browse/SLING-11787 > Project: Sling > Issue Type: New Feature > Components: Karaf >Reporter: Oliver Lietz >Assignee: Oliver Lietz >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[Jenkins] Sling » Modules » sling-org-apache-sling-starter » master #905 is FIXED
Please see https://ci-builds.apache.org/job/Sling/job/modules/job/sling-org-apache-sling-starter/job/master/905/ for details. No further emails will be sent until the status of the build is changed.
[GitHub] [sling-org-apache-sling-models-jacksonexporter] sonarcloud[bot] commented on pull request #7: SLING-11924 disallow the serialization of a ResourceResolver
sonarcloud[bot] commented on PR #7: URL: https://github.com/apache/sling-org-apache-sling-models-jacksonexporter/pull/7#issuecomment-1625254101 Kudos, SonarCloud Quality Gate passed! [](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-models-jacksonexporter=7) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-models-jacksonexporter=7=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-models-jacksonexporter=7=false=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-models-jacksonexporter=7=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-models-jacksonexporter=7=false=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-models-jacksonexporter=7=false=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-models-jacksonexporter=7=false=VULNERABILITY) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-models-jacksonexporter=7=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-models-jacksonexporter=7=false=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-models-jacksonexporter=7=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-models-jacksonexporter=7=false=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-models-jacksonexporter=7=false=CODE_SMELL) [3 Code Smells](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-models-jacksonexporter=7=false=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-models-jacksonexporter=7=new_coverage=list) [94.7% Coverage](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-models-jacksonexporter=7=new_coverage=list) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-models-jacksonexporter=7=new_duplicated_lines_density=list) [0.0% Duplication](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-models-jacksonexporter=7=new_duplicated_lines_density=list) -- 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 Launcher Maven Plugin 0.1.6
+1 David On Fri, 7 Jul 2023 at 11:56, Robert Munteanu wrote: > Hi, > > We solved 1 issue in this release: > https://issues.apache.org/jira/browse/SLING/fixforversion/12352559 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2763/ > > 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 2763 /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, > Robert Munteanu >
Re: [VOTE] Release Apache Sling OSGi Feature Maven Plugin 1.7.2
+1 David On Fri, 7 Jul 2023 at 11:56, Carsten Ziegeler wrote: > +1 > > Carsten > > On 07.07.2023 12:53, Robert Munteanu wrote: > > Hi, > > > > We solved 2 issues in this release: > > https://issues.apache.org/jira/browse/SLING/fixforversion/12353301 > > > > Staging repository: > > https://repository.apache.org/content/repositories/orgapachesling-2762/ > > > > 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 2762 /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, > > Robert Munteanu > > -- > Carsten Ziegeler > Adobe > cziege...@apache.org >
Re: [VOTE] Release Apache Sling OSGi Feature Maven Plugin 1.7.2
+1 Carsten On 07.07.2023 12:53, Robert Munteanu wrote: Hi, We solved 2 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12353301 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-2762/ 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 2762 /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, Robert Munteanu -- Carsten Ziegeler Adobe cziege...@apache.org
[VOTE] Release Apache Sling Feature Launcher Maven Plugin 0.1.6
Hi, We solved 1 issue in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12352559 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-2763/ 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 2763 /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, Robert Munteanu
[jira] [Updated] (SLING-11934) Plug-in ITs fail on Windows
[
https://issues.apache.org/jira/browse/SLING-11934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-11934:
Fix Version/s: Feature Launcher Maven Plugin 0.1.8
(was: Feature Launcher Maven Plugin 0.1.6)
> Plug-in ITs fail on Windows
> ---
>
> Key: SLING-11934
> URL: https://issues.apache.org/jira/browse/SLING-11934
> Project: Sling
> Issue Type: Bug
>Reporter: Robert Munteanu
>Priority: Major
> Fix For: Feature Launcher Maven Plugin 0.1.8
>
>
> Seen at
> https://ci-builds.apache.org/blue/organizations/jenkins/Sling%2Fmodules%2Fsling-feature-launcher-maven-plugin/detail/master/179/pipeline/59
>
> {noformat}
> [INFO] --- invoker:3.3.0:integration-test (integration-test) @
> feature-launcher-maven-plugin ---
> [INFO] Building: empty-config-it\pom.xml
> [INFO] run post-build script verify.groovy
> [INFO] empty-config-it\pom.xml .. SUCCESS
> (39.8 s)
> [INFO] Building: simple-for-SLING-10956-it\pom.xml
> Sending interrupt signal to process
> [INFO] run post-build script verify.groovy
> [INFO] simple-for-SLING-10956-it\pom.xml SUCCESS
> (1622.0 s)
> [INFO] Building: simple-it\pom.xml
> script returned exit code -1
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (SLING-9581) Reduce implementation duplication between kickstart and feature-launcher maven plugin
[ https://issues.apache.org/jira/browse/SLING-9581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-9581: --- Fix Version/s: Feature Launcher Maven Plugin 0.1.8 (was: Feature Launcher Maven Plugin 0.1.6) > Reduce implementation duplication between kickstart and feature-launcher > maven plugin > - > > Key: SLING-9581 > URL: https://issues.apache.org/jira/browse/SLING-9581 > Project: Sling > Issue Type: Improvement > Components: Maven Plugins and Archetypes >Reporter: Robert Munteanu >Assignee: Robert Munteanu >Priority: Major > Fix For: Feature Model Sling Maven Kickstart Plugin 0.0.10, > Feature Model Sling Kickstart Project 0.0.14, Feature Launcher Maven Plugin > 0.1.8 > > > There is an implementation overlap between the kickstart tooling and the > feature-launcher maven plugin. We should remove it to ensure our tooling > behaves consistently. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SLING-11442) Allow blocking after the features have been launched
[
https://issues.apache.org/jira/browse/SLING-11442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-11442:
Fix Version/s: Feature Launcher Maven Plugin 0.1.8
(was: Feature Launcher Maven Plugin 0.1.6)
> Allow blocking after the features have been launched
>
>
> Key: SLING-11442
> URL: https://issues.apache.org/jira/browse/SLING-11442
> Project: Sling
> Issue Type: Improvement
> Components: Maven Plugins and Archetypes
>Reporter: Robert Munteanu
>Priority: Major
> Fix For: Feature Launcher Maven Plugin 0.1.8
>
>
> The plug-in is right now working well in non-interactive scenarios, where one
> or multiple features are launched, tests executed, then the features stopped.
> It would be useful to configure the plug-in to block after the features have
> been started, e.g. by waiting indefinitely or waiting for user input. This
> way it could be used in an interactive manner to launch an application, e.g.
> {noformat}$ mvn clean package feature-launcher:start{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[VOTE] Release Apache Sling OSGi Feature Maven Plugin 1.7.2
Hi, We solved 2 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12353301 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-2762/ 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 2762 /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, Robert Munteanu
[jira] [Updated] (SLING-11935) JarDecompressorTest.testWithEmbeddedJar fails on Jenkins/Windows
[
https://issues.apache.org/jira/browse/SLING-11935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-11935:
Fix Version/s: OSGi Feature Maven Plugin 1.7.4
(was: OSGi Feature Maven Plugin 1.7.2)
> JarDecompressorTest.testWithEmbeddedJar fails on Jenkins/Windows
>
>
> Key: SLING-11935
> URL: https://issues.apache.org/jira/browse/SLING-11935
> Project: Sling
> Issue Type: Bug
> Components: Feature Model, Maven Plugins and Archetypes
>Reporter: Robert Munteanu
>Priority: Major
> Fix For: OSGi Feature Maven Plugin 1.7.4
>
>
> This is the only CI failure, but I don't understand enough about the
> JarDecompressor to make an informed fix. I will ignore the test on Windows
> for now, but it would be great to understand the root cause and fix it.
> {noformat}[ERROR]
> org.apache.sling.feature.maven.mojos.JarDecompressorTest.testJarWithEmbeddedJar
> Time elapsed: 0.071 s <<< FAILURE!
> java.lang.AssertionError: expected:<2108> but was:<1984>
> at org.junit.Assert.fail(Assert.java:89)
> at org.junit.Assert.failNotEquals(Assert.java:835)
> at org.junit.Assert.assertEquals(Assert.java:647)
> at org.junit.Assert.assertEquals(Assert.java:633)
> at
> org.apache.sling.feature.maven.mojos.JarDecompressorTest.testJarWithEmbeddedJar(JarDecompressorTest.java:81)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at
> org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
> at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:364)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:237)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:158)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:428)
> at
> org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:162)
> at
> org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:562)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:548){noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (SLING-11937) sling-maven-plugin: Unstable ITs: Uninstall bundle returns a 404
[
https://issues.apache.org/jira/browse/SLING-11937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-11937:
Description:
The ITs for the sling-maven-plugin are unstable (particularly on Windows).
They fail with
{code}
[INFO] --- sling:3.0.3-SNAPSHOT:install-file (bundle-install) @ example-pom ---
[INFO] Downloading from central:
https://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.commons.messaging/1.0.2/org.apache.sling.commons.messaging-1.0.2.jar
[INFO] Downloaded from central:
https://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.commons.messaging/1.0.2/org.apache.sling.commons.messaging-1.0.2.jar
(9.1 kB at 27 kB/s)
[INFO] Resolved artifact to
F:\jenkins\jenkins-home\712657a4\workspace\odules_sling-maven-plugin_master\jdk_1.8_latest\.repository\org\apache\sling\org.apache.sling.commons.messaging\1.0.2\org.apache.sling.commons.messaging-1.0.2.jar
[INFO] Installing Bundle
org.apache.sling.commons.messaging(F:\jenkins\jenkins-home\712657a4\workspace\odules_sling-maven-plugin_master\jdk_1.8_latest\.repository\org\apache\sling\org.apache.sling.commons.messaging\1.0.2\org.apache.sling.commons.messaging-1.0.2.jar)
to http://localhost:50972/system/console/ via WebConsole...
[INFO] Bundle installed successfully
[INFO]
[INFO] --- sling:3.0.3-SNAPSHOT:uninstall (bundle-uninstall) @ example-pom ---
[INFO] Uninstalling Bundle org.apache.sling.commons.messaging from
http://localhost:50972/system/console/ via WebConsole...
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 1.721 s
[INFO] Finished at: 2023-07-02T02:08:33Z
[INFO]
[INFO] [jenkins-event-spy] Generated
F:\jenkins\jenkins-home\712657a4\workspace\odules_sling-maven-plugin_master\jdk_1.8_latest@tmp\withMaven4b5a6f97\maven-spy-20230702-020831-4455121863055328026922.log
[ERROR] Failed to execute goal
org.apache.sling:sling-maven-plugin:3.0.3-SNAPSHOT:uninstall (bundle-uninstall)
on project example-pom: Uninstall from http://localhost:50972/system/console/
failed, cause: status code: 404, reason phrase: Not Found -> [Help 1]
{code}
(https://ci-builds.apache.org/blue/organizations/jenkins/Sling%2Fmodules%2Fsling-maven-plugin/detail/master/195/pipeline/)
The reason is that the installation happens asynchronously in a background
thread in
https://github.com/apache/felix-dev/blob/8e35c940a95c91f3fee09c537dbaf9665e5d027e/webconsole/src/main/java/org/apache/felix/webconsole/internal/core/BundlesServlet.java#L1726,
so there is a race condition if the uninstall is triggered before the
installation in the background thread is finished.
Also the documentation in
https://sling.apache.org/components/sling-maven-plugin/bundle-installation.html
currently incorrectly states:
{quote}
Felix Web Console
The plugin by default places an HTTP POST request to the Felix Web Console.
This will achieve both upload and installation of the bundle in one request
synchronously.
{quote}
In fact this is an asynchronous operation.
was:
The ITs for the sling-maven-plugin are unstable (particularly on Windows).
They fail with
{code}
[INFO] --- sling:3.0.3-SNAPSHOT:install-file (bundle-install) @ example-pom ---
[INFO] Downloading from central:
https://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.commons.messaging/1.0.2/org.apache.sling.commons.messaging-1.0.2.jar
[INFO] Downloaded from central:
https://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.commons.messaging/1.0.2/org.apache.sling.commons.messaging-1.0.2.jar
(9.1 kB at 27 kB/s)
[INFO] Resolved artifact to
F:\jenkins\jenkins-home\712657a4\workspace\odules_sling-maven-plugin_master\jdk_1.8_latest\.repository\org\apache\sling\org.apache.sling.commons.messaging\1.0.2\org.apache.sling.commons.messaging-1.0.2.jar
[INFO] Installing Bundle
org.apache.sling.commons.messaging(F:\jenkins\jenkins-home\712657a4\workspace\odules_sling-maven-plugin_master\jdk_1.8_latest\.repository\org\apache\sling\org.apache.sling.commons.messaging\1.0.2\org.apache.sling.commons.messaging-1.0.2.jar)
to http://localhost:50972/system/console/ via WebConsole...
[INFO] Bundle installed successfully
[INFO]
[INFO] --- sling:3.0.3-SNAPSHOT:uninstall (bundle-uninstall) @ example-pom ---
[INFO] Uninstalling Bundle org.apache.sling.commons.messaging from
http://localhost:50972/system/console/ via WebConsole...
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 1.721 s
[INFO] Finished at: 2023-07-02T02:08:33Z
[INFO]
[INFO]
[jira] [Created] (SLING-11937) sling-maven-plugin: Unstable ITs: Uninstall bundle returns a 404
Konrad Windszus created SLING-11937:
---
Summary: sling-maven-plugin: Unstable ITs: Uninstall bundle
returns a 404
Key: SLING-11937
URL: https://issues.apache.org/jira/browse/SLING-11937
Project: Sling
Issue Type: Improvement
Components: Maven Plugins and Archetypes
Affects Versions: Sling Maven Plugin 3.0.2
Reporter: Konrad Windszus
Assignee: Konrad Windszus
The ITs for the sling-maven-plugin are unstable (particularly on Windows).
They fail with
{code}
[INFO] --- sling:3.0.3-SNAPSHOT:install-file (bundle-install) @ example-pom ---
[INFO] Downloading from central:
https://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.commons.messaging/1.0.2/org.apache.sling.commons.messaging-1.0.2.jar
[INFO] Downloaded from central:
https://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.commons.messaging/1.0.2/org.apache.sling.commons.messaging-1.0.2.jar
(9.1 kB at 27 kB/s)
[INFO] Resolved artifact to
F:\jenkins\jenkins-home\712657a4\workspace\odules_sling-maven-plugin_master\jdk_1.8_latest\.repository\org\apache\sling\org.apache.sling.commons.messaging\1.0.2\org.apache.sling.commons.messaging-1.0.2.jar
[INFO] Installing Bundle
org.apache.sling.commons.messaging(F:\jenkins\jenkins-home\712657a4\workspace\odules_sling-maven-plugin_master\jdk_1.8_latest\.repository\org\apache\sling\org.apache.sling.commons.messaging\1.0.2\org.apache.sling.commons.messaging-1.0.2.jar)
to http://localhost:50972/system/console/ via WebConsole...
[INFO] Bundle installed successfully
[INFO]
[INFO] --- sling:3.0.3-SNAPSHOT:uninstall (bundle-uninstall) @ example-pom ---
[INFO] Uninstalling Bundle org.apache.sling.commons.messaging from
http://localhost:50972/system/console/ via WebConsole...
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 1.721 s
[INFO] Finished at: 2023-07-02T02:08:33Z
[INFO]
[INFO] [jenkins-event-spy] Generated
F:\jenkins\jenkins-home\712657a4\workspace\odules_sling-maven-plugin_master\jdk_1.8_latest@tmp\withMaven4b5a6f97\maven-spy-20230702-020831-4455121863055328026922.log
[ERROR] Failed to execute goal
org.apache.sling:sling-maven-plugin:3.0.3-SNAPSHOT:uninstall (bundle-uninstall)
on project example-pom: Uninstall from http://localhost:50972/system/console/
failed, cause: status code: 404, reason phrase: Not Found -> [Help 1]
{code}
The reason is that the installation happens asynchronously in a background
thread in
https://github.com/apache/felix-dev/blob/8e35c940a95c91f3fee09c537dbaf9665e5d027e/webconsole/src/main/java/org/apache/felix/webconsole/internal/core/BundlesServlet.java#L1726,
so there is a race condition if the uninstall is triggered before the
installation in the background thread is finished.
Also the documentation in currently incorrectly states:
{quote}
Felix Web Console
The plugin by default places an HTTP POST request to the Felix Web Console.
This will achieve both upload and installation of the bundle in one request
synchronously.
{quote}
In fact this is an asynchronous operation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (SLING-11937) sling-maven-plugin: Unstable ITs: Uninstall bundle returns a 404
[
https://issues.apache.org/jira/browse/SLING-11937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-11937:
Description:
The ITs for the sling-maven-plugin are unstable (particularly on Windows).
They fail with
{code}
[INFO] --- sling:3.0.3-SNAPSHOT:install-file (bundle-install) @ example-pom ---
[INFO] Downloading from central:
https://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.commons.messaging/1.0.2/org.apache.sling.commons.messaging-1.0.2.jar
[INFO] Downloaded from central:
https://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.commons.messaging/1.0.2/org.apache.sling.commons.messaging-1.0.2.jar
(9.1 kB at 27 kB/s)
[INFO] Resolved artifact to
F:\jenkins\jenkins-home\712657a4\workspace\odules_sling-maven-plugin_master\jdk_1.8_latest\.repository\org\apache\sling\org.apache.sling.commons.messaging\1.0.2\org.apache.sling.commons.messaging-1.0.2.jar
[INFO] Installing Bundle
org.apache.sling.commons.messaging(F:\jenkins\jenkins-home\712657a4\workspace\odules_sling-maven-plugin_master\jdk_1.8_latest\.repository\org\apache\sling\org.apache.sling.commons.messaging\1.0.2\org.apache.sling.commons.messaging-1.0.2.jar)
to http://localhost:50972/system/console/ via WebConsole...
[INFO] Bundle installed successfully
[INFO]
[INFO] --- sling:3.0.3-SNAPSHOT:uninstall (bundle-uninstall) @ example-pom ---
[INFO] Uninstalling Bundle org.apache.sling.commons.messaging from
http://localhost:50972/system/console/ via WebConsole...
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 1.721 s
[INFO] Finished at: 2023-07-02T02:08:33Z
[INFO]
[INFO] [jenkins-event-spy] Generated
F:\jenkins\jenkins-home\712657a4\workspace\odules_sling-maven-plugin_master\jdk_1.8_latest@tmp\withMaven4b5a6f97\maven-spy-20230702-020831-4455121863055328026922.log
[ERROR] Failed to execute goal
org.apache.sling:sling-maven-plugin:3.0.3-SNAPSHOT:uninstall (bundle-uninstall)
on project example-pom: Uninstall from http://localhost:50972/system/console/
failed, cause: status code: 404, reason phrase: Not Found -> [Help 1]
{code}
(https://ci-builds.apache.org/blue/organizations/jenkins/Sling%2Fmodules%2Fsling-maven-plugin/detail/master/195/pipeline/)
The reason is that the installation happens asynchronously in a background
thread in
https://github.com/apache/felix-dev/blob/8e35c940a95c91f3fee09c537dbaf9665e5d027e/webconsole/src/main/java/org/apache/felix/webconsole/internal/core/BundlesServlet.java#L1726,
so there is a race condition if the uninstall is triggered before the
installation in the background thread is finished.
Also the documentation in currently incorrectly states:
{quote}
Felix Web Console
The plugin by default places an HTTP POST request to the Felix Web Console.
This will achieve both upload and installation of the bundle in one request
synchronously.
{quote}
In fact this is an asynchronous operation.
was:
The ITs for the sling-maven-plugin are unstable (particularly on Windows).
They fail with
{code}
[INFO] --- sling:3.0.3-SNAPSHOT:install-file (bundle-install) @ example-pom ---
[INFO] Downloading from central:
https://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.commons.messaging/1.0.2/org.apache.sling.commons.messaging-1.0.2.jar
[INFO] Downloaded from central:
https://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.commons.messaging/1.0.2/org.apache.sling.commons.messaging-1.0.2.jar
(9.1 kB at 27 kB/s)
[INFO] Resolved artifact to
F:\jenkins\jenkins-home\712657a4\workspace\odules_sling-maven-plugin_master\jdk_1.8_latest\.repository\org\apache\sling\org.apache.sling.commons.messaging\1.0.2\org.apache.sling.commons.messaging-1.0.2.jar
[INFO] Installing Bundle
org.apache.sling.commons.messaging(F:\jenkins\jenkins-home\712657a4\workspace\odules_sling-maven-plugin_master\jdk_1.8_latest\.repository\org\apache\sling\org.apache.sling.commons.messaging\1.0.2\org.apache.sling.commons.messaging-1.0.2.jar)
to http://localhost:50972/system/console/ via WebConsole...
[INFO] Bundle installed successfully
[INFO]
[INFO] --- sling:3.0.3-SNAPSHOT:uninstall (bundle-uninstall) @ example-pom ---
[INFO] Uninstalling Bundle org.apache.sling.commons.messaging from
http://localhost:50972/system/console/ via WebConsole...
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 1.721 s
[INFO] Finished at: 2023-07-02T02:08:33Z
[INFO]
[INFO] [jenkins-event-spy] Generated
