Thanks for your feedback Taher,
Rest inline...
Le 26/06/2018 à 18:49, Taher Alkhateeb a écrit :
Ok, so you have a plugin that essentially prints out a report of
dependencies and decides which ones are up to date. Here are my
thoughts
- First, your patch is not correct and does not add the
Ok, so you have a plugin that essentially prints out a report of
dependencies and decides which ones are up to date. Here are my
thoughts
- First, your patch is not correct and does not add the task you
mentioned. It seems you didn't test it?
- Upon testing this plugin, I found packages that
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
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
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
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
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
