I thought my 1st message was clear enough. Let me try to phrase it better.
In order for our users to have an easier and secure life, I suggest to have
this patch applied
Index: build.gradle
===================================================================
--- build.gradle (révision 1834418)
+++ build.gradle (copie de travail)
@@ -31,6 +31,7 @@
classpath 'at.bxm.gradleplugins:gradle-svntools-plugin:latest.release'
classpath 'org.asciidoctor:asciidoctor-gradle-plugin:1.5.7'
classpath 'org.asciidoctor:asciidoctorj-pdf:1.5.0-alpha.16'
+ classpath 'com.github.ben-manes:gradle-versions-plugin:0.17.0'
}
}
apply plugin: 'java'
And to create a Gradle task to use it. Actually just run
./gradlew dependencyUpdates -Drevision=release
And of course to document it in our main README
It would clarify how to keep libs updated to our users rather than having to
look for this in Jira or by themselves.
What do you think (not only you Taher ;)) ?
Jacques
Le 26/06/2018 à 10:56, Taher Alkhateeb a écrit :
I'm not sure I understand what you want to do exactly. Clarification would help
On Tue, Jun 26, 2018 at 11:27 AM, Jacques Le Roux
<jacques.le.r...@les7arts.com> wrote:
Hi,
Nobody interested? So sounds like a lazy consensus.
Without any more comments I'll open a Jira and attach a patch
Jacques
Le 11/06/2018 à 14:02, Jacques Le Roux a écrit :
Hi,
I was wondering: some projects use the trunk or I guess more often a
release branch as source.
Should we not provide them a way to check the branch they use has the last
libs versions using gradle-versions-plugin with a documented tasks, or
should this stay (a bit buried) in one of our Jiras?
I mean in a more global way, should we not document that for our users?
Jacques
