[
https://issues.apache.org/jira/browse/OFBIZ-12808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17714999#comment-17714999
]
Daniel Watford commented on OFBIZ-12808:
----------------------------------------
Hi [~mbrohl] ,
Would a non-eclipse user be able to recognise if they introduce the same sort
of issue again, perhaps by adding new dependencies to plugins?
Is it something the gradle could detect and use to deliberately fail a build?
> 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)
