I’m using Maven in a CI scenario right now making use of the -am and -amd
switches. We are having an issue right now with how the list of projects to
make is solved. Consider the following five projects:
A, B, C, D, and E.
The dependencies between these projects are as follows:
E depends on A
looks like you got a html document instead of a pom file as a response
On 2020-03-12 20:00, Rune Gellein wrote:
Hi,
I was have just moved to using the maven resolver ant task and I am now
getting this error:
/org.apache.maven.model.building.ModelBuildingException: 4 problems were
encountered whi
Hi,
I was have just moved to using the maven resolver ant task and I am now
getting this error:
/org.apache.maven.model.building.ModelBuildingException: 4 problems were
encountered while building the effective model for com.sun.xml.ws:rt:2.3.1
[FATAL] Non-parseable POM
C:\Users\me\m\org\glassfish\j
refactor foo to a multimodule one with the test utilities as an artifact
and one with the code + tests for original foo, you can then depend on
the test module with scope test in the main module and keep everything
in source repo making it easy to stay in sync
On 12-03-2020 14:55, Andreas Sewe
I'd say option 4 is the way to go. But you need to solve the circular
dependency problem. One way is to have a third api project/module, which
foo-test-utils have a compile time dependency on. Here you could use the
Service Provider Interface pattern.
/Anders
On Thu, Mar 12, 2020 at 2:55 PM Andre
Hi,
I am struggling to figure out what the Maven Way is for distributing
test utils.
Say I have a project "foo" along with some unit tests for it. Moreover,
I have some utilities that help in testing "foo" (e.g., test data
builders or test fixtures). These utilities are used by the unit tests
for
