This is an automated email from the ASF dual-hosted git repository.

remm pushed a commit to branch 9.0.x
in repository https://gitbox.apache.org/repos/asf/tomcat.git


The following commit(s) were added to refs/heads/9.0.x by this push:
     new e9a7b3c6d1 Add warnings and details about webapp classes
e9a7b3c6d1 is described below

commit e9a7b3c6d1e576efec11c5ce75c3cb6f00151354
Author: remm <r...@apache.org>
AuthorDate: Thu Dec 21 11:45:10 2023 +0100

    Add warnings and details about webapp classes
    
    They need to be packaged as well, and they also might be needed during
    compilation.
---
 webapps/docs/graal.xml | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/webapps/docs/graal.xml b/webapps/docs/graal.xml
index e2a631a513..95a793e36b 100644
--- a/webapps/docs/graal.xml
+++ b/webapps/docs/graal.xml
@@ -78,6 +78,18 @@
     folder.
   </p>
 
+  <p>
+    All the webapp classes need to be made available to the Maven shade plugin
+    as well as the compiler during the JSP precompilation step.
+    Any JARs that are present in <code>/WEB-INF/lib</code>
+    need to be made available as Maven dependencies.
+    The <code>webapp-jspc.ant.xml</code> script will copy classes from the
+    <code>/WEB-INF/classes</code> folder of the webapp
+    to the <code>target/classes</code> path that Maven uses as the compilation
+    target, but if any of the JSP sources use them, then they need to be
+    packaged as JARs instead. 
+  </p>
+
   <p>
     The first step is to build the shaded Tomcat JAR with all dependencies.
     Any JSP in the webapp must all be precompiled and packaged (assuming


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Reply via email to