As Anthony said as you have a chicken-egg problem and you need to break the
cycle somehow.
To cut the loop I would eventually either:
Solution 1: split the projects into:
1. the library itself without tests
2. the test library, depending on the lib
3. the library tests depending on both
Hello,
Thanks for your idea, and yes I think I have got a chick-egg problem, but the
solution, which works for me, was easy.
The testing framework is used only on „testing“ goal and the test source code
contains 3 classes only, so I have stored
these classes in a single Git repository and
You can specify a dependency version using an expression like this:
${project.version}
${project.version} refers to the POM’s project/version value.
Note that you can declare project properties, and use those in expressions too.
See this for more details:
-
Hello,
I am building an additional testing framework for my framework. I now have the
following cyclic import of the dependencies "MyFramework imports
MyTestingFramework" and "MyTestingFramework imports MyFramework".
For example, if MyFramework is version 0.2.1-SNAPSHOT, then MyTestingFramework
