[
https://issues.apache.org/jira/browse/MNG-7667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MNG-7667:
---------------------------------
Description:
A problem with our IT suite:
Version of Maven used in outer build (the one we invoke on CLI, usually a
"stable/release" maven version) and the version of Maven used in inner build
(the version we test) usually differ, that's the point of test suite after all.
Problem: while outer build applies "best practices" re build, so it locks down
all the plugin versions, the inner build use "bare" or "simple" POMs, so it is
totally dependent on the plugin versions found in default life-cycle bindings
of the Maven version being tested.
The "bootstrap" list (list of artifacts we pre-populate into local repository
before ITs start) is really not a static list, but is dynamic.
was:
A problem with out IT suite:
Version of Maven used in outer build (the one we invoke on CLI, usually a
"stable/release" maven version) and the version of Maven used in inner build
(the version we test) usually differ, that's the point of test suite after all.
Problem: while outer build applies "best practices" re build, so it locks down
all the plugin versions, the inner build use "bare" or "simple" POMs, so it is
totally dependent on the plugin versions found in default life-cycle bindings
of the Maven version being tested.
The "bootstrap" list (list of artifacts we pre-populate into local repository
before ITs start) is really not a static list, but is dynamic.
> IT suite fails if tested Maven lifecycle binding contains plugin version not
> in bootstrap
> -----------------------------------------------------------------------------------------
>
> Key: MNG-7667
> URL: https://issues.apache.org/jira/browse/MNG-7667
> Project: Maven
> Issue Type: Bug
> Components: Integration Tests
> Reporter: Tamas Cservenak
> Priority: Major
>
> A problem with our IT suite:
> Version of Maven used in outer build (the one we invoke on CLI, usually a
> "stable/release" maven version) and the version of Maven used in inner build
> (the version we test) usually differ, that's the point of test suite after
> all.
> Problem: while outer build applies "best practices" re build, so it locks
> down all the plugin versions, the inner build use "bare" or "simple" POMs, so
> it is totally dependent on the plugin versions found in default life-cycle
> bindings of the Maven version being tested.
> The "bootstrap" list (list of artifacts we pre-populate into local repository
> before ITs start) is really not a static list, but is dynamic.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
