[
https://issues.apache.org/jira/browse/OFBIZ-13207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17922936#comment-17922936
]
Steve commented on OFBIZ-13207:
-------------------------------
Ok, after more experimenting....
I conclude that the content of the plugins folder needs to be in place *before*
the build.
I used the trunk framework and the 24.09 plugins, with JDK 17..0.14
It won't build:
C:\ofbiz>gradlew cleanAll loadAll
Starting a Gradle Daemon (subsequent builds will be faster)
> Task :buildSrc:extractPluginRequests
> Task :buildSrc:generatePluginAdapters
> Task :buildSrc:compileJava
> Task :buildSrc:compileGroovy NO-SOURCE
> Task :buildSrc:compileGroovyPlugins
> Task :buildSrc:pluginDescriptors
> Task :buildSrc:processResources
> Task :buildSrc:classes
> Task :buildSrc:jar
FAILURE: Build completed with 2 failures.
1: Task failed with an exception.
-----------
* Where:
Build file 'C:\ofbiz\plugins\solr\build.gradle' line: 30
* What went wrong:
A problem occurred evaluating project ':plugins:solr'.
> No signature of method:
> org.gradle.api.internal.artifacts.ivyservice.dependencysubstitution.DefaultDependencySubstitutions$1.with()
> is applicable for argument types:
> (org.gradle.internal.component.external.model.DefaultModuleComponentSelector)
> values: [com.google.guava:guava:28.0-jre]
Possible solutions: with(groovy.lang.Closure), with(boolean,
groovy.lang.Closure), wait(), wait(long), find(), wait(long, int)
* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Get more help at https://help.gradle.org.
==============================================================================
2: Task failed with an exception.
-----------
* What went wrong:
A problem occurred configuring root project 'ofbiz'.
> No hooks found
* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Get more help at https://help.gradle.org.
==============================================================================
Deprecated Gradle features were used in this build, making it incompatible with
Gradle 9.0.
> 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)
