You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Radu Cotescu (Jira)" <ji...@apache.org> on 2020/02/05 13:59:00 UTC
[jira] [Resolved] (SLING-9048) The HTL engine does not specify the
correct io.sightly.runtime requirement version range
[ https://issues.apache.org/jira/browse/SLING-9048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Radu Cotescu resolved SLING-9048.
---------------------------------
Resolution: Fixed
Fixed in [commit a584639|https://github.com/apache/sling-org-apache-sling-scripting-sightly/commit/a584639].
> The HTL engine does not specify the correct io.sightly.runtime requirement version range
> ----------------------------------------------------------------------------------------
>
> Key: SLING-9048
> URL: https://issues.apache.org/jira/browse/SLING-9048
> Project: Sling
> Issue Type: Bug
> Components: Scripting
> Affects Versions: Scripting HTL Engine 1.2.0-1.4.0
> Reporter: Radu Cotescu
> Assignee: Radu Cotescu
> Priority: Minor
> Fix For: Scripting HTL Engine 1.3.4-1.4.0
>
>
> When SLING-8471 was implemented, the transition from the {{maven-bundle-plugin}} to the {{bnd-maven-plugin}} introduced the error of defining the {{io.sightly.runtime}} requirement as:
> {code:java}
> Require-Capability: io.sightly.runtime; filter:="(&(version<=1.0)(!(version>=2.0)))"
> {code}
> instead of:
> {code:java}
> Require-Capability: io.sightly.runtime; filter:="(&(version>=1.0)(!(version>=2.0)))"
> {code}
> While in practice this doesn't affect a regular Sling setup, it should be corrected.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)