We first need to decide on the version this will get released as.
Updating everything to 3.4 now and to 4.0 two weeks later I can avoid
the duplicate effort this time.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
Am 12/16/16 um 21:36 schrieb Michael Osipov:
> Am 2016-12-16 um 18:41 schrieb Christian Schulte:
>> Am 12/15/16 um 22:49 schrieb Michael Osipov:
>>> I would expect a VALIDATION_LEVEL_MAVEN_3_4 with VALIDATION_LEVEL_STRICT
>>> = VALIDATION_LEVEL_MAVEN_3_1. All spots which say Severity errOn31 =
>>>
Am 2016-12-16 um 18:41 schrieb Christian Schulte:
Am 12/15/16 um 22:49 schrieb Michael Osipov:
I would expect a VALIDATION_LEVEL_MAVEN_3_4 with VALIDATION_LEVEL_STRICT
= VALIDATION_LEVEL_MAVEN_3_1. All spots which say Severity errOn31 =
getSeverity( request,
First commit is not relevant to the increase of the validation level,
BTW. Just the second one.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Am 12/15/16 um 22:49 schrieb Michael Osipov:
> I would expect a VALIDATION_LEVEL_MAVEN_3_4 with VALIDATION_LEVEL_STRICT
> = VALIDATION_LEVEL_MAVEN_3_1. All spots which say Severity errOn31 =
> getSeverity( request, ModelBuildingRequest.VALIDATION_LEVEL_MAVEN_3_1 );
> must be turned into
Hi,
I have tried Maven 3.4.0-SNAPSHOT on an in-house project today where the
build has failed with a POM validation error telling me that I have
duplicate plugin declaration. I have traced the issue down to
DefaultModelValidator#validate20RawPlugins() but did not understand that
either
