Hm, so I have two choices:
- Change the POM so that the failsafe plugin runs in the test phase, which
happens before the jar signing (that works BTW).
- Change the code to repackage the IT tests and make public all that the IT
tests need (I've not done that but I'll see what breaks)
Thank you all
I think the maven way is not much concerned with package structure, however why
not have a IT package? Do you have much need for package access in your ITs?
For Unit tests sharing the packages can be helpful, but for IT I would expect
it does not only need to be collocated, but it actually is be
Hi,
On 30/05/17 16:44, George Kopf wrote:
I apologize if this topic has already been discussed. I searched all over
the web and the archives and didn't find anything, but I can't believe that
I'm the only person with this request.
No need to apologize for asking...
I'm running the CI/CD pi
From: Gary Gregory
Sent: Monday, May 29, 2017 5:01 PM
To: Maven Users List
Subject: Running integration tests against a signed jar
Hi All:
I have a POM that builds a signed jar, so far so good. Unit tests run, no
problem.
When integration tests run through fai
Hello everyone,
I need to collect information about dependencies (their GAV only) of a very
large number of projects. Therefore I wrote a simple Maven plugin. It's is
based on maven-dependency-plugin, but reports dependencies in a format,
whihc I can use later.
However applying this plugin to pro
I think a BOM POM will work for your situation. The developers add your CI
POM as a dependency in dependencyManagement using import scope:
ci.pom.group
ci.pom
${ci.pom.version}
pom
import
Read about the import scope here: https://maven.apache
I apologize if this topic has already been discussed. I searched all over
the web and the archives and didn't find anything, but I can't believe that
I'm the only person with this request.
I'm running the CI/CD pipeline for several java projects.
We're using Git, Maven, Jenkins, Sonar, and Nexus