[
https://issues.apache.org/jira/browse/OFBIZ-13207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17922436#comment-17922436
]
Steve commented on OFBIZ-13207:
-------------------------------
Webshop/ecommerce.
documentation and post-build of 18.12 +JDK 5, url is
[https://localhost:8443/ecommerce/control/main]
post-build of 24 +JDK 17, url is NOT
[https://localhost:8443/ecommerce/control/main]
or rather I get this
HTTP Status 404 – Not Found
Type Status Report
Description The origin server did not find a current representation for the
target resource or is not willing to disclose that one exists.
Apache Tomcat/9.0.97
ofbiz is in C/ root both times.
Admin works.
"in the INSTALL you clarified JDK 17 as a specific requirement"
I mean that the INSTALL doc for a version should specify what version of JDK to
use for +*that*+ version.
I appreciate the difficulty in keeping the multiple descriptions of the install
process in sync from various docs, wiki, web front page etc...
But this leads to my initial issues:
[https://cwiki.apache.org/confluence/display/ofbiz/demo+and+test+setup+guide]
"Download and install Java 1.8 or higher"
All descriptions should just state "use the JDK version as indicated in the
INSTALL" doc. And then you only ever have to update the INSTALL.
> Installation documentation (Windows 11 frustrated installation)
> ---------------------------------------------------------------
>
> Key: OFBIZ-13207
> URL: https://issues.apache.org/jira/browse/OFBIZ-13207
> Project: OFBiz
> Issue Type: Improvement
> Components: ALL COMPONENTS
> Affects Versions: 18.12.17
> Environment: Windows 11.
> Reporter: Steve
> Assignee: Jacques Le Roux
> Priority: Trivial
>
> Background 45 years using computers, 20 years as a business owner.
> Trying Ofbiz as a replacement for legacy invoicing software and ecommerce
> site.
> Install says: install JDK.
> Current JDK version is 23.
> Gradle Wrapper inOfbiz pulls in gradle 5.0-rc-5 (not even a release version).
> Consequently the build fails with piles of deprecation errors.
> From the gradle compatibility table, gradle 5 works with jdk 11, so I used
> that.
> This allowed the build to complete, but still with a pile of deprecation
> notices.
> The last couple of sentences do not reflect the frustration and time wasted
> in reading about unfamiliar concepts and understanding the
> problems….something NO BUSINESS USER would ordinarily be able to do, nor
> would have the time. So Ofbiz goes in the bin at this point/goodbye potential
> user.
>
> As I’m a fighter I tried to use the current gradle 18.1.12 with the current
> JDK 23.
> This requires replacing various obsolete method names in the files
> build.gradle and solr\build.gradle
> before I was eventually beaten by aspectjweaver-1.8.9.jar; Invalid CEN header
> which I could not overcome despite repeated downloads and using -U in gradlew.
> All the above is unthinkable for a potential user.
> None of the above can be attribute to Windows, as far as I can tell…so no-one
> has come across these problems in the last X years? No-one has installed it?
> Added to the very low commit rate in Github, it seems to be evident that
> Ofbiz is staggering along a purely maintenance path. Unless there is some
> evidence to the contrary somewhere.
> Shame, it could be a world beater. I wanted it to be the solution.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
