You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Dan Klco (JIRA)" <ji...@apache.org> on 2014/06/27 02:08:24 UTC

[jira] [Commented] (SLING-3512) All dependencies referenced from TEI classes should have "compile" scope

    [ https://issues.apache.org/jira/browse/SLING-3512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14045358#comment-14045358 ] 

Dan Klco commented on SLING-3512:
---------------------------------

Justin & Konrad, is this issue ready to be resolved?

> All dependencies referenced from TEI classes should have "compile" scope
> ------------------------------------------------------------------------
>
>                 Key: SLING-3512
>                 URL: https://issues.apache.org/jira/browse/SLING-3512
>             Project: Sling
>          Issue Type: Bug
>          Components: Scripting
>    Affects Versions: Scripting JSP-Taglib 2.2.0
>            Reporter: Konrad Windszus
>            Assignee: Justin Edelson
>             Fix For: Scripting JSP-Taglib 2.2.2
>
>
> Currently some classes which are referenced from TEI classes (e.g. DefineObjectsTEI) cannot be resolved within an IDE, because the according dependency is given with scope "provided". Since provided dependencies are not evaluated if given in a transitive way [0], the classpath of the referencing JSP does not necessarily contain those transitive dependencies, but they are necessary for the TEI to be instanciated within the IDE.
> For example the DefineObjectsTEI references classes from org.apache.sling.api and slf4j-api. Therefore both dependencies should have the "compile" scope.
> [0] - http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope



--
This message was sent by Atlassian JIRA
(v6.2#6252)