[prev in list] [next in list] [prev in thread] [next in thread] 

List:       fop-dev
Subject:    [jira] [Resolved] (FOP-2935) servlet-api dependency scope
From:       "Simon Steiner (Jira)" <jira () apache ! org>
Date:       2020-05-22 13:20:00
Message-ID: JIRA.13303130.1588775640000.92116.1590153600274 () Atlassian ! JIRA
[Download RAW message or body]


     [ https://issues.apache.org/jira/browse/FOP-2935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

Simon Steiner resolved FOP-2935.
--------------------------------
    Resolution: Fixed

http://svn.apache.org/viewvc?view=revision&revision=1878031

> 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
> 
> 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)


[prev in list] [next in list] [prev in thread] [next in thread]