Answers to: Add library with pom.xml

Comment by adamf on adamf's answer

adamf — Mon, 25 Sep 2017 08:50:30 -0400

yeah, I already noticed that src and src_test are copied compiled into classes. Wonder if things get easier if ivy project conforms to standard maven project directory layout (src/main/java, src/test/java, src/main/resources, ..). Great about TDD is that you have less chance of introducing regressions or bugs. When having tests separate there is less motivation to keep them up to date and increased complexity for continuous integration.

Comment by Reguel Wermelinger on adamf's answer

Reguel Wermelinger — Mon, 25 Sep 2017 04:15:55 -0400

ok basically I like this approach. But I think the exclusions of test frameworks is not intuitive. I always suggest to create an extra project for test cases (Even tough standard maven handles it different). So you will never have code deps to test frameworks and therefore you do no need to exclude them while copying POM deps. If test and prod code is in the same projects, chances are ways to high that test code at some point of time will leak into production without notice...

Answer by adamf

adamf — Tue, 19 Sep 2017 11:45:18 -0400

Another way to use maven-dependency-plugin suggestested by Emmanuel is this:

<plugin>
    <artifactId>maven-dependency-plugin</artifactId>
    <executions>
        <execution>
            <id>Copy-dependency-PROD</id>
            <phase>validate</phase>
            <goals>
                <goal>copy-dependencies</goal>
            </goals>
            <configuration combine.self="override">
            <outputDirectory>${basedir}/lib</outputDirectory>
            <stripVersion>true</stripVersion>
            <includeScope>compile</includeScope>
            <excludeGroupIds>org.powermock, org.hamcrest,org.mockito, junit, org.objenesis, org.sonarsource.java</excludeGroupIds>
            <excludeArtifactIds>jsf-api, javase, commons-codec</excludeArtifactIds>
            <excludeTypes>iar</excludeTypes>
            <excludeTransitive>true</excludeTransitive>
            </configuration>
        </execution>
    </executions>
</plugin>

This will include any jar dependency to the lib directory and is packged when running maven. In Desinger it still needs to be linked manually once by right clicking on the project, "Build Path.." -> Configure Build Path -> Add External JARs.

Comment by Reguel Wermelinger on Reguel Wermelinger's answer

Reguel Wermelinger — Tue, 11 Oct 2016 15:35:23 -0400

Try to use the latest project-build-plugin:6.3.0 as it has several improvements in the classpath handling: http://axonivy.github.io/project-build-plugin/release/6.3/index.html

If the commandline execution still does not work. Run mvn clean install -X and share the debug output with us.

Comment by Gerald on Reguel Wermelinger's answer

Gerald — Tue, 11 Oct 2016 13:19:50 -0400

Hi, thx for the answer. This works well and I have the lib in the local project folder. But I still cannot execute a "mvn compile" (I want to run the build process on a Jenkins later).

I added the lib in Axon Ivy and it tells me that there are no longer missing references. But, as mentioned, the command line process cannot find it. Do I need to define the local library somewhere else for Maven?

Thx in advance,

Gerald

Answer by Reguel Wermelinger

Reguel Wermelinger — Tue, 11 Oct 2016 09:04:14 -0400

The thing is, that only IAR maven-dependencies are included in the projects classpath on the engine. There is currently no built in support to include normal JAR dependencies in a project and auto-download them when a project is deployed to an engine.

A simple work-around is to add the maven-dependency-copy plugin to your POM.xml. It will copy JAR dependencies to a directory in your project and you can add it to the classapth:

<build>
<plugins>
...
    <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-dependency-plugin</artifactId>
        <version>2.10</version>
        <executions>
            <execution>
                <id>copy.maven.dependencies</id>
                <goals><goal>copy</goal></goals>
                <phase>generate-resources</phase>
                <configuration>
                    <outputDirectory>lib</outputDirectory>
                    <artifactItems>
                        <artifactItem>
                            <groupId>com.opencsv</groupId>
                            <artifactId>opencsv</artifactId>
                            <version>3.8</version>
                        </artifactItem>
                    </artifactItems>
                </configuration>
            </execution>
        </executions>
    </plugin>
</plugins>
</build>

With this configuration you can run mvn clean generate-resources, refresh your project in the workspace afterwards and add the JARs in the lib directory to your classpath via: Java Perspective -> Right click on Jar -> build path -> add to build path

Comment by Hap Em on Gerald's question

Hap Em — Tue, 11 Oct 2016 03:49:24 -0400

Could you include your pom file?