[
https://issues.apache.org/jira/browse/FOP-2935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17239569#comment-17239569
]
Andreas 'PAX' Lück commented on FOP-2935:
-----------------------------------------
[~edigonzales] and [~ssteiner], did that really fix the issue? The old scope
was "default" and the new scope is an explicit "compile". But the default scope
is already "compile". So, in fact, this changed nothing?
[https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#dependency-scope|Dependency
Scope]
> servlet-api dependency scope
> ----------------------------
>
> Key: FOP-2935
> URL: https://issues.apache.org/jira/browse/FOP-2935
> Project: FOP
> Issue Type: Bug
> Affects Versions: 2.4
> Reporter: Stefan Ziegler
> Assignee: Simon Steiner
> Priority: Major
> Fix For: trunk
>
>
> I had troubles with the Apache FOP's servlet-api:2.2 dependency in a Spring
> Boot application. The "javax.servlet.ServletContext" class is available in
> Spring Boot's Tomcat dependency and in FOP's servlet-api dependency. If Java
> picks up the the class from servlet-api it's too old. Tomcat refuses to start.
> Can the scope of the servlet-api be changed in FOP's pom.xml?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
