You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "kwin (via GitHub)" <gi...@apache.org> on 2025/10/08 10:29:16 UTC
[PR] SLING-12953 Manage Jakarta JSON-P 2.1 [sling-parent]
kwin opened a new pull request, #55:
URL: https://github.com/apache/sling-parent/pull/55
(no comment)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@sling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] SLING-12953 Manage Jakarta JSON-P 2.1 [sling-parent]
Posted by "rombert (via GitHub)" <gi...@apache.org>.
rombert commented on PR #55:
URL: https://github.com/apache/sling-parent/pull/55#issuecomment-3381162142
> I think the whole point of JSON-P is to program impl agnostic. Therefore at compile time only the API dependency should be leveraged. Wouldn't it work if you leverage commons johnzon only with `test` scope even you have the API with `compile` / `provided` scope?
Ah, right, that makes sense.
--
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-unsubscribe@sling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] SLING-12953 Manage Jakarta JSON-P 2.1 [sling-parent]
Posted by "kwin (via GitHub)" <gi...@apache.org>.
kwin merged PR #55:
URL: https://github.com/apache/sling-parent/pull/55
--
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-unsubscribe@sling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] SLING-12953 Manage Jakarta JSON-P 2.1 [sling-parent]
Posted by "sonarqubecloud[bot] (via GitHub)" <gi...@apache.org>.
sonarqubecloud[bot] commented on PR #55:
URL: https://github.com/apache/sling-parent/pull/55#issuecomment-3380870300
## [](https://sonarcloud.io/dashboard?id=apache_sling-parent&pullRequest=55) **Quality Gate passed**
Issues
 [0 New issues](https://sonarcloud.io/project/issues?id=apache_sling-parent&pullRequest=55&issueStatuses=OPEN,CONFIRMED&sinceLeakPeriod=true)
 [0 Accepted issues](https://sonarcloud.io/project/issues?id=apache_sling-parent&pullRequest=55&issueStatuses=ACCEPTED)
Measures
 [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-parent&pullRequest=55&issueStatuses=OPEN,CONFIRMED&sinceLeakPeriod=true)
 [0.0% Coverage on New Code](https://sonarcloud.io/component_measures?id=apache_sling-parent&pullRequest=55&metric=new_coverage&view=list)
 [0.0% Duplication on New Code](https://sonarcloud.io/component_measures?id=apache_sling-parent&pullRequest=55&metric=new_duplicated_lines_density&view=list)
[See analysis details on SonarQube Cloud](https://sonarcloud.io/dashboard?id=apache_sling-parent&pullRequest=55)
--
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-unsubscribe@sling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] SLING-12953 Manage Jakarta JSON-P 2.1 [sling-parent]
Posted by "kwin (via GitHub)" <gi...@apache.org>.
kwin commented on PR #55:
URL: https://github.com/apache/sling-parent/pull/55#issuecomment-3381086694
I think the whole point of JSON-P is to program impl agnostic. Therefore at compile time only the API dependency should be leveraged. Wouldn't it work if you leverage commons johnzon only with `test` scope even you have the API with `compile` / `provided` scope?
--
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-unsubscribe@sling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org