Am 11/20/16 um 03:28 schrieb Igor Fedorenko: > I am sorry, Christian, I must be missing something obvious. When I try > building the IT project you suggested as an expect of correct parent > version usage [1] I get the error below when using current 3.4 master. > Are you able to build the project successfully?
Sure you are running the ITs @HEAD? That's what Jenkins is running and nothing fails there. The error message is what you get with the unfixed IT and then is expected. When I say "local" vs. "remote" parent resolution behave exactly the same there is one liddle difference left. For local poms, there is no way to check the version range in use contains an upper bound due to a different API in use. For external poms, there is an additional check that the range does contain an upper bound. Do you really have projects where the <version> in <parent> is using a version range and do inherit the project version from the parent? How could you ever deploy something like that to a repository? Asking because I'd like to understand why you could not notice that these projects are not working as expected. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
