如何将Eclipse Java动态Web项目从SVN转Git后部署到Jenkins？转Maven需改代码吗？

Hey there! Let me break this down for you clearly— I’ve been in a similar situation with migrating legacy Eclipse web projects to Jenkins, so I get the time crunch and confusion.

Jenkins does NOT only support Maven projects! It can handle all kinds of Java projects, including your traditional Eclipse dynamic web app. That said, using Maven will make your Jenkins build/deploy workflow way more automated and maintainable, so let’s focus on that transition first.

Absolutely not! Maven is all about dependency management and build process standardization— your business code stays almost entirely untouched. You’ll just be adding configuration files and organizing your project structure, not rewriting logic.

1. Set up the standard Maven project structure #

Adjust your Eclipse project to match Maven’s default layout (Eclipse can do this automatically):

your-project/
├── src/
│   ├── main/
│   │   ├── java/       # Move all your existing Java code here from the old src folder
│   │   ├── resources/  # Move config files (properties, XMLs) here
│   │   └── webapp/     # Relocate your old WebContent folder here (includes WEB-INF, static assets)
│   └── test/           # Optional, but useful for test code later
└── pom.xml             # The core Maven config file we’ll build out

In Eclipse, right-click your project → Configure → Convert to Maven Project— this generates a basic pom.xml for you, saving tons of manual work.

2. Configure the pom.xml key sections #

Focus on these essential parts:

• Project identity: Add groupId, artifactId, version to identify your project
• Packaging type: Set <packaging>war</packaging> since this is a web app
• Dependency management: Replace JARs in WEB-INF/lib with Maven dependency coordinates. For example, instead of keeping servlet-api.jar locally, use:

  <dependency>
      <groupId>javax.servlet</groupId>
      <artifactId>javax.servlet-api</artifactId>
      <version>4.0.1</version>
      <scope>provided</scope> <!-- The app server (Tomcat, etc.) provides this, no need to package it -->
  </dependency>
  

  You don’t have to look up every coordinate manually: right-click the project → Maven → Add Dependency to search and auto-import, or drag JARs from WEB-INF/lib into the <dependencies> section of pom.xml— Eclipse will auto-fill coordinates for most common JARs.
• Build plugin for WAR packaging: Add the maven-war-plugin to ensure proper WAR generation:

  <build>
      <plugins>
          <plugin>
              <groupId>org.apache.maven.plugins</groupId>
              <artifactId>maven-war-plugin</artifactId>
              <version>3.3.2</version>
              <configuration>
                  <warSourceDirectory>src/main/webapp</warSourceDirectory>
                  <failOnMissingWebXml>false</failOnMissingWebXml> <!-- Skip if you use Servlet 3.0+ annotations instead of web.xml -->
              </configuration>
          </plugin>
      </plugins>
  </build>
  

3. Handle custom build needs (if any) #

If your project requires specific Java versions or custom build steps, add plugins like maven-compiler-plugin to enforce settings:

<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-compiler-plugin</artifactId>
    <version>3.11.0</version>
    <configuration>
        <source>1.8</source> <!-- Match your project's Java version -->
        <target>1.8</target>
    </configuration>
</plugin>

• SVN to Git migration: Use git svn clone to migrate your entire SVN repo (including history) to Git. Once done, Jenkins can pull directly from Git— it’s simpler to configure than SVN.
• Jenkins deployment shortcut: If you’re pressed for time, you don’t have to switch to Maven immediately. Set up a Freestyle project in Jenkins, configure it to pull from Git, and use your existing Eclipse Ant script (if you have one) or manual build commands to compile/package the WAR, then deploy via the Deploy to container plugin. You can refine to Maven later.
• Automate deployment with Maven: Once you’re on Maven, use the maven-cargo-plugin to auto-deploy your WAR to Tomcat/JBoss directly from the build, cutting out manual steps.

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