Steve created OFBIZ-13207:
-----------------------------

             Summary: 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


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)

Reply via email to