On 2016-03-22 22:24, Christophe Thiebaud wrote:
Hi all,
for those interested, I stumbled on a (natural) defect with the approach
"#2 "super" multi-module pom" (cf.
http://dag.cloud/docs/theproblem.html)
e.g.
let A and B be 2 projects that need ordering
let A be i
it was less than 100 for sure, but probably more than 20),
>> and
>> that worked fine.
>>
>> I wasn't aware of the Maven event spy approach. That sounds like a
>> tidy,
>> albeit more technical, solution. I don't think we were able to
>> successful
, Mar 15, 2016 at 4:17 PM, Christophe Thiebaud <
christophe.thiebaud@dag.cloud> wrote:
Hi all,
The problem is all in the title :
How to find the correct build order of a set of distinct but
interdependent projects.
Distinct means that each project lives in its own source repository,
wasn't aware of the Maven event spy approach. That sounds like a
tidy,
albeit more technical, solution. I don't think we were able to
successfully use the dependency plugin, but this was a few years ago
and
the plugin may have advanced since then.
On Tue, Mar 15, 2016 at 4:1
Hi all,
The problem is all in the title :
How to find the correct build order of a set of distinct but
interdependent projects.
Distinct means that each project lives in its own source repository,
each project build separately.
Interdependent means that projects may be dependent upon each
