项目部署：服务器依赖路径创建与WAR包部署优化需求咨询

Hey there! Let's break down your two questions step by step—they're tied together perfectly when it comes to speeding up your WAR deployment.

1. How to create a dependency path on your server #

First, you'll want to set up a dedicated, organized directory for your dependencies so your WAR project can reliably access them. Here's how to do it right:

• Plan and create your base directory structure
  Log into your server and use mkdir to build a clean path. I recommend grouping dependencies by project to avoid confusion. For example:

  # Create a nested directory for your WAR project's dependencies
  sudo mkdir -p /opt/app-dependencies/your-war-project/lib
  

  The -p flag ensures all parent directories are created if they don't exist, so you won't get errors mid-command.

• Set proper permissions for your application user
  Whatever user runs your WAR (like tomcat for Tomcat deployments) needs read access to this directory. Fix permissions with:

  # Assume your app runs as the tomcat user/group
  sudo chown -R tomcat:tomcat /opt/app-dependencies/your-war-project
  sudo chmod -R 755 /opt/app-dependencies/your-war-project
  

  755 gives the owner full access and read/execute to others—perfect for letting your app load dependencies without security issues.

• Configure your application server to recognize the path
  This depends on your container, but for Tomcat (the most common for WARs), you have two solid options:

  1. Add to Tomcat's global classpath: Edit catalina.properties and update the common.loader line to include your dependency path:

     common.loader=${catalina.base}/lib,${catalina.base}/lib/*.jar,${catalina.home}/lib,${catalina.home}/lib/*.jar,/opt/app-dependencies/your-war-project/lib/*.jar
     

  2. Link directly in your WAR's context: Create a META-INF/context.xml file in your project with this configuration to mount the dependency directory as your WAR's WEB-INF/lib:

     <Context>
       <Resources>
         <PreResources base="/opt/app-dependencies/your-war-project/lib" className="org.apache.catalina.webresources.DirResourceSet" webAppMount="/WEB-INF/lib"/>
       </Resources>
     </Context>
     

2. Speed up WAR deployment by loading dependencies from a specified path #

Your 26.3MB WAR is slow to deploy because it's carrying all its dependencies along. Stripping those out and loading them from the server's local path will cut deployment time drastically. Here's the playbook:

• Modify your build config to exclude dependencies from the WAR
  If you're using Maven (the standard for Java WARs), update your pom.xml to tell the war plugin to leave dependencies out, and generate a classpath manifest pointing to your server's dependency path:

  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-war-plugin</artifactId>
        <version>3.3.2</version>
        <configuration>
          <!-- Don't package jars into WEB-INF/lib -->
          <packagingExcludes>WEB-INF/lib/*.jar</packagingExcludes>
          <!-- Generate a manifest that tells the app where to find dependencies -->
          <archive>
            <manifest>
              <addClasspath>true</addClasspath>
              <classpathPrefix>/opt/app-dependencies/your-war-project/lib/</classpathPrefix>
            </manifest>
          </archive>
        </configuration>
      </plugin>
    </plugins>
  </build>
  

  Now your built WAR will only contain your project code—way smaller and faster to upload!

• Sync dependencies to the server's path
  Use Maven to copy all your project's dependencies to a local folder, then upload them to the server:

  # Copy dependencies to a local target folder
  mvn dependency:copy-dependencies -DoutputDirectory=target/dependencies
  # Upload to the server's dependency path
  scp -r target/dependencies/* tomcat@your-server-ip:/opt/app-dependencies/your-war-project/lib/
  

  Don't forget to set permissions on the server like we did in the first question—otherwise your app will throw class not found errors.

• Verify the setup works
  Deploy your slimmed-down WAR, start your server, and check the logs for any ClassNotFoundException or similar errors. If logs are clean, test your app's core functionality to make sure all dependencies are loading correctly.

内容的提问来源于stack exchange，提问作者Attri