You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@causeway.apache.org by "Andi Huber (Jira)" <ji...@apache.org> on 2023/07/05 08:27:00 UTC

[jira] [Commented] (CAUSEWAY-3520) Framework fails to build with Eclipse M2E 2.4.0.20230704-1545

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

Andi Huber commented on CAUSEWAY-3520:
--------------------------------------

M2E refuses to build some projects that have no module-info file. However, before switching to jakarta namespace, its hard to migrate all projects to module-path. 

As a workaround, I'm reverting m2e to an earlier version from May-2023 or something.

> Framework fails to build with Eclipse M2E 2.4.0.20230704-1545
> -------------------------------------------------------------
>
>                 Key: CAUSEWAY-3520
>                 URL: https://issues.apache.org/jira/browse/CAUSEWAY-3520
>             Project: Causeway
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Andi Huber
>            Assignee: Andi Huber
>            Priority: Major
>             Fix For: 2.0.0-RC2
>
>
> Latest m2e version, seems more sensitive to module.info/pom inconsistencies.
> My M2E version:
> Eclipse.org - m2e	M2E Maven Integration for Eclipse Core	2.4.0.20230704-1545	org.eclipse.m2e.feature



--
This message was sent by Atlassian Jira
(v8.20.10#820010)