You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@buildr.apache.org by Antoine Toulme <an...@lunar-ocean.com> on 2016/05/20 06:05:28 UTC
Update on development for 1.5
Hello all,
I got a few things in for 1.5. The changelog reads:
* Change: Update RJB to 1.5.4
* Change: Update rubyzip to 1.2.0
* Change: Update hoe to 3.15.0
* Change: Update net-ssh to 3.1.1
* Change: Update json_pure to 1.8.3
* Change: Update diff-lcs to 1.2.5
* Change: Update xml-simple to 1.1.5
* Change: Update jekyll to 3.1.3
* Change: Update rdoc to 4.2.2
* Added: Travis badge to README.rdoc
* Added: BUILDR-577 Allow remote repo to be added with http basic auth support. Submitted by Michael Guymon.
* Fixed: BUILDR-207 remove 'Skipping tests' messages
* Added: BUILDR-703 release: allow THIS_VERSION to be defined in another file
* Fixed: BUILDR-674 Artifacts with bundle extension cannot be downloaded by Buildr
Additionally, I have started reviewing the issues in jira and as best I could tried to perform some triage. Some issues are old and don’t apply so much and I’ve started closing them. If needed we can reopen issues if they should be looked at again.
I’m still working on the update to Java 8. I have done some of the work to move to Scala 2.11.8. It’s not been easy so far, with a lot of changes in the specs, specs2, scalatest libraries.
Unfortunately, it would be hard to support both 2.11 and the older versions. Is it OK to only support 2.11 and leave older versions with 1.4.25?
I have other things slowly brewing but I’d really like to knock off the old issues and update to Java 8 before anything else happens.
Cheers,
Antoine
Re: Update on development for 1.5
Posted by Antoine Toulme <an...@toulme.name>.
No, there are quite a few places in the code mentioning 1.5.
> On Aug 15, 2016, at 3:49 PM, Alex Boisvert <al...@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 <an...@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 <an...@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 <pe...@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 <pe...@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
>>>
>>
>>
Re: Update on development for 1.5
Posted by Peter Donald <pe...@realityforge.org>.
Hi,
On Tue, Aug 16, 2016 at 8:49 AM, Alex Boisvert <al...@gmail.com> wrote:
> BTW, this is great! Looking forward to 1.5.
Agreed - fantastic work Antoine.
I am currently on a death march project so won't be able to help out
merging custom_pom addon back into core. But I love the work that is
being done.
--
Cheers,
Peter Donald
Re: Update on development for 1.5
Posted by Alex Boisvert <al...@gmail.com>.
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 <an...@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 <an...@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 <pe...@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 <pe...@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
> >
>
>
Re: Update on development for 1.5
Posted by Antoine Toulme <an...@toulme.name>.
Yeah, I’m thinking of generalizing this Spec2Runner and ZincRunner classes into a library that enables Java to run Scala main objects.
> On Aug 16, 2016, at 8:10 AM, Alex Boisvert <al...@gmail.com> wrote:
>
> Ha ha. You can't win the Java game in "hard mode" without dealing with the
> classloader bosses. ;)
>
> On Aug 16, 2016 7:43 AM, "Antoine Toulme" <an...@toulme.name> wrote:
>
>> It took a while to get it right.
>>
>> -I needed a Java wrapper class to call out to the Main object on the
>> compiler. I took after Specs2Runner.
>> -Even then, zinc kept failing missing scala.reflect packages. This was
>> very weird since the classpath definitely contained those classes.
>> I eventually found out that zinc plays with the classloader and takes
>> several arguments: -scala-library, -scala-compiler, and a new one,
>> -scala-extra. (https://github.com/typesafehub/zinc <https://github.com/
>> typesafehub/zinc> gave it away).
>> Adding -scala-extra, pointing at the scala-reflect jar fixed the issue.
>>
>> Cheers,
>>
>> Antoine
>>
>>> On Aug 16, 2016, at 7:20 AM, Alex Boisvert <al...@gmail.com>
>> wrote:
>>>
>>> Nice, thanks for bringing zinc back.
>>>
>>> On Mon, Aug 15, 2016 at 11:38 PM, Antoine Toulme <an...@toulme.name>
>>> wrote:
>>>
>>>> Just brought zinc back in. Had to do a little dancing around with a Java
>>>> class to call out to the Scala main object.
>>>>
>>>> Here is the commit:
>>>>
>>>> [master 749acfe] Bring back zinc compiler, using the latest version and
>> a
>>>> runner class
>>>> 5 files changed, 183 insertions(+), 5 deletions(-)
>>>> create mode 100644 lib/buildr/scala/org/apache/buildr/ZincRunner.class
>>>> create mode 100644 lib/buildr/scala/org/apache/buildr/ZincRunner.java
>>>>
>>>>> On Aug 15, 2016, at 4:49 PM, Antoine Toulme <an...@toulme.name>
>> wrote:
>>>>>
>>>>> On Aug 15, 2016, at 3:47 PM, Alex Boisvert <al...@gmail.com>
>>>> wrote:
>>>>>>
>>>>>> On Mon, Aug 15, 2016 at 3:24 PM, Antoine Toulme <an...@toulme.name>
>>>> wrote:
>>>>>>
>>>>>>> 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.
>>>>>>>
>>>>>>
>>>>>> Zinc's last release was about a month ago (July 3rd); I think you
>> might
>>>>>> have been looking at older artifacts / older organization in maven2
>>>> repo?
>>>>>>
>>>>>> https://github.com/typesafehub/zinc
>>>>>>
>>>>>> No biggie, just mentioning it.
>>>>>
>>>>> OK, I missed it:
>>>>> http://central.maven.org/maven2/com/typesafe/zinc/zinc/0.3.12/ <
>>>> http://central.maven.org/maven2/com/typesafe/zinc/zinc/0.3.12/>
>>>>>
>>>>> OK, let me try to bring this back in.
>>>>>
>>>>> I looked at this new Zinc incarnation from SBT and found that it has a
>>>> first 1.0.0-X1 build out there:
>>>>> http://mvnrepository.com/artifact/org.scala-sbt/zinc_2.11 <
>>>> http://mvnrepository.com/artifact/org.scala-sbt/zinc_2.11>
>>>>>
>>>>> Here is the code:
>>>>> https://github.com/sbt/zinc <https://github.com/sbt/zinc>
>>>>>
>>>>> I tried to use it but could not find the main class like the old one.
>>>>
>>>>
>>
>>
Re: Update on development for 1.5
Posted by Alex Boisvert <al...@gmail.com>.
Ha ha. You can't win the Java game in "hard mode" without dealing with the
classloader bosses. ;)
On Aug 16, 2016 7:43 AM, "Antoine Toulme" <an...@toulme.name> wrote:
> It took a while to get it right.
>
> -I needed a Java wrapper class to call out to the Main object on the
> compiler. I took after Specs2Runner.
> -Even then, zinc kept failing missing scala.reflect packages. This was
> very weird since the classpath definitely contained those classes.
> I eventually found out that zinc plays with the classloader and takes
> several arguments: -scala-library, -scala-compiler, and a new one,
> -scala-extra. (https://github.com/typesafehub/zinc <https://github.com/
> typesafehub/zinc> gave it away).
> Adding -scala-extra, pointing at the scala-reflect jar fixed the issue.
>
> Cheers,
>
> Antoine
>
> > On Aug 16, 2016, at 7:20 AM, Alex Boisvert <al...@gmail.com>
> wrote:
> >
> > Nice, thanks for bringing zinc back.
> >
> > On Mon, Aug 15, 2016 at 11:38 PM, Antoine Toulme <an...@toulme.name>
> > wrote:
> >
> >> Just brought zinc back in. Had to do a little dancing around with a Java
> >> class to call out to the Scala main object.
> >>
> >> Here is the commit:
> >>
> >> [master 749acfe] Bring back zinc compiler, using the latest version and
> a
> >> runner class
> >> 5 files changed, 183 insertions(+), 5 deletions(-)
> >> create mode 100644 lib/buildr/scala/org/apache/buildr/ZincRunner.class
> >> create mode 100644 lib/buildr/scala/org/apache/buildr/ZincRunner.java
> >>
> >>> On Aug 15, 2016, at 4:49 PM, Antoine Toulme <an...@toulme.name>
> wrote:
> >>>
> >>> On Aug 15, 2016, at 3:47 PM, Alex Boisvert <al...@gmail.com>
> >> wrote:
> >>>>
> >>>> On Mon, Aug 15, 2016 at 3:24 PM, Antoine Toulme <an...@toulme.name>
> >> wrote:
> >>>>
> >>>>> 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.
> >>>>>
> >>>>
> >>>> Zinc's last release was about a month ago (July 3rd); I think you
> might
> >>>> have been looking at older artifacts / older organization in maven2
> >> repo?
> >>>>
> >>>> https://github.com/typesafehub/zinc
> >>>>
> >>>> No biggie, just mentioning it.
> >>>
> >>> OK, I missed it:
> >>> http://central.maven.org/maven2/com/typesafe/zinc/zinc/0.3.12/ <
> >> http://central.maven.org/maven2/com/typesafe/zinc/zinc/0.3.12/>
> >>>
> >>> OK, let me try to bring this back in.
> >>>
> >>> I looked at this new Zinc incarnation from SBT and found that it has a
> >> first 1.0.0-X1 build out there:
> >>> http://mvnrepository.com/artifact/org.scala-sbt/zinc_2.11 <
> >> http://mvnrepository.com/artifact/org.scala-sbt/zinc_2.11>
> >>>
> >>> Here is the code:
> >>> https://github.com/sbt/zinc <https://github.com/sbt/zinc>
> >>>
> >>> I tried to use it but could not find the main class like the old one.
> >>
> >>
>
>
Re: Update on development for 1.5
Posted by Antoine Toulme <an...@toulme.name>.
It took a while to get it right.
-I needed a Java wrapper class to call out to the Main object on the compiler. I took after Specs2Runner.
-Even then, zinc kept failing missing scala.reflect packages. This was very weird since the classpath definitely contained those classes.
I eventually found out that zinc plays with the classloader and takes several arguments: -scala-library, -scala-compiler, and a new one, -scala-extra. (https://github.com/typesafehub/zinc <https://github.com/typesafehub/zinc> gave it away).
Adding -scala-extra, pointing at the scala-reflect jar fixed the issue.
Cheers,
Antoine
> On Aug 16, 2016, at 7:20 AM, Alex Boisvert <al...@gmail.com> wrote:
>
> Nice, thanks for bringing zinc back.
>
> On Mon, Aug 15, 2016 at 11:38 PM, Antoine Toulme <an...@toulme.name>
> wrote:
>
>> Just brought zinc back in. Had to do a little dancing around with a Java
>> class to call out to the Scala main object.
>>
>> Here is the commit:
>>
>> [master 749acfe] Bring back zinc compiler, using the latest version and a
>> runner class
>> 5 files changed, 183 insertions(+), 5 deletions(-)
>> create mode 100644 lib/buildr/scala/org/apache/buildr/ZincRunner.class
>> create mode 100644 lib/buildr/scala/org/apache/buildr/ZincRunner.java
>>
>>> On Aug 15, 2016, at 4:49 PM, Antoine Toulme <an...@toulme.name> wrote:
>>>
>>> On Aug 15, 2016, at 3:47 PM, Alex Boisvert <al...@gmail.com>
>> wrote:
>>>>
>>>> On Mon, Aug 15, 2016 at 3:24 PM, Antoine Toulme <an...@toulme.name>
>> wrote:
>>>>
>>>>> 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.
>>>>>
>>>>
>>>> Zinc's last release was about a month ago (July 3rd); I think you might
>>>> have been looking at older artifacts / older organization in maven2
>> repo?
>>>>
>>>> https://github.com/typesafehub/zinc
>>>>
>>>> No biggie, just mentioning it.
>>>
>>> OK, I missed it:
>>> http://central.maven.org/maven2/com/typesafe/zinc/zinc/0.3.12/ <
>> http://central.maven.org/maven2/com/typesafe/zinc/zinc/0.3.12/>
>>>
>>> OK, let me try to bring this back in.
>>>
>>> I looked at this new Zinc incarnation from SBT and found that it has a
>> first 1.0.0-X1 build out there:
>>> http://mvnrepository.com/artifact/org.scala-sbt/zinc_2.11 <
>> http://mvnrepository.com/artifact/org.scala-sbt/zinc_2.11>
>>>
>>> Here is the code:
>>> https://github.com/sbt/zinc <https://github.com/sbt/zinc>
>>>
>>> I tried to use it but could not find the main class like the old one.
>>
>>
Re: Update on development for 1.5
Posted by Alex Boisvert <al...@gmail.com>.
Nice, thanks for bringing zinc back.
On Mon, Aug 15, 2016 at 11:38 PM, Antoine Toulme <an...@toulme.name>
wrote:
> Just brought zinc back in. Had to do a little dancing around with a Java
> class to call out to the Scala main object.
>
> Here is the commit:
>
> [master 749acfe] Bring back zinc compiler, using the latest version and a
> runner class
> 5 files changed, 183 insertions(+), 5 deletions(-)
> create mode 100644 lib/buildr/scala/org/apache/buildr/ZincRunner.class
> create mode 100644 lib/buildr/scala/org/apache/buildr/ZincRunner.java
>
> > On Aug 15, 2016, at 4:49 PM, Antoine Toulme <an...@toulme.name> wrote:
> >
> > On Aug 15, 2016, at 3:47 PM, Alex Boisvert <al...@gmail.com>
> wrote:
> >>
> >> On Mon, Aug 15, 2016 at 3:24 PM, Antoine Toulme <an...@toulme.name>
> wrote:
> >>
> >>> 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.
> >>>
> >>
> >> Zinc's last release was about a month ago (July 3rd); I think you might
> >> have been looking at older artifacts / older organization in maven2
> repo?
> >>
> >> https://github.com/typesafehub/zinc
> >>
> >> No biggie, just mentioning it.
> >
> > OK, I missed it:
> > http://central.maven.org/maven2/com/typesafe/zinc/zinc/0.3.12/ <
> http://central.maven.org/maven2/com/typesafe/zinc/zinc/0.3.12/>
> >
> > OK, let me try to bring this back in.
> >
> > I looked at this new Zinc incarnation from SBT and found that it has a
> first 1.0.0-X1 build out there:
> > http://mvnrepository.com/artifact/org.scala-sbt/zinc_2.11 <
> http://mvnrepository.com/artifact/org.scala-sbt/zinc_2.11>
> >
> > Here is the code:
> > https://github.com/sbt/zinc <https://github.com/sbt/zinc>
> >
> > I tried to use it but could not find the main class like the old one.
>
>
Re: Update on development for 1.5
Posted by Antoine Toulme <an...@toulme.name>.
Just brought zinc back in. Had to do a little dancing around with a Java class to call out to the Scala main object.
Here is the commit:
[master 749acfe] Bring back zinc compiler, using the latest version and a runner class
5 files changed, 183 insertions(+), 5 deletions(-)
create mode 100644 lib/buildr/scala/org/apache/buildr/ZincRunner.class
create mode 100644 lib/buildr/scala/org/apache/buildr/ZincRunner.java
> On Aug 15, 2016, at 4:49 PM, Antoine Toulme <an...@toulme.name> wrote:
>
> On Aug 15, 2016, at 3:47 PM, Alex Boisvert <al...@gmail.com> wrote:
>>
>> On Mon, Aug 15, 2016 at 3:24 PM, Antoine Toulme <an...@toulme.name> wrote:
>>
>>> 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.
>>>
>>
>> Zinc's last release was about a month ago (July 3rd); I think you might
>> have been looking at older artifacts / older organization in maven2 repo?
>>
>> https://github.com/typesafehub/zinc
>>
>> No biggie, just mentioning it.
>
> OK, I missed it:
> http://central.maven.org/maven2/com/typesafe/zinc/zinc/0.3.12/ <http://central.maven.org/maven2/com/typesafe/zinc/zinc/0.3.12/>
>
> OK, let me try to bring this back in.
>
> I looked at this new Zinc incarnation from SBT and found that it has a first 1.0.0-X1 build out there:
> http://mvnrepository.com/artifact/org.scala-sbt/zinc_2.11 <http://mvnrepository.com/artifact/org.scala-sbt/zinc_2.11>
>
> Here is the code:
> https://github.com/sbt/zinc <https://github.com/sbt/zinc>
>
> I tried to use it but could not find the main class like the old one.
Re: Update on development for 1.5
Posted by Antoine Toulme <an...@toulme.name>.
On Aug 15, 2016, at 3:47 PM, Alex Boisvert <al...@gmail.com> wrote:
>
> On Mon, Aug 15, 2016 at 3:24 PM, Antoine Toulme <an...@toulme.name> wrote:
>
>> 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.
>>
>
> Zinc's last release was about a month ago (July 3rd); I think you might
> have been looking at older artifacts / older organization in maven2 repo?
>
> https://github.com/typesafehub/zinc
>
> No biggie, just mentioning it.
OK, I missed it:
http://central.maven.org/maven2/com/typesafe/zinc/zinc/0.3.12/ <http://central.maven.org/maven2/com/typesafe/zinc/zinc/0.3.12/>
OK, let me try to bring this back in.
I looked at this new Zinc incarnation from SBT and found that it has a first 1.0.0-X1 build out there:
http://mvnrepository.com/artifact/org.scala-sbt/zinc_2.11 <http://mvnrepository.com/artifact/org.scala-sbt/zinc_2.11>
Here is the code:
https://github.com/sbt/zinc <https://github.com/sbt/zinc>
I tried to use it but could not find the main class like the old one.
Re: Update on development for 1.5
Posted by Alex Boisvert <al...@gmail.com>.
On Mon, Aug 15, 2016 at 3:24 PM, Antoine Toulme <an...@toulme.name> wrote:
> 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.
>
Zinc's last release was about a month ago (July 3rd); I think you might
have been looking at older artifacts / older organization in maven2 repo?
https://github.com/typesafehub/zinc
No biggie, just mentioning it.
Re: Update on development for 1.5
Posted by Antoine Toulme <an...@toulme.name>.
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 <an...@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 <pe...@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 <pe...@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
>
Re: Update on development for 1.5
Posted by Antoine Toulme <an...@toulme.name>.
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 <pe...@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 <pe...@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
Re: Update on development for 1.5
Posted by Peter Donald <pe...@realityforge.org>.
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 <pe...@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
Re: Update on development for 1.5
Posted by Peter Donald <pe...@realityforge.org>.
On Fri, May 20, 2016 at 4:05 PM, Antoine Toulme <an...@lunar-ocean.com> wrote:
> I got a few things in for 1.5. The changelog reads:
Excellent work.
> Additionally, I have started reviewing the issues in jira and as best I could tried to perform some triage. Some issues are old and don’t apply so much and I’ve started closing them. If needed we can reopen issues if they should be looked at again.
Sounds good.
> I have other things slowly brewing but I’d really like to knock off the old issues and update to Java 8 before anything else happens.
The one thing I would like to see and are willing to do the work for
is moving 'buildr/custom_pom' addon back into the core. I would
ideally like to be generating useful poms with correctly defined poms
for consumption in other build systems. Besides adding a truckload of
tests the only other thing that I think would be useful to add is the
ability to specify "provided" scoped dependencies. I am not really
sure about how to go about this.
I had thought of adding something like
compile.provides << :mydependency
This would be equivalent to
project.compile.with :mydependency
project.pom.provided_dependencies << :mydependency
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.
Thoughts?
--
Cheers,
Peter Donald