[
https://issues.apache.org/jira/browse/MNG-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Kanters closed MNG-6990.
-------------------------------
Assignee: Martin Kanters
Resolution: Not A Bug
> Build order not set corectly
> ----------------------------
>
> Key: MNG-6990
> URL: https://issues.apache.org/jira/browse/MNG-6990
> Project: Maven
> Issue Type: Bug
> Components: Bootstrap & Build
> Affects Versions: 3.3.9, 3.5.3, 3.6.3
> Environment: OS:
> Kubuntu 18.04 LTS
> JDK:
> openjdk version "1.8.0_265"
> OpenJDK Runtime Environment (build 1.8.0_265-8u265-b01-0ubuntu2~18.04-b01)
> OpenJDK 64-Bit Server VM (build 25.265-b01, mixed mode)
> Projects have been tested with Eclipse Photon, 2020-06, 2020-09
> Reporter: Stefano Cazzola
> Assignee: Martin Kanters
> Priority: Major
> Attachments: test-no-parent.zip, test-with-parent-fixed.zip,
> test-with-parent.zip
>
>
> It seems that Maven is not able to decide the correct build order when two
> projects extend the same parent but one has a dependency on the other.
> More precisely, it seems that whenever projects extend the same parent, they
> are built following the alphabetical order: this means that if project A
> depends on project B, it is nonetheless built before B, generating
> compilation error.
> I've created some very simple example I'm attaching to this ticket, one using
> a parent (which does not compile), one not (which does compile).
> Please note that I tested specifically against the versions I mentioned. I
> would not be able to say if in previous versions the build order was detected
> corretcly, or if it was resolved in some intermediate version.
> Please note also that I am not able to tell if it's a Maven or Eclipse issue.
> For this reason I'm filing the same ticket to the Eclipse Team.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
