[GitHub] kwin commented on a change in pull request #1: Sling-7346-Json response converting response property value to string even if it is json object

kwin commented on a change in pull request #1: Sling-7346-Json response converting response property value to string even if it is json object URL: https://github.com/apache/sling-org-apache-sling-servlets-post/pull/1#discussion_r159595351 ## File path:

[jira] [Resolved] (SLING-7352) Validation IT: Deploy Validation API and Core Bundle only once

[ https://issues.apache.org/jira/browse/SLING-7352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved SLING-7352. Resolution: Fixed Fixed in

[jira] [Created] (SLING-7352) Validation IT: Deploy Validation API and Core Bundle only once

Konrad Windszus created SLING-7352: -- Summary: Validation IT: Deploy Validation API and Core Bundle only once Key: SLING-7352 URL: https://issues.apache.org/jira/browse/SLING-7352 Project: Sling

[jira] [Commented] (SLING-7346) Issues with custom fields in PostResponse as a result of fix for SLING-6681(Replace commons.json usage in org.apache.sling.servlets.post)

[ https://issues.apache.org/jira/browse/SLING-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16310914#comment-16310914 ] Rahul Bhardwaj commented on SLING-7346: --- PR -

[GitHub] bhardwajrahul20 opened a new pull request #1: Sling-7346-Json response converting response property value to string even if it is json object

bhardwajrahul20 opened a new pull request #1: Sling-7346-Json response converting response property value to string even if it is json object URL: https://github.com/apache/sling-org-apache-sling-servlets-post/pull/1 This

RE: [VOTE] Release Apache Sling Engine 2.6.12

+1

Re: [VOTE] Release Apache Sling Engine 2.6.12

I merged it back into master. On Wed, Jan 3, 2018 at 5:46 PM, Karl Pauls wrote: > rats, yes - i guess we can just merge the branch into master... > > > On Wednesday, January 3, 2018, Stefan Seifert > wrote: >> >> you did the release not on the master

[GitHub] karlpauls opened a new pull request #2: Sling 7349

karlpauls opened a new pull request #2: Sling 7349 URL: https://github.com/apache/sling-org-apache-sling-engine/pull/2 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub

[GitHub] karlpauls closed pull request #2: Sling 7349

karlpauls closed pull request #2: Sling 7349 URL: https://github.com/apache/sling-org-apache-sling-engine/pull/2 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and

Re: [VOTE] Release Apache Sling Engine 2.6.12

rats, yes - i guess we can just merge the branch into master... On Wednesday, January 3, 2018, Stefan Seifert wrote: > you did the release not on the master branch but on this branch - i > suppose by accident? >

RE: [VOTE] Release Apache Sling Engine 2.6.12

you did the release not on the master branch but on this branch - i suppose by accident? https://github.com/apache/sling-org-apache-sling-engine/tree/SLING-7349 stefan >-Original Message- >From: Karl Pauls [mailto:karlpa...@gmail.com] >Sent: Wednesday, January 3, 2018 4:08 PM >To: Sling

[VOTE] Release Apache Sling Engine 2.6.12

I would like to call a vote on the following release, Apache Sling Engine 2.6.12 We solved 1 issue in this release: https://issues.apache.org/jira/projects/SLING/versions/12342248 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1843/ You can use this UNIX

[jira] [Commented] (SLING-7351) Make the "dependencies.properties" visible for maven-failsafe-plugin

[ https://issues.apache.org/jira/browse/SLING-7351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309712#comment-16309712 ] Oliver Lietz commented on SLING-7351: - bq. I plan to do a release of it soon. Let's wait for Maven

[jira] [Resolved] (SLING-7351) Make the "dependencies.properties" visible for maven-failsafe-plugin

[ https://issues.apache.org/jira/browse/SLING-7351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz resolved SLING-7351. - Resolution: Done > Make the "dependencies.properties" visible for maven-failsafe-plugin >

[jira] [Assigned] (SLING-7351) Make the "dependencies.properties" visible for maven-failsafe-plugin

[ https://issues.apache.org/jira/browse/SLING-7351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz reassigned SLING-7351: --- Assignee: Oliver Lietz (was: Konrad Windszus) > Make the "dependencies.properties" visible

[jira] [Commented] (SLING-7351) Make the "dependencies.properties" visible for maven-failsafe-plugin

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

[jira] [Commented] (SLING-7351) Make the "dependencies.properties" visible for maven-failsafe-plugin

[ https://issues.apache.org/jira/browse/SLING-7351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309701#comment-16309701 ] ASF GitHub Bot commented on SLING-7351: --- kwin commented on issue #1: SLING-7351 include

[jira] [Commented] (SLING-7351) Make the "dependencies.properties" visible for maven-failsafe-plugin

[ https://issues.apache.org/jira/browse/SLING-7351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309699#comment-16309699 ] Konrad Windszus commented on SLING-7351: Even better. Can you apply that patch to parent? I plan

[GitHub] kwin closed pull request #1: SLING-7351 include 'META-INF/maven/dependencies.properties' in generated

kwin closed pull request #1: SLING-7351 include 'META-INF/maven/dependencies.properties' in generated URL: https://github.com/apache/sling-parent/pull/1 This is an automated message from the Apache Git Service. To respond

[GitHub] kwin commented on issue #1: SLING-7351 include 'META-INF/maven/dependencies.properties' in generated

kwin commented on issue #1: SLING-7351 include 'META-INF/maven/dependencies.properties' in generated URL: https://github.com/apache/sling-parent/pull/1#issuecomment-355021890 Solved differently (for details refer to https://issues.apache.org/jira/browse/SLING-7351).

[jira] [Updated] (SLING-7351) Make the "dependencies.properties" visible for maven-failsafe-plugin

[ https://issues.apache.org/jira/browse/SLING-7351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-7351: --- Summary: Make the "dependencies.properties" visible for maven-failsafe-plugin (was: Include

[jira] [Commented] (SLING-7351) Include the "dependencies.properties" file in the final JAR

[ https://issues.apache.org/jira/browse/SLING-7351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309689#comment-16309689 ] Oliver Lietz commented on SLING-7351: - [~kwin], patch looks good to me, but I suggest an even less

Re: Pax Exam not compatible with maven-failsafe-plugin 2.20.1

On Wednesday 03 January 2018 14:55:27 Konrad Windszus wrote: > Please check out https://issues.apache.org/jira/browse/SLING-7351 > and the attached PR > which should include that file in the generated bundle. Thanks, Konrad. See my comment - that

Re: Pax Exam not compatible with maven-failsafe-plugin 2.20.1

Please check out https://issues.apache.org/jira/browse/SLING-7351 and the attached PR which should include that file in the generated bundle. > On 3. Jan 2018, at 14:10, Konrad Windszus wrote: > > >> Pax Exam is running fine

[jira] [Commented] (SLING-7351) Include the "dependencies.properties" file in the final JAR

[ https://issues.apache.org/jira/browse/SLING-7351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309670#comment-16309670 ] ASF GitHub Bot commented on SLING-7351: --- kwin opened a new pull request #1: SLING-7351 include

[GitHub] kwin opened a new pull request #1: SLING-7351 include 'META-INF/maven/dependencies.properties' in generated

kwin opened a new pull request #1: SLING-7351 include 'META-INF/maven/dependencies.properties' in generated URL: https://github.com/apache/sling-parent/pull/1 bundle (in case it does exist below 'target/classes') This file is being referenced from ITs leveraging pax exam and must be

[jira] [Commented] (SLING-7347) Update plugins to the most recent versions

[ https://issues.apache.org/jira/browse/SLING-7347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309662#comment-16309662 ] Konrad Windszus commented on SLING-7347: The issue with pax exam is now tracked in SLING-7351. >

[jira] [Updated] (SLING-7351) Include the "dependencies.properties" file in the final JAR

[ https://issues.apache.org/jira/browse/SLING-7351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-7351: --- Description: With the upgrade of the maven-failsafe-plugin in SLING-7347 pax-exam based

[jira] [Issue Comment Deleted] (SLING-7347) Update plugins to the most recent versions

[ https://issues.apache.org/jira/browse/SLING-7347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-7347: --- Comment: was deleted (was: {noformat}

[jira] [Created] (SLING-7351) Include the "dependencies.properties" file in the final JAR

Konrad Windszus created SLING-7351: -- Summary: Include the "dependencies.properties" file in the final JAR Key: SLING-7351 URL: https://issues.apache.org/jira/browse/SLING-7351 Project: Sling

Re: [VOTE] Release Apache Sling Log Tracer 1.0.6

+1 On Wed, Jan 3, 2018 at 7:44 AM, Karl Pauls wrote: > +1 > > regards, > > Karl > > On Wed, Jan 3, 2018 at 1:24 PM, Stefan Seifert > wrote: > > +1 > > > > > > -- > Karl Pauls > karlpa...@gmail.com >

[jira] [Commented] (SLING-7350) StreamRendererServlet redirects HEAD requests to external uri if available

[ https://issues.apache.org/jira/browse/SLING-7350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309646#comment-16309646 ] Ian Boston commented on SLING-7350: --- Patch LGTM. Could you open a pull request please. >

Re: Pax Exam not compatible with maven-failsafe-plugin 2.20.1

> Pax Exam is running fine with the generated JAR and only META- > INF/maven/dependencies.properties is missing for depends-maven-plugin. > > Therefore I prefer a third option which is configured in Parent, adds > dependencies.properties to the JAR if present and leaves everything else as >

[jira] [Resolved] (SLING-7349) Plain Servlets registered with the org.apache.sling HTTP Context cannot get requests parameters from POST body

[ https://issues.apache.org/jira/browse/SLING-7349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved SLING-7349. --- Resolution: Fixed Fixed by registering a servlet filter with the org.apache.sling HttpContext that

[jira] [Commented] (SLING-7349) Plain Servlets registered with the org.apache.sling HTTP Context cannot get requests parameters from POST body

[ https://issues.apache.org/jira/browse/SLING-7349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309609#comment-16309609 ] ASF GitHub Bot commented on SLING-7349: --- karlpauls closed pull request #1: SLING-7349: register a

[jira] [Commented] (SLING-7349) Plain Servlets registered with the org.apache.sling HTTP Context cannot get requests parameters from POST body

[ https://issues.apache.org/jira/browse/SLING-7349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309607#comment-16309607 ] ASF GitHub Bot commented on SLING-7349: --- karlpauls opened a new pull request #1: SLING-7349:

[GitHub] karlpauls closed pull request #1: SLING-7349: register a servlet filter with the org.apache.sling HttpC?

karlpauls closed pull request #1: SLING-7349: register a servlet filter with the org.apache.sling HttpC? URL: https://github.com/apache/sling-org-apache-sling-engine/pull/1 This is an automated message from the Apache Git

[GitHub] karlpauls opened a new pull request #1: SLING-7349: register a servlet filter with the org.apache.sling HttpC?

karlpauls opened a new pull request #1: SLING-7349: register a servlet filter with the org.apache.sling HttpC? URL: https://github.com/apache/sling-org-apache-sling-engine/pull/1 ?ontext that ensures that requests will use the ParameterSupport used during handleSecurity when no

[jira] [Comment Edited] (SLING-7350) StreamRendererServlet redirects HEAD requests to external uri if available

[ https://issues.apache.org/jira/browse/SLING-7350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309604#comment-16309604 ] Satya Deep Maheshwari edited comment on SLING-7350 at 1/3/18 12:54 PM:

[jira] [Commented] (SLING-7349) Plain Servlets registered with the org.apache.sling HTTP Context cannot get requests parameters from POST body

[ https://issues.apache.org/jira/browse/SLING-7349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309603#comment-16309603 ] Karl Pauls commented on SLING-7349: --- The reason is that we need to look at the post parameters during

[jira] [Updated] (SLING-7350) StreamRendererServlet redirects HEAD requests to external uri if available

[ https://issues.apache.org/jira/browse/SLING-7350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Satya Deep Maheshwari updated SLING-7350: - Attachment: SLING-7350.diff Attaching a proposed change. cc [~i...@tfd.co.uk] >

[jira] [Created] (SLING-7350) StreamRendererServlet redirects HEAD requests to external uri if available

Satya Deep Maheshwari created SLING-7350: Summary: StreamRendererServlet redirects HEAD requests to external uri if available Key: SLING-7350 URL: https://issues.apache.org/jira/browse/SLING-7350

[jira] [Created] (SLING-7349) Plain Servlets registered with the org.apache.sling HTTP Context cannot get requests parameters from POST body

Karl Pauls created SLING-7349: - Summary: Plain Servlets registered with the org.apache.sling HTTP Context cannot get requests parameters from POST body Key: SLING-7349 URL:

Re: Pax Exam not compatible with maven-failsafe-plugin 2.20.1

On Wednesday 03 January 2018 13:35:13 Konrad Windszus wrote: > > Adding an additionalClasspathElement in Parent (see my comment in > > SLING-7347) or a third option as 1) will not work in Parent. > > > > O. > > > > p.s.: the issue is with depends-maven-plugin not Exam itself > > I am not sure I

Re: [VOTE] Release Apache Sling Log Tracer 1.0.6

+1 regards, Karl On Wed, Jan 3, 2018 at 1:24 PM, Stefan Seifert wrote: > +1 > -- Karl Pauls karlpa...@gmail.com

Re: [VOTE] Release Apache Sling XSS Protection API 2.0.4

+1 regards, Karl On Wed, Jan 3, 2018 at 1:24 PM, Stefan Seifert wrote: > +1 -- Karl Pauls karlpa...@gmail.com

Re: Pax Exam not compatible with maven-failsafe-plugin 2.20.1

> > Adding an additionalClasspathElement in Parent (see my comment in SLING-7347) > or a third option as 1) will not work in Parent. > > O. > > p.s.: the issue is with depends-maven-plugin not Exam itself I am not sure I can follow here. Actually adding org.apache.maven.plugins

Re: Pax Exam not compatible with maven-failsafe-plugin 2.20.1

On Wednesday 03 January 2018 13:08:45 Konrad Windszus wrote: > When running mvn verify on Sling Scripting Groovy with the most recent > version of the maven-failsafe-plugin the following exceptions are emitted > from the ITs (leveraging Pax-Exam): > > [ERROR] Tests run: 1, Failures: 0, Errors: 1,

[jira] [Commented] (SLING-7347) Update plugins to the most recent versions

[ https://issues.apache.org/jira/browse/SLING-7347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309578#comment-16309578 ] Oliver Lietz commented on SLING-7347: - {noformat}

RE: [VOTE] Release Apache Sling Log Tracer 1.0.6

+1

RE: [VOTE] Release Apache Sling XSS Protection API 2.0.4

+1

[jira] [Commented] (SLING-7347) Update plugins to the most recent versions

[ https://issues.apache.org/jira/browse/SLING-7347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309562#comment-16309562 ] Konrad Windszus commented on SLING-7347: Exactly, I just sent out a proposal in

Pax Exam not compatible with maven-failsafe-plugin 2.20.1

When running mvn verify on Sling Scripting Groovy with the most recent version of the maven-failsafe-plugin the following exceptions are emitted from the ITs (leveraging Pax-Exam): [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.083 s <<< FAILURE! - in

[jira] [Commented] (SLING-7347) Update plugins to the most recent versions

[ https://issues.apache.org/jira/browse/SLING-7347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309556#comment-16309556 ] Oliver Lietz commented on SLING-7347: - [~kwin], the issue in Scripting Groovy is related to

Re: [VOTE] Release Apache Sling Log Tracer 1.0.6

Correction - We solved 1 issue in this release +1 Approve the releases Chetan Mehrotra On Wed, Jan 3, 2018 at 4:58 PM, Chetan Mehrotra wrote: > I would like to call a vote on the following release, > > Apache Sling Log Tracer 1.0.6 > > We solved 2 issue in this

[VOTE] Release Apache Sling Log Tracer 1.0.6

I would like to call a vote on the following release, Apache Sling Log Tracer 1.0.6 We solved 2 issue in this release: https://issues.apache.org/jira/projects/SLING/versions/12340678 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1842/ You can use this

[jira] [Resolved] (SLING-7348) Switch to OSGi annotation for Tracer bundle

[ https://issues.apache.org/jira/browse/SLING-7348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chetan Mehrotra resolved SLING-7348. Resolution: Fixed Done with

[jira] [Updated] (SLING-5669) Restrict usage of log tracing feature with access control

[ https://issues.apache.org/jira/browse/SLING-5669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chetan Mehrotra updated SLING-5669: --- Fix Version/s: (was: Log Tracer 1.0.6) Log Tracer 1.0.8 > Restrict

[jira] [Commented] (SLING-7347) Update plugins to the most recent versions

[ https://issues.apache.org/jira/browse/SLING-7347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309487#comment-16309487 ] Konrad Windszus commented on SLING-7347: bq. I guess you mean SLING-7334 instead of SLING-2334,

[jira] [Created] (SLING-7348) Switch to OSGi annotation for Tracer bundle

Chetan Mehrotra created SLING-7348: -- Summary: Switch to OSGi annotation for Tracer bundle Key: SLING-7348 URL: https://issues.apache.org/jira/browse/SLING-7348 Project: Sling Issue Type:

[jira] [Assigned] (SLING-7346) Issues with custom fields in PostResponse as a result of fix for SLING-6681(Replace commons.json usage in org.apache.sling.servlets.post)

[ https://issues.apache.org/jira/browse/SLING-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls reassigned SLING-7346: - Assignee: Karl Pauls > Issues with custom fields in PostResponse as a result of fix for >

[jira] [Updated] (SLING-7346) Issues with custom fields in PostResponse as a result of fix for SLING-6681(Replace commons.json usage in org.apache.sling.servlets.post)

[ https://issues.apache.org/jira/browse/SLING-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls updated SLING-7346: -- Affects Version/s: Servlets Post 2.3.22 > Issues with custom fields in PostResponse as a result of fix

[jira] [Updated] (SLING-7346) Issues with custom fields in PostResponse as a result of fix for SLING-6681(Replace commons.json usage in org.apache.sling.servlets.post)

[ https://issues.apache.org/jira/browse/SLING-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls updated SLING-7346: -- Fix Version/s: Servlets Post 2.3.24 > Issues with custom fields in PostResponse as a result of fix for

[jira] [Comment Edited] (SLING-7347) Update plugins to the most recent versions

[ https://issues.apache.org/jira/browse/SLING-7347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309425#comment-16309425 ] Konrad Windszus edited comment on SLING-7347 at 1/3/18 11:05 AM: - [~olli]

[jira] [Commented] (SLING-7347) Update plugins to the most recent versions

[ https://issues.apache.org/jira/browse/SLING-7347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309480#comment-16309480 ] Oliver Lietz commented on SLING-7347: - [~kwin], I guess you mean SLING-7334 instead of SLING-2334,

[jira] [Commented] (SLING-7318) PreparePackageMojoTest.testSubsystemBaseGeneration fails intermittently

[ https://issues.apache.org/jira/browse/SLING-7318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309478#comment-16309478 ] Konrad Windszus commented on SLING-7318: The exception message is still not being complete due to

[jira] [Commented] (SLING-7347) Update plugins to the most recent versions

[ https://issues.apache.org/jira/browse/SLING-7347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309465#comment-16309465 ] Konrad Windszus commented on SLING-7347: I think this

[jira] [Commented] (SLING-7347) Update plugins to the most recent versions

[ https://issues.apache.org/jira/browse/SLING-7347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309448#comment-16309448 ] Oliver Lietz commented on SLING-7347: - [~kwin], you can find some posts related to issues with those

[jira] [Commented] (SLING-7334) slingstart-maven-plugin: DependencyLifecycleParticipant must only consider Maven modules leveraging the same version of slingstart-m-p

[ https://issues.apache.org/jira/browse/SLING-7334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309431#comment-16309431 ] Konrad Windszus commented on SLING-7334: Fixed in

[jira] [Commented] (SLING-7334) slingstart-maven-plugin: DependencyLifecycleParticipant must only consider Maven modules leveraging the same version of slingstart-m-p

[ https://issues.apache.org/jira/browse/SLING-7334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309430#comment-16309430 ] ASF GitHub Bot commented on SLING-7334: --- kwin closed pull request #3: SLING-7334 only consider Maven

[GitHub] kwin closed pull request #3: SLING-7334 only consider Maven modules leveraging the same version of

kwin closed pull request #3: SLING-7334 only consider Maven modules leveraging the same version of URL: https://github.com/apache/sling-slingstart-maven-plugin/pull/3 This is an automated message from the Apache Git

[jira] [Commented] (SLING-7347) Update plugins to the most recent versions

[ https://issues.apache.org/jira/browse/SLING-7347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309425#comment-16309425 ] Konrad Windszus commented on SLING-7347: [~olli] Do you have any reference for those being broken?

[jira] [Reopened] (SLING-7347) Update plugins to the most recent versions

[ https://issues.apache.org/jira/browse/SLING-7347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz reopened SLING-7347: - [~kwin], {{maven-failsafe-plugin}} and {{maven-surefire-plugin}} newer {{2.18.1}} are still broken.

[jira] [Resolved] (SLING-7347) Update plugins to the most recent versions

[ https://issues.apache.org/jira/browse/SLING-7347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved SLING-7347. Resolution: Fixed Fixed in

[jira] [Assigned] (SLING-7347) Update plugins to the most recent versions

[ https://issues.apache.org/jira/browse/SLING-7347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus reassigned SLING-7347: -- Assignee: Konrad Windszus > Update plugins to the most recent versions >

[jira] [Updated] (SLING-7347) Update plugins to the most recent versions

[ https://issues.apache.org/jira/browse/SLING-7347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-7347: --- Description: When executing {{mvn

[jira] [Created] (SLING-7347) Update plugins to the most recent versions

Konrad Windszus created SLING-7347: -- Summary: Update plugins to the most recent versions Key: SLING-7347 URL: https://issues.apache.org/jira/browse/SLING-7347 Project: Sling Issue Type:

[jira] [Created] (SLING-7346) Issues with custom fields in PostResponse as a result of fix for SLING-6681(Replace commons.json usage in org.apache.sling.servlets.post)

Rahul Bhardwaj created SLING-7346: - Summary: Issues with custom fields in PostResponse as a result of fix for SLING-6681(Replace commons.json usage in org.apache.sling.servlets.post) Key: SLING-7346 URL:

[jira] [Resolved] (SLING-7345) Remove plugin versions from reporting section

[ https://issues.apache.org/jira/browse/SLING-7345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved SLING-7345. Resolution: Fixed Fixed in

[jira] [Created] (SLING-7345) Remove plugin versions from reporting section

Konrad Windszus created SLING-7345: -- Summary: Remove plugin versions from reporting section Key: SLING-7345 URL: https://issues.apache.org/jira/browse/SLING-7345 Project: Sling Issue Type: