[jira] [Created] (SLING-6603) Update FreeMarker to 2.3.25-incubating
Oliver Lietz created SLING-6603: --- Summary: Update FreeMarker to 2.3.25-incubating Key: SLING-6603 URL: https://issues.apache.org/jira/browse/SLING-6603 Project: Sling Issue Type: Improvement Components: Scripting Reporter: Oliver Lietz Assignee: Oliver Lietz Fix For: Scripting FreeMarker 1.0.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
ResourceResolverFactoryActivator: if/else contains same code related to legacy required providers
Hi, I think the code is using the same warning for the if/else branches. Is this on purpose? Thanks, Robert [1]: https://github.com/apache/sling/blob/f96c59667877297a994a2f5d7e710 664e1848c26/bundles/resourceresolver/src/main/java/org/apache/sling/res ourceresolver/impl/ResourceResolverFactoryActivator.java#L362-L370
Re: [VOTE] Release Apache Sling Scripting Core 2.0.46
+1 checked signatures and build. On Fri, Mar 3, 2017 at 5:42 AM, Oliver Lietz wrote: > Hi, > > we solved 3 issues in this release: > https://issues.apache.org/jira/browse/SLING/fixforversion/12339253 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-1656/ > > You can use this UNIX script to download the release and verify the > signatures: > http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh > > Usage: > sh check_staged_release.sh 1656 /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, > O. > >
Re: [VOTE] Release Apache Sling Health Check Core 1.2.6
+1 checked signatures and build On Fri, Mar 3, 2017 at 9:23 AM, Oliver Lietz wrote: > Hi, > > we solved 7 issues in this release: > https://issues.apache.org/jira/browse/SLING/fixforversion/12335062 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-1657/ > > You can use this UNIX script to download the release and verify the > signatures: > http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh > > Usage: > sh check_staged_release.sh 1657 /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, > O. > >
[jira] [Resolved] (SLING-6602) Add JSR305 nullness annotations to AbstractResourceVisitor
[
https://issues.apache.org/jira/browse/SLING-6602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus resolved SLING-6602.
Resolution: Fixed
Fixed in [r1785351|http://svn.apache.org/r1785351].
> Add JSR305 nullness annotations to AbstractResourceVisitor
> --
>
> Key: SLING-6602
> URL: https://issues.apache.org/jira/browse/SLING-6602
> Project: Sling
> Issue Type: Improvement
>Affects Versions: API 2.16.2
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>
> {{o.a.s.api.resource.AbstractResourceVisitor}} is lacking the JSR 305
> nullness annotations.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (SLING-6602) Add JSR305 nullness annotations to AbstractResourceVisitor
[
https://issues.apache.org/jira/browse/SLING-6602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-6602:
---
Fix Version/s: API 2.16.4
> Add JSR305 nullness annotations to AbstractResourceVisitor
> --
>
> Key: SLING-6602
> URL: https://issues.apache.org/jira/browse/SLING-6602
> Project: Sling
> Issue Type: Improvement
>Affects Versions: API 2.16.2
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
> Fix For: API 2.16.4
>
>
> {{o.a.s.api.resource.AbstractResourceVisitor}} is lacking the JSR 305
> nullness annotations.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (SLING-6602) Add JSR305 nullness annotations to AbstractResourceVisitor
Konrad Windszus created SLING-6602:
--
Summary: Add JSR305 nullness annotations to AbstractResourceVisitor
Key: SLING-6602
URL: https://issues.apache.org/jira/browse/SLING-6602
Project: Sling
Issue Type: Improvement
Affects Versions: API 2.16.2
Reporter: Konrad Windszus
Assignee: Konrad Windszus
{{o.a.s.api.resource.AbstractResourceVisitor}} is lacking the JSR 305 nullness
annotations.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
Re: [VOTE] Release Apache Sling i18n 2.5.8
+1 On Fri, Mar 3, 2017 at 4:29 AM, Timothee Maret wrote: > +1 (non binding) > > Regards, > > Timothee > > 2017-03-03 9:15 GMT+01:00 Oliver Lietz : > > > Hi, > > > > we solved 2 issues in this release: > > https://issues.apache.org/jira/browse/SLING/fixforversion/12338904 > > > > Staging repository: > > https://repository.apache.org/content/repositories/orgapachesling-1652/ > > > > You can use this UNIX script to download the release and verify the > > signatures: > > http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh > > > > Usage: > > sh check_staged_release.sh 1652 /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, > > O. > > > > >
Re: [VOTE] Release Apache Sling JCR Installer 3.1.24
+1 checked signature and build On Fri, Mar 3, 2017 at 4:26 AM, Timothee Maret wrote: > +1 (non binding) > > Regards, > > Timothee > > 2017-03-03 9:49 GMT+01:00 Oliver Lietz : > > > Hi, > > > > we solved 2 issues in this release: > > https://issues.apache.org/jira/browse/SLING/fixforversion/12338806 > > > > Staging repository: > > https://repository.apache.org/content/repositories/orgapachesling-1653/ > > > > You can use this UNIX script to download the release and verify the > > signatures: > > http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh > > > > Usage: > > sh check_staged_release.sh 1653 /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, > > O. > > > > >
[jira] [Resolved] (SLING-6600) Support multivalue validator argument values in ResourceValidationModelProviderImpl
[
https://issues.apache.org/jira/browse/SLING-6600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus resolved SLING-6600.
Resolution: Fixed
Fix Version/s: Validation 1.0.0
Fixed with [r1785330|http://svn.apache.org/r1785330] by using the above syntax
to pass multivalue arrays to the Validator.
> Support multivalue validator argument values in
> ResourceValidationModelProviderImpl
> ---
>
> Key: SLING-6600
> URL: https://issues.apache.org/jira/browse/SLING-6600
> Project: Sling
> Issue Type: Improvement
> Components: Validation
>Affects Versions: Validation 1.0.0
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
> Fix For: Validation 1.0.0
>
>
> Currently only singlevalue argument values are allowed for property
> {{validatorArguments}} in {{ResourceValidationModelProviderImpl}}. If you
> give the following multivalue string
> {code}{"key1=value1", "key1=value2"}{code} the second item will just
> overwrite the first one.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (SLING-4637) Provide Validation feature
[
https://issues.apache.org/jira/browse/SLING-4637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz updated SLING-4637:
Summary: Provide Validation feature (was: provide Validation feature)
> Provide Validation feature
> --
>
> Key: SLING-4637
> URL: https://issues.apache.org/jira/browse/SLING-4637
> Project: Sling
> Issue Type: New Feature
> Components: Karaf
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Karaf Features 0.2.0, Karaf Integration Tests 0.2.0
>
>
> {{sling-extension-validation}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
Re: [VOTE] Release Apache Sling Scripting HTL JavaScript Use Provider 1.0.20
+1 checked signatures and build On Fri, Mar 3, 2017 at 4:18 AM, Oliver Lietz wrote: > Hi, > > we solved 2 issues in this release: > https://issues.apache.org/jira/browse/SLING/fixforversion/12339542 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-1655/ > > You can use this UNIX script to download the release and verify the > signatures: > http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh > > Usage: > sh check_staged_release.sh 1655 /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, > O. > >
[jira] [Updated] (SLING-6601) Add Validation to Launchpad
[ https://issues.apache.org/jira/browse/SLING-6601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-6601: Issue Type: Sub-task (was: Task) Parent: SLING-6194 > Add Validation to Launchpad > --- > > Key: SLING-6601 > URL: https://issues.apache.org/jira/browse/SLING-6601 > Project: Sling > Issue Type: Sub-task > Components: Launchpad, Validation >Reporter: Oliver Lietz >Assignee: Oliver Lietz > Labels: Sling-9-ReleaseNotes > Fix For: Launchpad Builder 9 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SLING-6601) Add Validation to Launchpad
[ https://issues.apache.org/jira/browse/SLING-6601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-6601: Labels: Sling-9-ReleaseNotes (was: ) > Add Validation to Launchpad > --- > > Key: SLING-6601 > URL: https://issues.apache.org/jira/browse/SLING-6601 > Project: Sling > Issue Type: Task > Components: Launchpad, Validation >Reporter: Oliver Lietz >Assignee: Oliver Lietz > Labels: Sling-9-ReleaseNotes > Fix For: Launchpad Builder 9 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (SLING-6601) Add Validation to Launchpad
[ https://issues.apache.org/jira/browse/SLING-6601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz resolved SLING-6601. - Resolution: Done [r1785322|https://svn.apache.org/r1785322] > Add Validation to Launchpad > --- > > Key: SLING-6601 > URL: https://issues.apache.org/jira/browse/SLING-6601 > Project: Sling > Issue Type: Task > Components: Launchpad, Validation >Reporter: Oliver Lietz >Assignee: Oliver Lietz > Fix For: Launchpad Builder 9 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SLING-6601) Add Validation to Launchpad
[ https://issues.apache.org/jira/browse/SLING-6601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-6601: Component/s: Validation Launchpad > Add Validation to Launchpad > --- > > Key: SLING-6601 > URL: https://issues.apache.org/jira/browse/SLING-6601 > Project: Sling > Issue Type: Task > Components: Launchpad, Validation >Reporter: Oliver Lietz >Assignee: Oliver Lietz > Fix For: Launchpad Builder 9 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (SLING-6601) Add Validation to Launchpad
Oliver Lietz created SLING-6601: --- Summary: Add Validation to Launchpad Key: SLING-6601 URL: https://issues.apache.org/jira/browse/SLING-6601 Project: Sling Issue Type: Task Reporter: Oliver Lietz Assignee: Oliver Lietz Fix For: Launchpad Builder 9 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (SLING-6600) Support multivalue validator argument values in ResourceValidationModelProviderImpl
Konrad Windszus created SLING-6600:
--
Summary: Support multivalue validator argument values in
ResourceValidationModelProviderImpl
Key: SLING-6600
URL: https://issues.apache.org/jira/browse/SLING-6600
Project: Sling
Issue Type: Improvement
Components: Validation
Affects Versions: Validation 1.0.0
Reporter: Konrad Windszus
Assignee: Konrad Windszus
Currently only singlevalue argument values are allowed for property
{{validatorArguments}} in {{ResourceValidationModelProviderImpl}}. If you give
the following multivalue string
{code}{"key1=value1", "key1=value2"}{code} the second item will just overwrite
the first one.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[VOTE] Release Apache Sling Health Check Core 1.2.6
Hi, we solved 7 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12335062 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1657/ You can use this UNIX script to download the release and verify the signatures: http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh Usage: sh check_staged_release.sh 1657 /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, O.
[jira] [Closed] (SLING-5624) Health Check Core 1.2.4 fails on Karaf
[
https://issues.apache.org/jira/browse/SLING-5624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz closed SLING-5624.
---
> Health Check Core 1.2.4 fails on Karaf
> --
>
> Key: SLING-5624
> URL: https://issues.apache.org/jira/browse/SLING-5624
> Project: Sling
> Issue Type: Bug
> Components: Karaf
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Karaf Features 0.2.0
>
>
> {{SlingExtensionHealthcheckIT}} fails with
> {{org.apache.sling/org.apache.sling.hc.core/1.2.4}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (SLING-6596) Typo: "guage" instead of "gauge" in metrics module
[ https://issues.apache.org/jira/browse/SLING-6596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz resolved SLING-6596. Resolution: Fixed oops ;-) good catch, sorry! I have fixed the fixes in revision 1785309 > Typo: "guage" instead of "gauge" in metrics module > -- > > Key: SLING-6596 > URL: https://issues.apache.org/jira/browse/SLING-6596 > Project: Sling > Issue Type: Bug > Components: Commons >Affects Versions: Commons Metrics 1.2.0 >Reporter: Bertrand Delacretaz >Assignee: Bertrand Delacretaz >Priority: Minor > Fix For: Commons Metrics 1.2.2 > > > The JSON produced by the metrics module uses "guage" instead of "gauge" -- This message was sent by Atlassian JIRA (v6.3.15#6346)
Re: [VOTE] Release Apache Sling Installer Health Checks 1.0.0
+1 On Thu, Mar 2, 2017 at 7:46 AM, Timothee Maret wrote: > +1 (non binding) > > Regards, > > Timothee > > 2017-03-02 8:55 GMT+01:00 Oliver Lietz : > > > Hi, > > > > we solved 1 issue in this release: > > https://issues.apache.org/jira/browse/SLING/fixforversion/12338122 > > > > Staging repository: > > https://repository.apache.org/content/repositories/orgapachesling-1648/ > > > > You can use this UNIX script to download the release and verify the > > signatures: > > http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh > > > > Usage: > > sh check_staged_release.sh 1648 /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, > > O. > > > > >
[jira] [Comment Edited] (SLING-6580) Use observation for validation models
[ https://issues.apache.org/jira/browse/SLING-6580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894417#comment-15894417 ] Konrad Windszus edited comment on SLING-6580 at 3/3/17 2:07 PM: As soon as we upgrade Sling API to 2.11.0 we should at the same time use "try-with-resources" on the resource resolver (SLING-4805). was (Author: kwin): As soon as we upgrade Sling API to 2.11.0 we should at the same time use "try with resources" on the resource resolver (SLING-4805). > Use observation for validation models > - > > Key: SLING-6580 > URL: https://issues.apache.org/jira/browse/SLING-6580 > Project: Sling > Issue Type: Improvement > Components: Extensions, Validation >Reporter: Oliver Lietz > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SLING-6580) Use observation for validation models
[ https://issues.apache.org/jira/browse/SLING-6580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894417#comment-15894417 ] Konrad Windszus commented on SLING-6580: As soon as we upgrade Sling API to 2.11.0 we should at the same time use "try with resources" on the resource resolver (SLING-4805). > Use observation for validation models > - > > Key: SLING-6580 > URL: https://issues.apache.org/jira/browse/SLING-6580 > Project: Sling > Issue Type: Improvement > Components: Extensions, Validation >Reporter: Oliver Lietz > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (SLING-6596) Typo: "guage" instead of "gauge" in metrics module
[ https://issues.apache.org/jira/browse/SLING-6596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus reopened SLING-6596: > Typo: "guage" instead of "gauge" in metrics module > -- > > Key: SLING-6596 > URL: https://issues.apache.org/jira/browse/SLING-6596 > Project: Sling > Issue Type: Bug > Components: Commons >Affects Versions: Commons Metrics 1.2.0 >Reporter: Bertrand Delacretaz >Assignee: Bertrand Delacretaz >Priority: Minor > Fix For: Commons Metrics 1.2.2 > > > The JSON produced by the metrics module uses "guage" instead of "gauge" -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SLING-6596) Typo: "guage" instead of "gauge" in metrics module
[
https://issues.apache.org/jira/browse/SLING-6596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894400#comment-15894400
]
Konrad Windszus commented on SLING-6596:
[~bdelacretaz] Seems your search/replace command did some damage here:
https://github.com/apache/sling/commit/2c287b659a42272adc6b803bcf5a4c2efbdc12c5:
{{Language}} became {{Langauge}}.
> Typo: "guage" instead of "gauge" in metrics module
> --
>
> Key: SLING-6596
> URL: https://issues.apache.org/jira/browse/SLING-6596
> Project: Sling
> Issue Type: Bug
> Components: Commons
>Affects Versions: Commons Metrics 1.2.0
>Reporter: Bertrand Delacretaz
>Assignee: Bertrand Delacretaz
>Priority: Minor
> Fix For: Commons Metrics 1.2.2
>
>
> The JSON produced by the metrics module uses "guage" instead of "gauge"
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (SLING-6599) Improve logging in HealthCheckMBeanCreator
[ https://issues.apache.org/jira/browse/SLING-6599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz resolved SLING-6599. - Resolution: Done [r1785285|https://svn.apache.org/r1785285] > Improve logging in HealthCheckMBeanCreator > -- > > Key: SLING-6599 > URL: https://issues.apache.org/jira/browse/SLING-6599 > Project: Sling > Issue Type: Improvement > Components: Extensions, Health Check >Reporter: Oliver Lietz >Assignee: Oliver Lietz >Priority: Minor > Fix For: Health Check Core 1.2.6 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
Re: Remove usage of commons legacy releases
On Friday 03 March 2017 14:07:28 Konrad Windszus wrote: > Currently org.apache.sling.testing.paxexam.SlingOptions only includes > "commons-collections" but not "commons-collections4". @Oliver Lietz: Could > you look into that? Sure. Releasing right now several bundles to get rid of snaphots in Karaf Features and therefore Testing PaxExam (but adding extra bundles is easy). Regards, O. > Thanks, > Konrad > > > On 27 Feb 2017, at 11:24, Carsten Ziegeler wrote: > > > > While in general we should use the lowest version possible of a > > dependency (in order to make updating installations easier), I think > > it's time now to get rid of using commons legacy releases. > > Especially as for most of them we have dependencies to the legacy and > > the latest version, which means we have to include to copies of that > > library. > > > > In particular I'm speaking about commons lang, commons collections, > > commons math and the httpclient. For all of them, except math, we > > currently have to include two versions in launchpad: > > commons-collections/commons-collections/3.2.2 > > org.apache.commons/commons-collections4/4.1 > > > > commons-lang/commons-lang/2.6 > > org.apache.commons/commons-lang3/3.4 > > > > org.apache.geronimo.bundles/commons-httpclient/3.1_1 > > org.apache.httpcomponents/httpcore-osgi/4.4.1 > > org.apache.httpcomponents/httpclient-osgi/4.4.1 > > > > For commons math, we are using > > org.apache.commons/commons-math/2.2 > > and probably should replace this with a 3.x version. > > > > WDYT > > > > Regards > > Carsten
Re: [VOTE] Release Apache Sling Parent 30
+1 On Thu, Mar 2, 2017 at 12:58 PM, Stefan Seifert wrote: > +1 > > >
Re: [VOTE] Release Apache Sling Resource Resolver 1.5.18
+1 checked signatures and build On Thu, Mar 2, 2017 at 5:22 PM, Karl Pauls wrote: > +1 > > regards, > > Karl > > On Thu, Mar 2, 2017 at 10:50 PM, Stefan Seifert > wrote: > > +1 > > > > -- > Karl Pauls > karlpa...@gmail.com >
[jira] [Updated] (SLING-4777) Decouple the model provider from the actual validation service
[ https://issues.apache.org/jira/browse/SLING-4777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-4777: --- Component/s: Validation > Decouple the model provider from the actual validation service > -- > > Key: SLING-4777 > URL: https://issues.apache.org/jira/browse/SLING-4777 > Project: Sling > Issue Type: Improvement > Components: Validation >Reporter: Konrad Windszus >Assignee: Konrad Windszus > Fix For: Validation 1.0.0 > > > As being mentioned in SLING-4027, it would be good to completely decouple the > model providing capabilities from the actual validation, as that would > a) make the codebase cleaner (and would ease testing) > b) allow to plug-in other services which provide models (e.g. based on > annotations on some files) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (SLING-5660) Validation is using outdated sling/validation/model
[
https://issues.apache.org/jira/browse/SLING-5660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus resolved SLING-5660.
Resolution: Fixed
> Validation is using outdated sling/validation/model
> ---
>
> Key: SLING-5660
> URL: https://issues.apache.org/jira/browse/SLING-5660
> Project: Sling
> Issue Type: Bug
> Components: Extensions
>Reporter: Oliver Lietz
>Assignee: Konrad Windszus
> Fix For: Validation 1.0.0
>
>
> The new {{sling/validation/model}} (one property removed) was used only after
> restarting Validation bundles:
> {{sling.validator.missing-required-property-with-name}}, {{location}} was
> empty.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (SLING-5660) Validation is using outdated sling/validation/model
[
https://issues.apache.org/jira/browse/SLING-5660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894318#comment-15894318
]
Konrad Windszus commented on SLING-5660:
With the new caching solution from SLING-6588 I assume this should be fixed
now. If not, please reopen.
> Validation is using outdated sling/validation/model
> ---
>
> Key: SLING-5660
> URL: https://issues.apache.org/jira/browse/SLING-5660
> Project: Sling
> Issue Type: Bug
> Components: Extensions
>Reporter: Oliver Lietz
>Assignee: Konrad Windszus
> Fix For: Validation 1.0.0
>
>
> The new {{sling/validation/model}} (one property removed) was used only after
> restarting Validation bundles:
> {{sling.validator.missing-required-property-with-name}}, {{location}} was
> empty.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (SLING-6581) Use Trie from Commons Collections
[ https://issues.apache.org/jira/browse/SLING-6581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-6581: --- Fix Version/s: Validation 1.0.0 > Use Trie from Commons Collections > - > > Key: SLING-6581 > URL: https://issues.apache.org/jira/browse/SLING-6581 > Project: Sling > Issue Type: Improvement > Components: Extensions, Validation >Reporter: Oliver Lietz >Assignee: Konrad Windszus > Fix For: Validation 1.0.0 > > > replace Trie by implementation from Commons Collections -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (SLING-6581) Use Trie from Commons Collections
[ https://issues.apache.org/jira/browse/SLING-6581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved SLING-6581. Resolution: Fixed Fixed in [r1785290|http://svn.apache.org/r1785290]. > Use Trie from Commons Collections > - > > Key: SLING-6581 > URL: https://issues.apache.org/jira/browse/SLING-6581 > Project: Sling > Issue Type: Improvement > Components: Extensions, Validation >Reporter: Oliver Lietz >Assignee: Konrad Windszus > > replace Trie by implementation from Commons Collections -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SLING-6440) Filesystem Resource Provider: Support "mounting" content resources from JSON files
[ https://issues.apache.org/jira/browse/SLING-6440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert updated SLING-6440: -- Fix Version/s: File System Resource Provider 2.0.0 > Filesystem Resource Provider: Support "mounting" content resources from JSON > files > -- > > Key: SLING-6440 > URL: https://issues.apache.org/jira/browse/SLING-6440 > Project: Sling > Issue Type: New Feature > Components: Extensions >Reporter: Stefan Seifert >Assignee: Stefan Seifert > Fix For: File System Resource Provider 1.3.0, File System > Resource Provider 2.0.0 > > > it would be nice if the filesystem resource provider does not only support > serving binary files and folders, but also arbitrary resources stored in > .json files in the folder hierarchy which are normally extracted when > installing the bundle with sling-initial-content. > is is necessary to explicitly switch this feature on per configuration, > because it may be desired to directly serve the JSON files as binary files in > some cases. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (SLING-6581) Use Trie from Commons Collections
[ https://issues.apache.org/jira/browse/SLING-6581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus reassigned SLING-6581: -- Assignee: Konrad Windszus > Use Trie from Commons Collections > - > > Key: SLING-6581 > URL: https://issues.apache.org/jira/browse/SLING-6581 > Project: Sling > Issue Type: Improvement > Components: Extensions, Validation >Reporter: Oliver Lietz >Assignee: Konrad Windszus > > replace Trie by implementation from Commons Collections -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SLING-6526) Switch back to Sling API 2.11.0
[ https://issues.apache.org/jira/browse/SLING-6526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert updated SLING-6526: -- Fix Version/s: (was: File System Resource Provider 1.3.0) File System Resource Provider 2.0.0 > Switch back to Sling API 2.11.0 > --- > > Key: SLING-6526 > URL: https://issues.apache.org/jira/browse/SLING-6526 > Project: Sling > Issue Type: Improvement > Components: Extensions >Affects Versions: File System Resource Provider 1.2.2 >Reporter: Stefan Seifert >Assignee: Stefan Seifert > Fix For: File System Resource Provider 2.0.0 > > > Switch back from Sling API 2.15.0 to 2.11.0 to support older sling > environments as well. it's still based on the new resource provider SPI. > we also should add unit test coverage. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SLING-6537) Filesystem Resource Provider: Support "mounting" content resources from FileVault JCR XML files
[ https://issues.apache.org/jira/browse/SLING-6537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert updated SLING-6537: -- Fix Version/s: File System Resource Provider 2.0.0 > Filesystem Resource Provider: Support "mounting" content resources from > FileVault JCR XML files > --- > > Key: SLING-6537 > URL: https://issues.apache.org/jira/browse/SLING-6537 > Project: Sling > Issue Type: New Feature > Components: Extensions >Reporter: Stefan Seifert >Assignee: Stefan Seifert > Fix For: File System Resource Provider 1.3.0, File System > Resource Provider 2.0.0 > > > it would be nice if the filesystem resource provider does not only support > serving binary files and folders, but also arbitrary resources stored in > FileVault JCR XML files in the folder hierarchy which are normally packaged > and uploaded. > is is necessary to explicitly switch this feature on per configuration, > because it may be desired to directly serve the JSON and XML files as binary > files in some cases. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
Re: Remove usage of commons legacy releases
Currently org.apache.sling.testing.paxexam.SlingOptions only includes "commons-collections" but not "commons-collections4". @Oliver Lietz: Could you look into that? Thanks, Konrad > On 27 Feb 2017, at 11:24, Carsten Ziegeler wrote: > > While in general we should use the lowest version possible of a > dependency (in order to make updating installations easier), I think > it's time now to get rid of using commons legacy releases. > Especially as for most of them we have dependencies to the legacy and > the latest version, which means we have to include to copies of that > library. > > In particular I'm speaking about commons lang, commons collections, > commons math and the httpclient. For all of them, except math, we > currently have to include two versions in launchpad: > commons-collections/commons-collections/3.2.2 > org.apache.commons/commons-collections4/4.1 > > commons-lang/commons-lang/2.6 > org.apache.commons/commons-lang3/3.4 > > org.apache.geronimo.bundles/commons-httpclient/3.1_1 > org.apache.httpcomponents/httpcore-osgi/4.4.1 > org.apache.httpcomponents/httpclient-osgi/4.4.1 > > For commons math, we are using > org.apache.commons/commons-math/2.2 > and probably should replace this with a 3.x version. > > WDYT > > Regards > Carsten > -- > Carsten Ziegeler > Adobe Research Switzerland > cziege...@apache.org
[jira] [Created] (SLING-6599) Improve logging in HealthCheckMBeanCreator
Oliver Lietz created SLING-6599: --- Summary: Improve logging in HealthCheckMBeanCreator Key: SLING-6599 URL: https://issues.apache.org/jira/browse/SLING-6599 Project: Sling Issue Type: Improvement Components: Extensions, Health Check Reporter: Oliver Lietz Assignee: Oliver Lietz Priority: Minor Fix For: Health Check Core 1.2.6 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SLING-6287) support maxparallel for main job queue to be -1 or between 0.0 and 1.0
[
https://issues.apache.org/jira/browse/SLING-6287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894133#comment-15894133
]
Oliver Lietz commented on SLING-6287:
-
[~cziegeler], can this change go into 4.2.2 or should it be deferred?
> support maxparallel for main job queue to be -1 or between 0.0 and 1.0
> --
>
> Key: SLING-6287
> URL: https://issues.apache.org/jira/browse/SLING-6287
> Project: Sling
> Issue Type: Improvement
> Components: Event
>Affects Versions: Event 4.2.0
>Reporter: Stefan Egli
>Priority: Minor
> Fix For: Event-4.2.2
>
> Attachments: SLING-6287.patch
>
>
> [Currently|https://github.com/apache/sling/blob/4eeb4593d6d9d43091ed1c5796746493724bfece/bundles/extensions/event/src/main/java/org/apache/sling/event/impl/jobs/config/MainQueueConfiguration.java#L104]
> the main job queue converts doubles as {{maxparallel}} into the default
> (15), as well as it converts ints < 2 into 2. This is unlike other queues,
> which allow to set values to -1 or between 0.0 and 1.0 as maxparallel.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[VOTE] Release Apache Sling Scripting Core 2.0.46
Hi, we solved 3 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12339253 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1656/ You can use this UNIX script to download the release and verify the signatures: http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh Usage: sh check_staged_release.sh 1656 /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, O.
[jira] [Resolved] (SLING-6598) Models Validation: Expose english validation message in exception
[
https://issues.apache.org/jira/browse/SLING-6598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus resolved SLING-6598.
Resolution: Fixed
Fix Version/s: Sling Models Validation Impl 1.0.0
Fixed in [r1785260|http://svn.apache.org/r1785260].
> Models Validation: Expose english validation message in exception
> -
>
> Key: SLING-6598
> URL: https://issues.apache.org/jira/browse/SLING-6598
> Project: Sling
> Issue Type: Improvement
> Components: Extensions, Validation
>Affects Versions: Sling Models Validation Impl 1.0.0
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Minor
> Fix For: Sling Models Validation Impl 1.0.0
>
>
> Although with SLING-4213 the validation error messages rely now on Sling i18n
> Resource Bundles to return the actual error message, it should still be
> possible to get the default (=English) validation error in the
> {{InvalidResourceException}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (SLING-6598) Models Validation: Expose english validation message in exception
Konrad Windszus created SLING-6598:
--
Summary: Models Validation: Expose english validation message in
exception
Key: SLING-6598
URL: https://issues.apache.org/jira/browse/SLING-6598
Project: Sling
Issue Type: Improvement
Components: Extensions, Validation
Affects Versions: Sling Models Validation Impl 1.0.0
Reporter: Konrad Windszus
Assignee: Konrad Windszus
Priority: Minor
Although with SLING-4213 the validation error messages rely now on Sling i18n
Resource Bundles to return the actual error message, it should still be
possible to get the default (=English) validation error in the
{{InvalidResourceException}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (SLING-6597) Use ServiceUserMapped to ensure presence of service user mapping
[ https://issues.apache.org/jira/browse/SLING-6597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz resolved SLING-6597. - Resolution: Done [r1785253|https://svn.apache.org/r1785253] > Use ServiceUserMapped to ensure presence of service user mapping > > > Key: SLING-6597 > URL: https://issues.apache.org/jira/browse/SLING-6597 > Project: Sling > Issue Type: Improvement > Components: Scripting >Reporter: Oliver Lietz >Assignee: Oliver Lietz > Fix For: Scripting Core 2.0.46 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
Re: Staging repository 1654 – Re: [VOTE] Release Apache Sling XSS 1.0.18
+1 (not binding) Regards, Timothee 2017-03-03 10:34 GMT+01:00 Oliver Lietz : > On Friday 03 March 2017 10:24:31 Timothee Maret wrote: > > Hi Oliver, > > Hi Timothee, > > > It seems the staged repository 1653 does not contain Apache Sling XSS > > bundle, but org.apache.sling.installer.provider.jcr instead. Maybe it > was > > mixed up with other ongoing votes. > > yes, XSS is in 1654. > > Thanks, > O. > > > Regards, > > > > Timothee > > > > 2017-03-03 10:02 GMT+01:00 Oliver Lietz : > > > Hi, > > > > > > we solved 2 issues in this release: > > > https://issues.apache.org/jira/browse/SLING/fixforversion/12339543 > > > > > > Staging repository: > > > https://repository.apache.org/content/repositories/ > orgapachesling-1653/ > > > > > > You can use this UNIX script to download the release and verify the > > > signatures: > > > http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh > > > > > > Usage: > > > sh check_staged_release.sh 1653 /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, > > > O. > >
[jira] [Created] (SLING-6597) Use ServiceUserMapped to ensure presence of service user mapping
Oliver Lietz created SLING-6597: --- Summary: Use ServiceUserMapped to ensure presence of service user mapping Key: SLING-6597 URL: https://issues.apache.org/jira/browse/SLING-6597 Project: Sling Issue Type: Improvement Components: Scripting Reporter: Oliver Lietz Assignee: Oliver Lietz Fix For: Scripting Core 2.0.46 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
Staging repository 1654 – Re: [VOTE] Release Apache Sling XSS 1.0.18
On Friday 03 March 2017 10:24:31 Timothee Maret wrote: > Hi Oliver, Hi Timothee, > It seems the staged repository 1653 does not contain Apache Sling XSS > bundle, but org.apache.sling.installer.provider.jcr instead. Maybe it was > mixed up with other ongoing votes. yes, XSS is in 1654. Thanks, O. > Regards, > > Timothee > > 2017-03-03 10:02 GMT+01:00 Oliver Lietz : > > Hi, > > > > we solved 2 issues in this release: > > https://issues.apache.org/jira/browse/SLING/fixforversion/12339543 > > > > Staging repository: > > https://repository.apache.org/content/repositories/orgapachesling-1653/ > > > > You can use this UNIX script to download the release and verify the > > signatures: > > http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh > > > > Usage: > > sh check_staged_release.sh 1653 /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, > > O.
Re: [VOTE] Release Apache Sling i18n 2.5.8
+1 (non binding) Regards, Timothee 2017-03-03 9:15 GMT+01:00 Oliver Lietz : > Hi, > > we solved 2 issues in this release: > https://issues.apache.org/jira/browse/SLING/fixforversion/12338904 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-1652/ > > You can use this UNIX script to download the release and verify the > signatures: > http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh > > Usage: > sh check_staged_release.sh 1652 /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, > O. > >
Re: [VOTE] Release Apache Sling JCR Installer 3.1.24
+1 (non binding) Regards, Timothee 2017-03-03 9:49 GMT+01:00 Oliver Lietz : > Hi, > > we solved 2 issues in this release: > https://issues.apache.org/jira/browse/SLING/fixforversion/12338806 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-1653/ > > You can use this UNIX script to download the release and verify the > signatures: > http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh > > Usage: > sh check_staged_release.sh 1653 /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, > O. > >
Re: [VOTE] Release Apache Sling XSS 1.0.18
Hi Oliver, It seems the staged repository 1653 does not contain Apache Sling XSS bundle, but org.apache.sling.installer.provider.jcr instead. Maybe it was mixed up with other ongoing votes. Regards, Timothee 2017-03-03 10:02 GMT+01:00 Oliver Lietz : > Hi, > > we solved 2 issues in this release: > https://issues.apache.org/jira/browse/SLING/fixforversion/12339543 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-1653/ > > You can use this UNIX script to download the release and verify the > signatures: > http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh > > Usage: > sh check_staged_release.sh 1653 /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, > O. > >
[VOTE] Release Apache Sling Scripting HTL JavaScript Use Provider 1.0.20
Hi, we solved 2 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12339542 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1655/ You can use this UNIX script to download the release and verify the signatures: http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh Usage: sh check_staged_release.sh 1655 /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, O.
[VOTE] Release Apache Sling XSS 1.0.18
Hi, we solved 2 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12339543 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1653/ You can use this UNIX script to download the release and verify the signatures: http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh Usage: sh check_staged_release.sh 1653 /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, O.
[VOTE] Release Apache Sling JCR Installer 3.1.24
Hi, we solved 2 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12338806 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1653/ You can use this UNIX script to download the release and verify the signatures: http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh Usage: sh check_staged_release.sh 1653 /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, O.
[jira] [Resolved] (SLING-6596) Typo: "guage" instead of "gauge" in metrics module
[ https://issues.apache.org/jira/browse/SLING-6596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz resolved SLING-6596. Resolution: Fixed Fixed in revision 1785238 > Typo: "guage" instead of "gauge" in metrics module > -- > > Key: SLING-6596 > URL: https://issues.apache.org/jira/browse/SLING-6596 > Project: Sling > Issue Type: Bug > Components: Commons >Affects Versions: Commons Metrics 1.2.0 >Reporter: Bertrand Delacretaz >Assignee: Bertrand Delacretaz >Priority: Minor > Fix For: Commons Metrics 1.2.2 > > > The JSON produced by the metrics module uses "guage" instead of "gauge" -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (SLING-6596) Typo: "guage" instead of "gauge" in metrics module
Bertrand Delacretaz created SLING-6596: -- Summary: Typo: "guage" instead of "gauge" in metrics module Key: SLING-6596 URL: https://issues.apache.org/jira/browse/SLING-6596 Project: Sling Issue Type: Bug Components: Commons Affects Versions: Commons Metrics 1.2.0 Reporter: Bertrand Delacretaz Assignee: Bertrand Delacretaz Priority: Minor Fix For: Commons Metrics 1.2.2 The JSON produced by the metrics module uses "guage" instead of "gauge" -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SLING-6581) Use Trie from Commons Collections
[
https://issues.apache.org/jira/browse/SLING-6581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15893920#comment-15893920
]
Oliver Lietz commented on SLING-6581:
-
[~kwin], as you are working on caching anyway, can you check if we can replace
{{org.apache.sling.validation.impl.util.Trie}} by one from Commons Collections?
> Use Trie from Commons Collections
> -
>
> Key: SLING-6581
> URL: https://issues.apache.org/jira/browse/SLING-6581
> Project: Sling
> Issue Type: Improvement
> Components: Extensions, Validation
>Reporter: Oliver Lietz
>
> replace Trie by implementation from Commons Collections
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (SLING-6569) NPE in DefaultValidationFailure when resource bundle is null
[
https://issues.apache.org/jira/browse/SLING-6569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15893913#comment-15893913
]
Konrad Windszus commented on SLING-6569:
I now really made the {{ResourceBundle}} parameter optional in
[r1785229|http://svn.apache.org/r1785229]. In case {{null}} is provided the
default resource bundle will be used which is given in the constructor to
{{DefaultValidationFailure}} and can be retrieved in every {{Validator}} via
{{ValidationContext.getDefaultResourceBundle()}}.
> NPE in DefaultValidationFailure when resource bundle is null
>
>
> Key: SLING-6569
> URL: https://issues.apache.org/jira/browse/SLING-6569
> Project: Sling
> Issue Type: Bug
> Components: Extensions, Validation
>Reporter: Oliver Lietz
>Assignee: Konrad Windszus
> Fix For: Validation 1.0.0
>
>
> Before:
> {noformat}
> [...]
> 2017-03-02 15:39:42,933 ERROR [127.0.0.1 [1488465582809] POST
> /validation/testing/fakeFolder1/resource HTTP/1.1]
> o.a.s.e.i.SlingRequestProcessorImpl [SlingRequestProcessorImpl.java : 225]
> service: Uncaught Throwable
> java.lang.NullPointerException: null
> at
> org.apache.sling.validation.spi.DefaultValidationFailure.getMessage(DefaultValidationFailure.java:64)
> at
> org.apache.sling.validation.testservices.internal.ValidationPostResponse.doSend(ValidationPostResponse.java:63)
> at
> org.apache.sling.servlets.post.AbstractPostResponse.send(AbstractPostResponse.java:387)
> at
> org.apache.sling.servlets.post.impl.SlingPostServlet.doPost(SlingPostServlet.java:226)
> [...]
> {noformat}
> After:
> {noformat}
> [...]
> 2017-03-02 15:46:33,866 ERROR [127.0.0.1 [1488465993738] POST
> /validation/testing/fakeFolder1/resource HTTP/1.1]
> o.a.s.e.i.SlingRequestProcessorImpl [SlingRequestProcessorImpl.java : 225]
> service: Uncaught Throwable
> java.lang.NullPointerException: ResourceBundle must not be null
> at
> org.apache.sling.validation.spi.DefaultValidationFailure.getMessage(DefaultValidationFailure.java:65)
> at
> org.apache.sling.validation.testservices.internal.ValidationPostResponse.doSend(ValidationPostResponse.java:63)
> at
> org.apache.sling.servlets.post.AbstractPostResponse.send(AbstractPostResponse.java:387)
> at
> org.apache.sling.servlets.post.impl.SlingPostServlet.doPost(SlingPostServlet.java:226)
> [...]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (SLING-6569) NPE in DefaultValidationFailure when resource bundle is null
[
https://issues.apache.org/jira/browse/SLING-6569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus reassigned SLING-6569:
--
Assignee: Konrad Windszus (was: Oliver Lietz)
> NPE in DefaultValidationFailure when resource bundle is null
>
>
> Key: SLING-6569
> URL: https://issues.apache.org/jira/browse/SLING-6569
> Project: Sling
> Issue Type: Bug
> Components: Extensions, Validation
>Reporter: Oliver Lietz
>Assignee: Konrad Windszus
> Fix For: Validation 1.0.0
>
>
> Before:
> {noformat}
> [...]
> 2017-03-02 15:39:42,933 ERROR [127.0.0.1 [1488465582809] POST
> /validation/testing/fakeFolder1/resource HTTP/1.1]
> o.a.s.e.i.SlingRequestProcessorImpl [SlingRequestProcessorImpl.java : 225]
> service: Uncaught Throwable
> java.lang.NullPointerException: null
> at
> org.apache.sling.validation.spi.DefaultValidationFailure.getMessage(DefaultValidationFailure.java:64)
> at
> org.apache.sling.validation.testservices.internal.ValidationPostResponse.doSend(ValidationPostResponse.java:63)
> at
> org.apache.sling.servlets.post.AbstractPostResponse.send(AbstractPostResponse.java:387)
> at
> org.apache.sling.servlets.post.impl.SlingPostServlet.doPost(SlingPostServlet.java:226)
> [...]
> {noformat}
> After:
> {noformat}
> [...]
> 2017-03-02 15:46:33,866 ERROR [127.0.0.1 [1488465993738] POST
> /validation/testing/fakeFolder1/resource HTTP/1.1]
> o.a.s.e.i.SlingRequestProcessorImpl [SlingRequestProcessorImpl.java : 225]
> service: Uncaught Throwable
> java.lang.NullPointerException: ResourceBundle must not be null
> at
> org.apache.sling.validation.spi.DefaultValidationFailure.getMessage(DefaultValidationFailure.java:65)
> at
> org.apache.sling.validation.testservices.internal.ValidationPostResponse.doSend(ValidationPostResponse.java:63)
> at
> org.apache.sling.servlets.post.AbstractPostResponse.send(AbstractPostResponse.java:387)
> at
> org.apache.sling.servlets.post.impl.SlingPostServlet.doPost(SlingPostServlet.java:226)
> [...]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[VOTE] Release Apache Sling i18n 2.5.8
Hi, we solved 2 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12338904 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1652/ You can use this UNIX script to download the release and verify the signatures: http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh Usage: sh check_staged_release.sh 1652 /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, O.
