[ 
https://issues.apache.org/jira/browse/OFBIZ-10213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacques Le Roux updated OFBIZ-10213:
------------------------------------
    Description: 
h2. This is an umbrella task for its action subtasks, please do not close, 
thanks.

We want to check from time to time if we need to update the dependencies.

It's easily done with the [gradle-versions-plugin 
|https://github.com/ben-manes/gradle-versions-plugin] which analyzes the 
dependencies and checks if there are newer versions available.

Running the check with
{code:java}
gradlew -PenableDependencyUpdates dependencyUpdates -Drevision=release
{code}
We get a list of dependencies to update.
Another option is to use
{code:java}
gradlew -PenableDependencyUpdates useLatestVersions && gradlew 
-PenableDependencyUpdates useLatestVersionsCheck
{code}
but useLatestVersionsCheck may fail. So it's like if you were using 
useLatestVersions (which does not fail) alone. Hence with all updates put in. 
With the current comments about versions in dependencies.gradle it's now 
reasonable to use (2024-12-13).

We have problems with a number of libs. We keep comments in the main 
build.gradle for special updating issues. Be sure to check the main 
build.gradle. Some Java classes need internal versions update too:

Also Solr et Lucene should use the same version, luceneMatchVersion should be 
updated in solrconfig.xml

  was:
h2. This is an umbrella task for its action subtasks, please do not close, 
thanks.

We want to check from time to time if we need to update the dependencies.

It's easily done with the [gradle-versions-plugin 
|https://github.com/ben-manes/gradle-versions-plugin] which analyzes the 
dependencies and checks if there are newer versions available.

Running the check with
{code:java}
gradlew -PenableDependencyUpdates dependencyUpdates -Drevision=release
{code}
We get a list of dependencies to update.

We have problems with a number of libs. We keep comments in the main 
build.gradle for special updating issues. Be sure to check the main 
build.gradle. Some Java classes need internal versions update too:

Also Solr et Lucene should use the same version, luceneMatchVersion should be 
updated in solrconfig.xml


> Update build.gradle to the latest dependencies
> ----------------------------------------------
>
>                 Key: OFBIZ-10213
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-10213
>             Project: OFBiz
>          Issue Type: Task
>          Components: Gradle
>    Affects Versions: Trunk, Upcoming Branch
>            Reporter: Jacques Le Roux
>            Priority: Trivial
>         Attachments: OFBIZ-10213.patch, OFBIZ-10213.patch, OFBIZ-10213.patch
>
>
> h2. This is an umbrella task for its action subtasks, please do not close, 
> thanks.
> We want to check from time to time if we need to update the dependencies.
> It's easily done with the [gradle-versions-plugin 
> |https://github.com/ben-manes/gradle-versions-plugin] which analyzes the 
> dependencies and checks if there are newer versions available.
> Running the check with
> {code:java}
> gradlew -PenableDependencyUpdates dependencyUpdates -Drevision=release
> {code}
> We get a list of dependencies to update.
> Another option is to use
> {code:java}
> gradlew -PenableDependencyUpdates useLatestVersions && gradlew 
> -PenableDependencyUpdates useLatestVersionsCheck
> {code}
> but useLatestVersionsCheck may fail. So it's like if you were using 
> useLatestVersions (which does not fail) alone. Hence with all updates put in. 
> With the current comments about versions in dependencies.gradle it's now 
> reasonable to use (2024-12-13).
> We have problems with a number of libs. We keep comments in the main 
> build.gradle for special updating issues. Be sure to check the main 
> build.gradle. Some Java classes need internal versions update too:
> Also Solr et Lucene should use the same version, luceneMatchVersion should be 
> updated in solrconfig.xml



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to