[
https://issues.apache.org/jira/browse/SLING-9886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17228737#comment-17228737
]
Konrad Windszus edited comment on SLING-9886 at 11/9/20, 5:44 PM:
------------------------------------------------------------------
Unfortunately there is no newer release of beanshell than 2.0b6 (which probably
still suffers from this bug):
https://github.com/beanshell/beanshell#notice-pending-new-release. This means
one has to live with the bug and the verify scripts need to be rewritten in BSH
or (probably easier) have to be migrated to groovy scripts.
was (Author: kwin):
Unfortunately there is no newer release of beanshell than 2.0b6 (which probably
still suffers from this bug):
https://github.com/beanshell/beanshell#notice-pending-new-release. This means
one has to live with the bug and the verify scripts need to be rewritten!
> Slingfeature-maven-plugin: ITs always succeed
> ---------------------------------------------
>
> Key: SLING-9886
> URL: https://issues.apache.org/jira/browse/SLING-9886
> Project: Sling
> Issue Type: Bug
> Components: Feature Model
> Affects Versions: slingfeature-maven-plugin 1.4.6
> Reporter: Konrad Windszus
> Priority: Major
> Fix For: slingfeature-maven-plugin 1.4.8
>
>
> Due to the way how the {{verify.bsh}} are written with a return statement
> after try and catch the following bug is triggered in BSH:
> https://github.com/beanshell/beanshell/issues/367.
> You can reproduce by just inverting a condition, e.g. in
> https://github.com/apache/sling-slingfeature-maven-plugin/blob/56caf46d529f7f09e86e0a644357e17d00028263/src/it/apis-jar-wrapper-bundle/verify.bsh#L30
> and you see that the build will still not fail.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
