添加JasperReports依赖后运行Maven项目报错求助

Hey there! Let's figure out why your Maven project is throwing errors after adding JasperReports dependencies. From the partial pom.xml you shared, here are the most common fixes and checks you can run through:

1. Ensure You Have All Required JasperReports Dependencies #

JasperReports relies on several transitive dependencies that are easy to miss if you only add the core jar. Make sure your <dependencies> section includes a complete setup like this:

<dependencies>
    <!-- JasperReports Core Library -->
    <dependency>
        <groupId>net.sf.jasperreports</groupId>
        <artifactId>jasperreports</artifactId>
        <version>6.20.6</version> <!-- Use the *latest stable version* for best compatibility -->
    </dependency>
    <!-- Required for PDF export functionality -->
    <dependency>
        <groupId>com.lowagie</groupId>
        <artifactId>itext</artifactId>
        <version>2.1.7</version>
    </dependency>
    <!-- Handles font rendering in reports -->
    <dependency>
        <groupId>net.sf.jasperreports</groupId>
        <artifactId>jasperreports-fonts</artifactId>
        <version>6.20.6</version>
    </dependency>
</dependencies>

2. Resolve Dependency Conflicts #

Maven might pull in conflicting versions of libraries (like commons-collections, log4j, or iText) that clash with your project or JasperReports. To spot these conflicts, run this command in your project directory:

mvn dependency:tree -Dverbose

Once you identify a conflicting artifact, use <exclusions> in your JasperReports dependency to exclude it. For example:

<dependency>
    <groupId>net.sf.jasperreports</groupId>
    <artifactId>jasperreports</artifactId>
    <version>6.20.6</version>
    <exclusions>
        <exclusion>
            <groupId>commons-collections</groupId>
            <artifactId>commons-collections</artifactId>
        </exclusion>
    </exclusions>
</dependency>

3. Fix Packaging for Desktop/JavaFX Projects #

Your pom shows <packaging>jar</packaging>—since your artifactId is prjInfoXFX (hinting at a JavaFX app), you need to ensure all JasperReports dependencies are included in your runtime. The Maven Shade Plugin is perfect for bundling everything into a single executable jar:

<build>
    <plugins>
        <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-shade-plugin</artifactId>
            <version>3.4.1</version>
            <executions>
                <execution>
                    <phase>package</phase>
                    <goals>
                        <goal>shade</goal>
                    </goals>
                    <configuration>
                        <transformers>
                            <transformer implementation="org.apache.maven.plugins.shade.resource.ManifestResourceTransformer">
                                <mainClass>your.main.class.path.Here</mainClass> <!-- Replace with your actual main class path -->
                            </transformer>
                        </transformers>
                    </configuration>
                </execution>
            </executions>
        </plugin>
    </plugins>
</build>

4. Verify Repository Configuration #

Sometimes Maven can't find JasperReports artifacts if your repository setup is incomplete. Double-check that your pom includes the Maven Central repository (it's usually there by default, but it never hurts to confirm):

<repositories>
    <repository>
        <id>central</id>
        <url>https://repo.maven.apache.org/maven2</url>
    </repository>
</repositories>

5. Clean and Rebuild Your Project #

Stale build files are a common culprit. Run these commands to wipe old builds and refresh dependencies:

mvn clean install -U

The -U flag forces Maven to update any snapshot dependencies to their latest versions.

If you can share the exact error message (like NoClassDefFoundError, missing artifact logs, or build failure details), we can narrow this down even more precisely!

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