[ 
https://issues.apache.org/jira/browse/YETUS-860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16839603#comment-16839603
 ] 

Allen Wittenauer commented on YETUS-860:
----------------------------------------

OK, a bit more depth on this issue. It's not Yetus specific.

During the branch phase, we do a maven install at UNION, which in this case 
will be the root of the tree. This lays down the old version's data.  (UNION 
here is already suspect since this makes the assumption that all modules are 
available to fetch from a remote repository. That's clearly not always going to 
be true.)

Cycle continues

Patch gets applied.  Now pom.xml has new version.

We run through an ordered list of maven modules.  Alas! The ordering 
specifically puts root last to test mvn install and fetch.  But this won't work 
because we can't fetch the new version.

To fix this, a few changes:

1) branch's mvn install absolutely must be root. UNION doesn't work as pointed 
out above.
2) We need to keep track of the root pom's version.  It's as good as any 
indicator for most projects that the version is going to change.  An 
enhancement could be to keep track of every version, but that seems like high 
work/low reward right now.
3) If we detect that the root pom's version has changed, run through mvn 
install at the branch level root again. This makes the mvn install test that 
happens next useless, but we're going to get invalid data anyway.



> mvn dependency order needs special handling for version change
> --------------------------------------------------------------
>
>                 Key: YETUS-860
>                 URL: https://issues.apache.org/jira/browse/YETUS-860
>             Project: Yetus
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 0.9.0, 0.10.0
>            Reporter: Allen Wittenauer
>            Assignee: Allen Wittenauer
>            Priority: Critical
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> Working on YETUS-859 has shown that the maven ordering is not getting handled 
> properly, at least when building Yetus.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to