This is an automated email from the ASF dual-hosted git repository. robertlazarski pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/axis-axis2-java-rampart.git
commit 353ec6ebc963ad3a4890bae6e468f05a5065abf1 Author: Robert Lazarski <[email protected]> AuthorDate: Mon Apr 13 05:28:26 2026 -1000 RAMPART-454 Put servlet-api on the aggregator Javadoc classpath mvn package (and mvn site / site-deploy) was failing in the apidocs module with: error: package jakarta.servlet.http does not exist import jakarta.servlet.http.HttpServletRequest; because rampart-core references HttpServletRequest (RampartUtil.java) and declares jakarta.servlet-api with <scope>provided</scope>. Provided scope is not transitive, so when apidocs aggregates rampart-core's sources for Javadoc, the servlet API is absent from the Javadoc classpath. Declare jakarta.servlet-api explicitly in apidocs/pom.xml so javadoc-no-fork (invoked at prepare-package for dist-javadoc and at site for site-javadoc) can resolve the import. --- apidocs/pom.xml | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/apidocs/pom.xml b/apidocs/pom.xml index 444227c2..6dd9ea8f 100644 --- a/apidocs/pom.xml +++ b/apidocs/pom.xml @@ -50,6 +50,14 @@ <artifactId>rampart-trust</artifactId> <version>${project.version}</version> </dependency> + <!-- rampart-core references jakarta.servlet.http.HttpServletRequest. + The servlet API is declared 'provided' in rampart-core so it is + not transitively visible; make it available on the Javadoc + classpath explicitly. --> + <dependency> + <groupId>jakarta.servlet</groupId> + <artifactId>jakarta.servlet-api</artifactId> + </dependency> </dependencies> <build> <plugins>
