Hi everyone,
any objections against merging those pr's for framework/plugins in
trunk/release22.01?
I think it would be good to test the changes on the demo servers as well
to detect possible runtime problems caused by the changed dependencies.
If there are no objections, I would like to merge the changes tomorrow.
Thanks,
Michael Brohl
ecomify GmbH - www.ecomify.de
Am 21.04.23 um 14:54 schrieb Michael Brohl (Jira):
[
https://issues.apache.org/jira/browse/OFBIZ-12808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17714986#comment-17714986
]
Michael Brohl commented on OFBIZ-12808:
---------------------------------------
Fixes for framework / plugins for trunk and release22.01 are now in the pull
requests.
To test, the corresponding pr's for framework and plugins have to be checked
out respectively.
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)
