[jira] [Comment Edited] (OFBIZ-12808) Eclipse build problems and proper dependency setup

["Jacques Le Roux (Jira)" <ji...@apache.org>]

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

Jacques Le Roux edited comment on OFBIZ-12808 at 4/21/23 4:32 PM:
------------------------------------------------------------------

Thanks Michael,

All compile, no import issues (AFAIK) and works here (UI).

I'd just warn people using {{org.eclipse.jdt.core.compiler.ignoreUnnamedModuleForSplitPackage=enabled}} in {{.settings}} to remove it before applying the patches (or updating later); using gradlew eclipse is a solution. I'm not sure but it else seems to freeze Eclipse or makes it VERy, VEry, Very slow.


was (Author: jacques.le.roux):
Thanks Michael,

All compile, no import issues (AFAIK) and works here (UI).

I'd just warn people using {{org.eclipse.jdt.core.compiler.ignoreUnnamedModuleForSplitPackage=enabled}} in {{.settings}} to remove it before applying the patches (or updating later); using gralew eclipse is a solution. I'm not sure but it else seems to freeze Eclipse or makes it VERy, VEry, Very slow.

> Eclipse build problems and proper dependency setup
> --------------------------------------------------
>
>                 Key: OFBIZ-12808
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-12808
>             Project: OFBiz
>          Issue Type: Bug
>          Components: ALL APPLICATIONS, ALL COMPONENTS, ALL PLUGINS
>    Affects Versions: 22.01.01, Upcoming Branch
>            Reporter: Michael Brohl
>            Assignee: Michael Brohl
>            Priority: Major
>             Fix For: 22.01.01, Upcoming Branch
>
>
> Due to improper dependency configurations and the JPMS (Java Plattform Module System) which was introduced to Java since version 9, the Eclipse build and running/debugging is not working with JDK 17 (trunk and release22.01).
> The reason is that there are dependencies to libraries which are also shipped with the JDK which causes a conflict leading to ignore those packages/classes in the build.
> We have a working solution for this.



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