hence why UK gov.want to hire 3,500 cyber-warriors ? ;-}
On 19 December 2016 at 07:38, Russel Winder wrote:
> On Sun, 2016-12-18 at 23:39 +0100, Cédric Champeau wrote:
> > This looks to be related to the recent changes by Paul for the new
> > release
> > process. Probably an overlook.
>
> I sus
On Sun, 2016-12-18 at 23:39 +0100, Cédric Champeau wrote:
> This looks to be related to the recent changes by Paul for the new
> release
> process. Probably an overlook.
I suspect you meant oversight rather than overlook there.
> Gradle records all Groovy builds, yes. Typically here you could ha
On Sun, 2016-12-18 at 07:51 -0800, John Wagenleitner wrote:
> […]
> This should be fixed now.
It is, thanks.
--
Russel.
=
Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.win...@ekiga.net
41 Buckmaster Road
Thanks John.
Yes, I should have a build-release process for testing later in the
week. The reference to oss.jfrog.org will probably disappear in due
course and point to our own repo.
Cheers, Paul.
On Mon, Dec 19, 2016 at 8:39 AM, Cédric Champeau
wrote:
> This looks to be related to the recent c
This looks to be related to the recent changes by Paul for the new release
process. Probably an overlook.
Gradle records all Groovy builds, yes. Typically here you could have shared
the URL only (and maybe clicked on it since it now shows my face instead of
yours ;)) and it would tell what tasks y
On Sun, Dec 18, 2016 at 6:42 AM, Russel Winder wrote:
> (And Guillaume this is on Debian Sid using OpenJDK8 from the packaging,
> but this is irrelevant to the problem… :-)
>
> BTW are all build recorded by Gradle Inc?
>
>
>
> |> ./gradlew clean
> :buildSrc:compileJava UP-TO-DATE
> :buildSrc:comp
(And Guillaume this is on Debian Sid using OpenJDK8 from the packaging,
but this is irrelevant to the problem… :-)
BTW are all build recorded by Gradle Inc?
|> ./gradlew clean
:buildSrc:compileJava UP-TO-DATE
:buildSrc:compileGroovy UP-TO-DATE
:buildSrc:processResources UP-TO-DATE
:buildSrc:cla
