From issues-return-173046-archive-asf-public=cust-asf.ponee.io@maven.apache.org Tue Sep 22 09:59:03 2020 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mailroute1-lw-us.apache.org (mailroute1-lw-us.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with ESMTPS id E8D2F18063F for ; Tue, 22 Sep 2020 11:59:02 +0200 (CEST) Received: from mail.apache.org (localhost [127.0.0.1]) by mailroute1-lw-us.apache.org (ASF Mail Server at mailroute1-lw-us.apache.org) with SMTP id 2162B1234D9 for ; Tue, 22 Sep 2020 09:59:02 +0000 (UTC) Received: (qmail 74698 invoked by uid 500); 22 Sep 2020 09:59:01 -0000 Mailing-List: contact issues-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@maven.apache.org Delivered-To: mailing list issues@maven.apache.org Received: (qmail 74686 invoked by uid 99); 22 Sep 2020 09:59:01 -0000 Received: from mailrelay1-us-west.apache.org (HELO mailrelay1-us-west.apache.org) (209.188.14.139) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Sep 2020 09:59:01 +0000 Received: from jira-he-de.apache.org (static.172.67.40.188.clients.your-server.de [188.40.67.172]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 972774048D for ; Tue, 22 Sep 2020 09:59:00 +0000 (UTC) Received: from jira-he-de.apache.org (localhost.localdomain [127.0.0.1]) by jira-he-de.apache.org (ASF Mail Server at jira-he-de.apache.org) with ESMTP id 17454780203 for ; Tue, 22 Sep 2020 09:59:00 +0000 (UTC) Date: Tue, 22 Sep 2020 09:59:00 +0000 (UTC) From: "Stefano Cazzola (Jira)" To: issues@maven.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (MNG-6990) Build order not set corectly MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/MNG-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefano Cazzola updated MNG-6990: --------------------------------- Description: 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. was: 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 compiles successfully-, one not - which does not 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. > 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 > Priority: Major > Attachments: test-no-parent.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)