[jira] [Commented] (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=17723933#comment-17723933 ] 

Jacques Le Roux commented on OFBIZ-12808:
-----------------------------------------

While working on OFBIZ-10478 I have found possible issues inside UtilHtml::hasUnclosedTag. According to Eclipse some imports are missing. It's OK in UtilXml.java for instance.

Missing imports seem to be
{color:#c5681c}import{color}{color:#e3e6e8} {color}{color:#e3e6e8}javax{color}{color:#e9ebed}.{color}{color:#e3e6e8}xml{color}{color:#e9ebed}.{color}{color:#e3e6e8}stream{color}{color:#e9ebed}.{color}{color:#e3e6e8}XMLEventReader{color}{color:#e9ebed};{color}

{color:#c5681c}import{color}{color:#e3e6e8} {color}{color:#e3e6e8}javax{color}{color:#e9ebed}.{color}{color:#e3e6e8}xml{color}{color:#e9ebed}.{color}{color:#e3e6e8}stream{color}{color:#e9ebed}.{color}{color:#e3e6e8}XMLInputFactory{color}{color:#e9ebed};{color}

 

 The error for both is
The package javax.xml.stream is accessible from more than one module: <unnamed>, java.xml

> 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)