[
https://issues.apache.org/jira/browse/YETUS-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16221740#comment-16221740
]
Allen Wittenauer commented on YETUS-559:
----------------------------------------
One of the big topics that I've hit time and time again when reading about
maven folks is the idea that in a multi module layout of being able to only
checkout that module and doing a build. From a Yetus testing perspective, this
specifically means not doing root first and even going so far as randomizing
the module build list for that initial mvn install. Because as soon as one
hits root, the maven repo cache has been updated and any potential violation of
that rule has been missed.
bq. Are we really saying those folks should all customize via personality?
Yes, because not every potential project that Yetus might run on has this issue
and might actually want to make sure their dependencies are working as
intended. There's also the issue of actually getting it correct, because root
may not be it either. Hadoop, for example, really wants hadoop-maven-plugins
built first, not root. Nifi, for a while there, was just a land of unconnected
modules.
Also: looking at maven's own root pom, I think most of us are probably doing
it wrong to begin with...
> mvn reordering should put root first
> ------------------------------------
>
> Key: YETUS-559
> URL: https://issues.apache.org/jira/browse/YETUS-559
> Project: Yetus
> Issue Type: Improvement
> Components: Test Patch
> Affects Versions: 0.4.0
> Reporter: Mike Drob
> Attachments: YETUS-559.patch
>
>
> when doing the maven module reordering, we currently put root module at the
> end. however, if child modules depend on changes in the root module, then
> they will fail (at mvn install) since they will be looking at the old root
> pom.
> See comment at
> https://issues.apache.org/jira/browse/HBASE-16338?focusedCommentId=16208146&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16208146
> for an example of how this can fail.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
