On Thu, Jun 05, 2014 at 10:46:42AM +0300, Eugene Zhukov wrote:
> Hi Miguel,
>
> Did you have a chance to look into 1.8 version packaging I pushed to a
> separate branch?
Hi Eugene,
Unfortunately I hadn't manage to find time to review the package but
I intend to do it soon.
I think I can review
On Fri, May 16, 2014 at 3:29 AM, Miguel Landaeta wrote:
> On Thu, May 15, 2014 at 11:23:41AM +0300, Eugene Zhukov wrote:
>>
>> I've been working on upgrading this package to 1.8, but now stuck with
>> 'compileGroovy.groovyClasspath' must not be empty. Would anyone be
>> interested to help? I can p
On 28.5.2014, at 14.50, Emmanuel Bourg wrote:
>
> Le 15/05/2014 10:23, Eugene Zhukov a écrit :
>
>> I've been working on upgrading this package to 1.8, but now stuck with
>> 'compileGroovy.groovyClasspath' must not be empty. Would anyone be
>> interested to help? I can push my changes I've done
Le 15/05/2014 10:23, Eugene Zhukov a écrit :
> I've been working on upgrading this package to 1.8, but now stuck with
> 'compileGroovy.groovyClasspath' must not be empty. Would anyone be
> interested to help? I can push my changes I've done so far.
Hi Eugene,
Did you try packaging gradle 1.6 ins
On Fri, May 16, 2014 at 3:29 AM, Miguel Landaeta wrote:
> On Thu, May 15, 2014 at 11:23:41AM +0300, Eugene Zhukov wrote:
>>
>> I've been working on upgrading this package to 1.8, but now stuck with
>> 'compileGroovy.groovyClasspath' must not be empty. Would anyone be
>> interested to help? I can p
On Thu, May 15, 2014 at 11:23:41AM +0300, Eugene Zhukov wrote:
>
> I've been working on upgrading this package to 1.8, but now stuck with
> 'compileGroovy.groovyClasspath' must not be empty. Would anyone be
> interested to help? I can push my changes I've done so far.
Just push it to the repo in a
On Thu, May 15, 2014 at 10:03:32AM +0200, Emmanuel Bourg wrote:
> Le 15/05/2014 02:51, Miguel Landaeta a écrit :
>
> > On top of your changes I fixed an outstanding bug and a lintian
> > warning.
>
> Do you it's worth upgrading further this package considering that gradle
> 2 is going to be packa
Hi,
On Thu, May 15, 2014 at 11:03 AM, Emmanuel Bourg wrote:
> Le 15/05/2014 02:51, Miguel Landaeta a écrit :
>
>> On top of your changes I fixed an outstanding bug and a lintian
>> warning.
>
> Thank you Miguel.
>
> Do you it's worth upgrading further this package considering that gradle
> 2 is g
Le 15/05/2014 02:51, Miguel Landaeta a écrit :
> On top of your changes I fixed an outstanding bug and a lintian
> warning.
Thank you Miguel.
Do you it's worth upgrading further this package considering that gradle
2 is going to be packaged separately?
Emmanuel bourg
--
To UNSUBSCRIBE, emai
On Mon, May 12, 2014 at 11:59:05AM -0300, Miguel Landaeta wrote:
>
> Thank you for taking care of gradle.
> I'll sponsor this.
On top of your changes I fixed an outstanding bug and a lintian
warning.
Thanks for helping to maintain this package.
--
Miguel Landaeta, nomadium at debian.org
secure
On Mon, May 12, 2014 at 01:34:57PM +0200, Emmanuel Bourg wrote:
> Hi all,
>
> I upgraded gradle to the version 1.5 and I'm looking for a sponsor to
> upload it. This update also fixes a compilation issue with Java 8. I was
> able to rebuild gradle itself and multiverse-core with this new version.
Hi all,
I upgraded gradle to the version 1.5 and I'm looking for a sponsor to
upload it. This update also fixes a compilation issue with Java 8. I was
able to rebuild gradle itself and multiverse-core with this new version.
Here is the changelog:
* New upstream release
- Added a build depe
12 matches
Mail list logo
