on this, I don't have exactly same opinion: yes, Maven 3.5.0 should behave like Maven 3.3.9, then we should fix Maven as much as possible and not force Surefire ITs to be changed
but if Surefire ITs define multiple times the same property on CLI, then use a edge case, removing the demendency on this edge case would not be a bad idea: in fact, I'd expect in a future Maven version that such multiple definition of a property on CLI would print a WARNING, because it shows some strange situation that people didn't expect Regards, Hervé Le dimanche 26 février 2017, 07:03:05 CET Christian Schulte a écrit : > Am 02/25/17 um 17:25 schrieb Tibor Digana: > >>> There are two commits for MNG-6078 part of -alpha-1. > > > > This was caused by system property duplicates in surefire ITs. > > It is already fixed in a branch SUREFIRE_SYSPROP_DUPLICATES. > > If something works with 3.3.9 but not 3.5.0, we need to fix it in Maven. > I think this is what Stephen did. No need to "fix" surefire ITs, if they > were working with 3.3.9 before. 3.5.0 would not be a drop in replacement > anymore that way. > > Regards, --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
