buildr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Antoine Toulme <anto...@toulme.name>
Subject Re: Update on development for 1.5
Date Mon, 15 Aug 2016 23:51:25 GMT
No, there are quite a few places in the code mentioning 1.5. 

> On Aug 15, 2016, at 3:49 PM, Alex Boisvert <alex.boisvert@gmail.com> wrote:
> 
> BTW, this is great!  Looking forward to 1.5.
> 
> Has anybody looked at deprecations?  We could remove anything that's been
> marked as deprecated in 1.3.x and before.
> 
> https://cwiki.apache.org/confluence/display/BUILDR/Backward+Compatibility
> 
> 
> On Mon, Aug 15, 2016 at 3:24 PM, Antoine Toulme <antoine@toulme.name> wrote:
> 
>> OK,
>> 
>> we now have support for Scala 2.11.
>> 
>> Two things had to go to make it happen:
>> -the Zinc compiler’s last release was 6 years ago, and it doesn’t seem to
>> play well with the latest. I have removed it.
>> -specs vs specs2. specs would not work with 2.11. I have removed it.
>> 
>> Also, as a bonus we now run our test suite on JDK8. Happy to report all
>> tests pass and we have a great streak of green builds:
>> https://travis-ci.org/apache/buildr/builds <https://travis-ci.org/apache/
>> buildr/builds>
>> 
>> We’re down to 8 issues for 1.5, 4 of them major ones.
>> 
>> Cheers,
>> 
>> Antoine
>> 
>>> On Aug 14, 2016, at 12:41 AM, Antoine Toulme <antoine@toulme.name>
>> wrote:
>>> 
>>> Cool, thanks!
>>> 
>>> Further updates on development.
>>> 
>>> We have 6 major issues remaining on the 1.5 roadmap.
>>> Still no progress on the Scala 2.11 upgrade, because I’m lazy.
>>> 
>>> Cheers,
>>> 
>>> Antoine
>>> 
>>>> On May 22, 2016, at 3:47 AM, Peter Donald <peter@realityforge.org>
>> wrote:
>>>> 
>>>> Actually went and updated custom_pom to do this as this shouuld be done
>> anyway.
>>>> 
>>>> On Sun, May 22, 2016 at 8:02 PM, Peter Donald <peter@realityforge.org>
>> wrote:
>>>>> We may also need to change the way we output dependencies from
>>>>> 
>>>>> <dependency>
>>>>>  <groupId>com.biz</groupId>
>>>>>  <artifactId>app</artifactId>
>>>>>  <version>1.0</version>
>>>>> </dependency>
>>>>> 
>>>>> to
>>>>> 
>>>>> <dependency>
>>>>>  <groupId>com.biz</groupId>
>>>>>  <artifactId>app</artifactId>
>>>>>  <version>1.0</version>
>>>>>  <exclusions>
>>>>>      <exclusion>
>>>>>          <groupId>*</groupId>
>>>>>          <artifactId>*</artifactId>
>>>>>      </exclusion>
>>>>>  </exclusions>
>>>>> </dependency>
>>>>> 
>>>>> As Maven assumes transitive dependencies and buildr assumes no
>>>>> transitive dependencies.
>>>> 
>>>> 
>>>> --
>>>> Cheers,
>>>> 
>>>> Peter Donald
>>> 
>> 
>> 


Mime
View raw message