Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Not A Problem
-
3.5.0
-
None
-
None
-
None
Description
After starting to use Maven 3.5.0 multiple instances of the attached exceptions started occurring when multiple builds are using and installing modules of the same reactor. I sanitized the module name.
Maven 3.3.9 did not have this issue