Re: Retirement discussion

2022-07-07 Thread Antoine Toulme
Folks, an update - we have taken a vote as the PMC and decided to retire Buildr.
I have added the retirement of Buildr as an item for the next board meeting.

Thank you!

Antoine

> On May 11, 2022, at 12:14 AM, Antoine Toulme  wrote:
> 
> Folks,
> 
> I have prepared the report for the board meeting here:
> https://cwiki.apache.org/confluence/display/BUILDR/May+2022+Board+Report 
> <https://cwiki.apache.org/confluence/display/BUILDR/May+2022+Board+Report>
> 
> We are talking about retiring this project. If you would like to see it 
> continue in its current form, please chime in!
> 
> Cheers!
> 
> Antoine



Retirement discussion

2022-05-11 Thread Antoine Toulme
Folks,

I have prepared the report for the board meeting here:
https://cwiki.apache.org/confluence/display/BUILDR/May+2022+Board+Report 


We are talking about retiring this project. If you would like to see it 
continue in its current form, please chime in!

Cheers!

Antoine

February 2022 report

2022-01-31 Thread Antoine Toulme
Hey folks,

I have prepared the report for February 2022:

https://cwiki.apache.org/confluence/display/BUILDR/February+2022+Board+Report 


Please review and edit, I will file it to the board next week.

Cheers,

Antoine

Re: August board report draft

2021-08-07 Thread Antoine Toulme
It has been posted now. Thanks all!

> On Aug 2, 2021, at 1:43 PM, Antoine Toulme  wrote:
> 
> Hey everyone,
> 
> This is the draft for the board report of August 2021: 
> https://cwiki.apache.org/confluence/display/BUILDR/August+2021+Board+Report 
> <https://cwiki.apache.org/confluence/display/BUILDR/August+2021+Board+Report>
> 
> It’s the same word for word as May 2021. Please review and edit at will :)
> 
> Cheers,
> 
> Antoine



August board report draft

2021-08-02 Thread Antoine Toulme
Hey everyone,

This is the draft for the board report of August 2021: 
https://cwiki.apache.org/confluence/display/BUILDR/August+2021+Board+Report 


It’s the same word for word as May 2021. Please review and edit at will :)

Cheers,

Antoine

May 2021 board report

2021-05-01 Thread Antoine Toulme
Hello everyone,

Please review this draft of the board report here:
https://cwiki.apache.org/confluence/display/BUILDR/May+2021+Board+Report 


Cheers,

Antoine

Re: February 2021 board report

2021-02-05 Thread Antoine Toulme
OK, I’ll submit it now so I don’t forget, we can edit it if needed.

> On Feb 5, 2021, at 11:23 AM, Alex Boisvert  wrote:
> 
> Thanks Antoine.  Yeah, no news to report on...
> 
> On Fri, Feb 5, 2021 at 9:28 AM Antoine Toulme  wrote:
> 
>> Hello folks,
>> 
>> Please see here the draft of the Feb 2021 board report.
>> 
>> 
>> https://cwiki.apache.org/confluence/display/BUILDR/February+2021+Board+Report
>> <
>> https://cwiki.apache.org/confluence/display/BUILDR/February+2021+Board+Report
>>> 
>> 
>> It is exactly the same as the report from November, as we didn’t really
>> have much development recently. Please feel free to update.
>> 
>> Cheers,
>> 
>> Antoine



February 2021 board report

2021-02-05 Thread Antoine Toulme
Hello folks,

Please see here the draft of the Feb 2021 board report.

https://cwiki.apache.org/confluence/display/BUILDR/February+2021+Board+Report 


It is exactly the same as the report from November, as we didn’t really have 
much development recently. Please feel free to update.

Cheers,

Antoine

Buildr board report

2020-11-02 Thread Antoine Toulme
Here is a draft of the board report for November:

https://cwiki.apache.org/confluence/display/BUILDR/November+2020+Board+Report 


Please let me know if it looks good and I’ll drop it in!

Cheers,

Antoine

August board report

2020-08-05 Thread Antoine Toulme
Hello all,

I have prepared the board report for August. No activity - so very simple 
report, same as May.

https://cwiki.apache.org/confluence/display/BUILDR/August+2020+Board+Report 


Please review and edit at will!

Cheers,

Antoine

May board report

2020-05-01 Thread Antoine Toulme
Hey everyone,

I hope you’re all keeping safe. I have prepared the board report for May 2020:
https://cwiki.apache.org/confluence/display/BUILDR/May+2020+Board+Report 


Cheers,

Antoine 

Feb 2020 board report

2020-01-29 Thread Antoine Toulme
Hello folks,

I drafted the report for Feb 2020 here:

https://cwiki.apache.org/confluence/display/BUILDR/February+2020+Board+Report 


Please review and edit at will!

Antoine

August board report

2019-08-06 Thread Antoine Toulme
Hey everybody,

I prepared the board report for August:
https://cwiki.apache.org/confluence/display/BUILDR/August+2019+Board+Report 


Please take a look and edit as needed. I will submit the board report in a week 
from now.

Cheers,

Antoine

Fixing CI

2019-07-14 Thread Antoine Toulme
Looks like Travis is in the red. Anybody looking to fix CI? Please coordinate 
on this thread.



Re: [VOTE] Buildr 1.5.8 release

2019-07-14 Thread Antoine Toulme
+1 from me as well. Good job!

> On Jul 14, 2019, at 04:20, Peter Donald  wrote:
> 
> +1 from me
> 
>> On Sun, Jul 14, 2019 at 9:18 PM Peter Donald  wrote:
>> 
>> We're voting on the source distributions available here:
>> https://dist.apache.org/repos/dist/dev/buildr/1.5.8/dist/
>> 
>> Specifically:
>> https://dist.apache.org/repos/dist/dev/buildr/1.5.8/dist/buildr-1.5.8.tgz
>> https://dist.apache.org/repos/dist/dev/buildr/1.5.8/dist/buildr-1.5.8.zip
>> 
>> The documentation generated for this release is available here:
>> https://dist.apache.org/repos/dist/dev/buildr/1.5.8/site/
>> https://dist.apache.org/repos/dist/dev/buildr/1.5.8/site/buildr.pdf
>> 
>> The following changes were made since 1.5.7:
>> 
>>  * Fixed:  Changed references to `https://repo1.maven.org/maven2`
>>  to use https where possible.
>>  * Change: Use the `zapwhite` gem to manage file whitespace within
>> repository.
>>  * Fixed:  Replace references to long removed `
>> http://www.ibiblio.org/maven2/` 
>> repository with
>>`https://repo1.maven.org/maven2`
>> .
>>  * Fixed:  Ensure pom files used in tests use https when referring to
>> maven repositories.
>>  * Added:  Add support for downloading external annotations and attaching
>> them to IntelliJ IDEA module dependencies.
>>  * Added:  Detect external annotations in the local project and add them
>> to the generated IntelliJ IDEA
>>module when generating. The default location is
>> `src/main/annotations` but other locations
>>can be specified by modifying the
>> `project.iml.annotation_paths` property.
>>  * Fixed:  Explicitly specify the `:sourcepath` parameter for javadoc
>> tool. This enables additional parameters
>>such as `-packagenames` and `-subpackages` to be passed to the
>> underling tool.
>>  * Fixed:  Stop generating poms with the parent POM
>> `org.sonatype.oss:oss-parent:8`. The las update was a long time
>>ago (i.e. 2012) and it is no longer maintained. It was also
>> deprecated several years ago and is not
>>guaranteed to work in modern Maven deployments.
>> 
>> 
> 
> -- 
> Cheers,
> 
> Peter Donald



May board report

2019-04-28 Thread Antoine Toulme
Hello folks,

Here is the board report for May 2019. Please review and comment:

https://cwiki.apache.org/confluence/display/BUILDR/May+2019+Board+Report 


Cheers,

Antoine

Re: [VOTE] Buildr 1.5.7 release

2019-02-15 Thread Antoine Toulme
+1 from me. Thanks Peter for cutting the release!

> On Feb 15, 2019, at 6:54 PM, Peter Donald  wrote:
> 
> We're voting on the source distributions available here:
> https://dist.apache.org/repos/dist/dev/buildr/1.5.7/dist/
> 
> Specifically:
> https://dist.apache.org/repos/dist/dev/buildr/1.5.7/dist/buildr-1.5.7.tgz
> https://dist.apache.org/repos/dist/dev/buildr/1.5.7/dist/buildr-1.5.7.zip
> 
> The documentation generated for this release is available here:
> https://dist.apache.org/repos/dist/dev/buildr/1.5.7/site/
> https://dist.apache.org/repos/dist/dev/buildr/1.5.7/site/buildr.pdf
> 
> The following changes were made since 1.5.6:
> 
>  * Fixed:  The fix that allowed special characters in usernames and
> passwords was only partially applied
>in the `1.5.6` release. The complete fix that correctly decoded
> usernames and passwords before
>passing them to HTTP library is now been applied.
>  * Change: GWT Addon: Added support for `:skip_merge_gwt_dependencies`
> parameter that makes it possible to
>avoid adding GWT dependencies to the project directly and thus
> the associated POM. This will be
>required to support GWT3.x and GWT2.x simultaneously as well as
> making it easier to manage
>dependencies in the POMs.
>  * Change: Javadoc: If the user does not supply an explicit `:sourcepath`
> to the doc/javadoc tool then
>default the value to `project.compile.sources`. This will stop
> javadoc from scanning the classpath
>for `*.java` files which can cause issues with projects that
> include `sources` classifier artifacts
>on the classpath. This is particularly relevant for GWT based
> projects that include artifacts with
>source embedded in the artifacts. This change also made it
> possible to remove an ugly hack in the
>GWT addon that removed the gwt artifacts from the javadoc path.
>  * Change: Drop deprecated Gem::Specification#has_rdoc= (no replacement)
> method. Submitted by Olle Jonsson.
>  * Change: Use https protocol to access Gem metadata. Submitted by Olle
> Jonsson.
>  * Change: Change RSpec shared_context usage to avoid warnings. Submitted
> by Olle Jonsson.
>  * Change: Migrated source control to Apache GitBox which supports using
> either GitHub or GitBox as the
>master repository.
> -- 
> Cheers,
> 
> Peter Donald



Re: Buildr board report for February 2019

2019-02-14 Thread Antoine Toulme
You’re the man Peter. OK I’ll post it out.

> On Feb 14, 2019, at 3:44 PM, Peter Donald  wrote:
> 
> Looks good ... although that reminds me we should probably put together a
> release just packaging the existing changes. I will try to kick it off
> tomorrow.
> 
> On Thu, Feb 14, 2019 at 11:55 AM Antoine Toulme  wrote:
> 
>> Hello all,
>> 
>> I have started notes on the Buildr board report for Feb 2019.
>> 
>> Please take a look and contribute to the report if you see anything
>> missing/incorrect:
>> 
>> 
>> https://cwiki.apache.org/confluence/display/BUILDR/February+2019+Board+Report
>> 
>> Cheers,
>> 
>> Antoine
> 
> 
> 
> -- 
> Cheers,
> 
> Peter Donald



Buildr board report for February 2019

2019-02-13 Thread Antoine Toulme
Hello all,

I have started notes on the Buildr board report for Feb 2019.

Please take a look and contribute to the report if you see anything 
missing/incorrect:

https://cwiki.apache.org/confluence/display/BUILDR/February+2019+Board+Report

Cheers,

Antoine

Re: [Vote] Move to using GitBox/GitHub as our git repository

2018-12-12 Thread Antoine Toulme
+1

> On Dec 12, 2018, at 15:12, Peter Donald  wrote:
> 
> +1 from me
> 
> On Thu, Dec 13, 2018 at 10:12 AM Peter Donald 
> wrote:
> 
>> Hi,
>> 
>> It looks like Apache is moving all the git repositories to GitBox over the
>> next few months. This will mean we will be able to directly use the GitHub
>> interface (See https://reference.apache.org/committer/github for
>> requirements) if you so desire. Apparently it takes between a minute and an
>> hour to actually make the switch.
>> 
>> This vote is to try and put us in the first batch of repositories that
>> move (December 9th 2018 -> January 9th 2019) rather than wait for forced
>> mass migration (February 7th).
>> 
>> All in favour?
>> 
>> --
>> Cheers,
>> 
>> Peter Donald
>> 
> 
> 
> -- 
> Cheers,
> 
> Peter Donald



August 2018 board report

2018-08-08 Thread Antoine Toulme
Hey folks,

I have pushed out the latest board report for Buildr, here it is:
https://cwiki.apache.org/confluence/display/BUILDR/August+2018+Board+Report 


Cheers,

Antoine

Stack Overflow reporting issue on pom generation

2018-06-12 Thread Antoine Toulme
I have asked the reporter if they could give a reproducible test case. It 
should be possible to reproduce based on their instructions.

https://stackoverflow.com/questions/50814835/buildr-wont-generate-a-pom-in-projects-with-multiple-packages

Cheers,

Antoine

Re: [VOTE] Buildr 1.5.6 release

2018-05-12 Thread Antoine Toulme
+1
Thanks for cutting the release Peter!

> On May 12, 2018, at 04:30, Alex Boisvert  wrote:
> 
> +1 (no testing done)
> 
>> On Sat, May 12, 2018, 4:14 AM Peter Donald  wrote:
>> 
>> +1 from me.
>> 
>> Tested several different builds in different environments and all seem to
>> work.
>> 
>> On Thu, May 10, 2018 at 9:53 AM, Peter Donald 
>> wrote:
>> 
>>> 
>>> We're voting on the source distributions available here:
>>> 
>>> https://dist.apache.org/repos/dist/dev/buildr/1.5.6/dist/
>>> 
>>> 
>>> Specifically:
>>> 
>>> 
>> https://dist.apache.org/repos/dist/dev/buildr/1.5.6/dist/buildr-1.5.6.tgz
>>> 
>>> 
>> https://dist.apache.org/repos/dist/dev/buildr/1.5.6/dist/buildr-1.5.6.zip
>>> 
>>> 
>>> The documentation generated for this release is available here:
>>> 
>>> https://dist.apache.org/repos/dist/dev/buildr/1.5.6/site/
>>> 
>>> https://dist.apache.org/repos/dist/dev/buildr/1.5.6/site/buildr.pdf
>>> 
>>> 
>>> The following changes were made since 1.5.5:
>>> 
>>> 
>>>  * Fixed:  Ensure that the username and passwords declared for
>>> repositories are correctly url encoded for
>>> 
>>>the upload repositories when converted to a URL. (i.e. Ensure
>>> `Buildr.repositories.release_to`
>>> 
>>>and `Buildr.repositories.snapshot_to` settings can have
>>> usernames and passwords with special
>>> 
>>>characters).
>>> 
>>>  * Added:  Add support for allowing some dependencies to include
>>> transitive dependencies via the
>>> 
>>>`pom.include_transitive_dependencies` configuration setting.
>>> 
>>>  * Added:  Add support for adding dependencies to the pom via the
>>> `pom.additional_dependencies` configuration
>>> 
>>>setting. These dependencies are `compile` scope and are in
>>> addition to any derived from the normal
>>> 
>>>compile dependencies.
>>> 
>>>  * Fixed:  GWT Addon: Use version `1.0.2` of the
>>> `com.google.jsinterop:jsinterop-annotations:jar` artifact
>>> 
>>>when using GWT 2.8.2 to align with version shipped with GWT.
>>> 
>>>  * Fixed:  Dependencies added as `pom.provided_dependencies` or
>>> `pom.runtime_dependencies` and not included
>>> 
>>>as compile dependencies were incorrectly omitted from pom.
>>> 
>>>  * Fixed:  Dependencies added as `pom.provided_dependencies` and
>>> `pom.runtime_dependencies` were being
>>> 
>>>incorrectly duplicated within the pom dependencies section.
>>> Now provided dependency scope takes
>>> 
>>>precedence over runtime scoped dependency.
>>> 
>>>  * Fixed:  Dependencies added to POMs will specify the classifier unless
>>> it is the default value.
>>> 
>>>  * Added:  Add the `project.pom.dependency_filter` configuration
>>> property that can be set to a proc. The proc
>>> 
>>>accepts a dependency and returns a boolean that determines
>>> whether the dependency is included in
>>> 
>>>the generated pom or not.
>>> 
>>>  * Fixed:  POMs generated by Buildr use the parent pom
>>> `org.sonatype.oss:oss-parent:pom:7` but this
>>> 
>>>generates a warning in the latest version of Maven. Modern
>>> versions of Maven would thus
>>> 
>>>ignore transitive dependencies declared in the pom. The
>>> parent pom has now been upgraded
>>> 
>>>to `org.sonatype.oss:oss-parent:pom:8` which will result in
>>> modern Maven correctly picking
>>> 
>>>up transitive dependencies.
>>> 
>>>  * Change: JaCoCo Addon: Update JaCoCo version to 0.8.0 which in turns
>>> supports Java9.
>>> 
>>>  * Added:  GWT Addon: Added support for `:gwtc_args` parameter to supply
>>> arbitrary parameters to
>>> 
>>>the GWT compiler.
>>> 
>>>  * Added:  Add support for sha512 digests to be generated for files
>>> during the upload. This is typically
>>> 
>>>configured by adding `sha512` to the list of digests via a
>>> line such as:
>>> 
>>>`repositories.release_to[:options] = {:digests => [:md5,
>>> :sha1, :sha512]}`
>>> 
>>>  * Fixed:  The default upload tasks would often get a ReadTimeout when
>>> uploading using http to a remote
>>> 
>>>server that did not have `KeepAlive` socket option enabled
>>> and the upload took more than 60
>>> 
>>>seconds (the default socket read timeout). Some commercial
>>> maven repositories could trigger
>>> 
>>>this scenario during upload of even modest size artifacts.
>>> Default the read_timeout to 10 minutes
>>> 
>>>when during upload to work address this issue.
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> --
>>> Cheers,
>>> 
>>> Peter Donald
>>> 
>> 
>> 
>> 
>> --
>> Cheers,
>> 
>> Peter Donald
>> 


Re: 1.5.6 ?

2018-05-09 Thread Antoine Toulme
\m/ !

> On May 9, 2018, at 4:51 PM, Peter Donald <pe...@realityforge.org> wrote:
> 
> I had a few minutes so I staged a release. Off to test it now ...
> 
> On Sat, May 5, 2018 at 9:55 PM, Peter Donald <pe...@realityforge.org> wrote:
> 
>> Hi,
>> 
>> On Sat, May 5, 2018 at 12:29 PM, Antoine Toulme <anto...@toulme.name>
>> wrote:
>>> Looks like we have a few good changes in the CHANGELOG.
>>> 
>>> Would a new release makes sense? I’d be happy to help drive it.
>> 
>> Sounds like a plan. I can run it through a few different MRI versions
>> to test although we no longer have any jruby based builds anymore.
>> 
>> --
>> Cheers,
>> 
>> Peter Donald
>> 
> 
> 
> 
> -- 
> Cheers,
> 
> Peter Donald



1.5.6 ?

2018-05-04 Thread Antoine Toulme
Looks like we have a few good changes in the CHANGELOG.

Would a new release makes sense? I’d be happy to help drive it.

Cheers,

Antoine

May 2018 board report

2018-05-04 Thread Antoine Toulme
Hi folks!

It’s time for our next board report. Please review and edit this page at will:
https://cwiki.apache.org/confluence/display/BUILDR/May+2018+Board+Report 


Cheers,

Antoine

Re: Report for Feb

2018-02-20 Thread Antoine Toulme
Allright, I have updated the report and am shipping it.

> On Feb 12, 2018, at 10:59 AM, Antoine Toulme <anto...@toulme.name> wrote:
> 
> Hey folks,
> 
> Please help fill the report for the board this month.
> 
> https://cwiki.apache.org/confluence/display/BUILDR/February+2018+Board+Report 
> <https://cwiki.apache.org/confluence/display/BUILDR/February+2018+Board+Report>
> 
> There are a few sections that are new to the format and are filled with TODOs 
> related to the lack of activity on the project.
> 
> I’ll write my thoughts on the report tomorrow but would like volunteers to 
> get a first go at it.
> 
> Cheers,
> 
> Antoine



Report for Feb

2018-02-12 Thread Antoine Toulme
Hey folks,

Please help fill the report for the board this month.

https://cwiki.apache.org/confluence/display/BUILDR/February+2018+Board+Report 


There are a few sections that are new to the format and are filled with TODOs 
related to the lack of activity on the project.

I’ll write my thoughts on the report tomorrow but would like volunteers to get 
a first go at it.

Cheers,

Antoine

Re: [ANNOUNCE] Apache Buildr 1.5.5 released

2017-12-15 Thread Antoine Toulme
Congrats!

Great to have more IDEA support.

> On Dec 15, 2017, at 21:35, Peter Donald <pe...@realityforge.org> wrote:
> 
> No problems.
> 
> I also have a whole sequence of changes around IDEA project building
> that are almost ready to release. I just need to get around to
> releasing it.
> 
> However having a 10 day old baby is proving to be quite the distraction atm ;)
> 
>> On Thu, Dec 14, 2017 at 8:53 AM, Antoine Toulme <anto...@toulme.name> wrote:
>> Congrats on the release Peter, great job pushing those changes through!
>> 
>>> On Dec 13, 2017, at 13:28, Peter Donald <pe...@realityforge.org> wrote:
>>> 
>>> Apache Buildr is a build system for Java-based applications, including 
>>> support
>>> for Scala, Groovy and a growing number of JVM languages and tools.  We 
>>> wanted
>>> something that's simple and intuitive to use, so we only need to tell it 
>>> what
>>> to do, and it takes care of the rest.  But also something we can easily 
>>> extend
>>> for those one-off tasks, with a language that's a joy to use.
>>> 
>>> 
>>> New in this release:
>>> 
>>> * Fixed:  The concatenation extension released as part of 1.5.4
>>> changed the way zip archives were
>>>   constructed so that entries for some intermediate
>>> directories were elided. For most consumers
>>>   of zip files this had no impact but some tools require the
>>> entries during scanning. (i.e. Older
>>>   versions of Jruby that loaded ruby scripts from within a jar).
>>> * Added:  IDEA Extension: Added support for passing `:iml_name`
>>> parameter to `ipr.add_gwt_configuration`
>>> 
>>> 
>>> To learn more about Buildr and get started:
>>> http://buildr.apache.org/
>>> 
>>> Thanks!
>>> The Apache Buildr Team
>> 
> 
> 
> 
> -- 
> Cheers,
> 
> Peter Donald



Re: [ANNOUNCE] Apache Buildr 1.5.5 released

2017-12-13 Thread Antoine Toulme
Congrats on the release Peter, great job pushing those changes through!

> On Dec 13, 2017, at 13:28, Peter Donald  wrote:
> 
> Apache Buildr is a build system for Java-based applications, including support
> for Scala, Groovy and a growing number of JVM languages and tools.  We wanted
> something that's simple and intuitive to use, so we only need to tell it what
> to do, and it takes care of the rest.  But also something we can easily extend
> for those one-off tasks, with a language that's a joy to use.
> 
> 
> New in this release:
> 
>  * Fixed:  The concatenation extension released as part of 1.5.4
> changed the way zip archives were
>constructed so that entries for some intermediate
> directories were elided. For most consumers
>of zip files this had no impact but some tools require the
> entries during scanning. (i.e. Older
>versions of Jruby that loaded ruby scripts from within a jar).
>  * Added:  IDEA Extension: Added support for passing `:iml_name`
> parameter to `ipr.add_gwt_configuration`
> 
> 
> To learn more about Buildr and get started:
> http://buildr.apache.org/
> 
> Thanks!
> The Apache Buildr Team



Re: [VOTE] Buildr 1.5.5 release

2017-12-05 Thread Antoine Toulme
+1 here too.

> On Dec 5, 2017, at 2:34 PM, Peter Donald  wrote:
> 
> +1 from me.
> 
> The goal of the release is just to fix that one bug that slipped through.
> 
> -- 
> Cheers,
> 
> Peter Donald



Re: [VOTE] Buildr 1.5.4 release

2017-11-29 Thread Antoine Toulme
Thank you! My +1 as well.

> On Nov 28, 2017, at 21:29, Peter Donald  wrote:
> 
> I had some time to do some testing of the latest version so I pushed out
> the release. Hope that is all good.
> 
> Anyhoo - I tested with several different  builds and are +1
> 
> On Wed, Nov 29, 2017 at 4:28 PM, Peter Donald 
> wrote:
> 
>> We're voting on the source distributions available here:
>> https://dist.apache.org/repos/dist/dev/buildr/1.5.4/dist/
>> 
>> Specifically:
>> https://dist.apache.org/repos/dist/dev/buildr/1.5.4/dist/buildr-1.5.4.tgz
>> https://dist.apache.org/repos/dist/dev/buildr/1.5.4/dist/buildr-1.5.4.zip
>> 
>> The documentation generated for this release is available here:
>> https://dist.apache.org/repos/dist/dev/buildr/1.5.4/site/
>> https://dist.apache.org/repos/dist/dev/buildr/1.5.4/site/buildr.pdf
>> 
>> The following changes were made since 1.5.3:
>> 
>>  * Added:  Findbugs Addon: Upgrade to version 3.0.1 of findbugs.
>>  * Added:  GPG Addon: Add boolean configuration setting `project.gpg`
>> that can be set to false via
>>`project.gpg = false` to avoid signing and uploading packages.
>> This is useful when some
>>projects are not intended for publishing.
>>  * Fixed:  JaCoCo Addon: Projects that have jacoco disabled will no
>> longer appear in the JaCoCo reports.
>>  * Change: JaCoCo Addon: Update JaCoCo version to 0.7.9.
>>  * Fixed:  BUILDR-733 - Escape classpath entries in the pathing jar
>> manifest. Submitted by Glenn Croes.
>>  * Fixed:  Ensure that the pom is attached to the jar artifact with empty
>> classifier rather than the last
>>artifact of a type defined. Otherwise a project that defines
>> multiple artifacts of the same type
>>(i.e. `package(:jar)` and `package(:jar, :classifier =>
>> :gwt)`) could have the pom named after
>>the package with the classifier rather than the package
>> without a classifer. (i.e. the pom could
>>be incorrectly defined as `mypackage-1.0.0-gwt.pom` rather
>> than `mypackage-1.0.0.pom`).
>>  * Added:  GWT Addon: Add support for GWT 2.8.2 release and make it the
>> default version unless otherwise specified.
>>  * Added:  GWT Addon: Added support for `:js_exports` boolean to enable
>> "JsInteropExports".
>>  * Added:  IDEA Extension: Added support for `:open_in_browser` boolean
>> passed to `ipr.add_gwt_configuration`
>>  * Added:  BUILDR-732 - Support bnd version 2.1.0 or more. Submitted By
>> Eric Bruneton.
>>  * Added:  Support to compiling Kotlin
>>  * Fixed:  Remove section on development builds in the Contributing
>> section.
>>  * Added:  New way to concatenate file contents when merging several
>> archives together.
>>  * Added:  New way to transform file contents when merging several
>> archives together.
>>  * Fixed:  Removed .class files from being checked in.
>>  * Added:  Support both Jetty 6 and Jetty 9 as addons. Added integration
>> tests to cover their use.
>> 
>> 
> 
> 
> -- 
> Cheers,
> 
> Peter Donald


Re: [VOTE] Buildr 1.5.4 release -- CANCELED

2017-09-27 Thread Antoine Toulme
I’ll look and restart a vote then. Thanks!

> On Sep 27, 2017, at 9:16 PM, Peter Donald <pe...@realityforge.org> wrote:
> 
> Actually looked like an easy fix so I committed it to master.
> 
> On Thu, Sep 28, 2017 at 1:48 PM, Peter Donald <pe...@realityforge.org>
> wrote:
> 
>> Actually I have just found a bug. I am not sure if this is a regression or
>> an existing bug. I will have a look at it later tonight, if you could hold
>> off releasing a little longer I can explore what the issue is.
>> 
>> Largely it is if we define a package and a classifier of same package that
>> is not :javadoc or :sources, the pom generated seems to be attached to the
>> last artifact rather than the one with no classifier. Should be easy to fix.
>> 
>> FWIW a reproduction would be something like
>> 
>> package(:jar)
>> package(:jar, :classifier => :gwt)
>> 
>> will produce a pom named "myartifact-2.0-gwt.pom" rather than
>> "myartifact-2.0.pom"
>> 
>> 
>> On Tue, Sep 26, 2017 at 8:19 AM, Peter Donald <pe...@realityforge.org>
>> wrote:
>> 
>>> +1
>>> 
>>> 
>>> Ran the MRI variant through all our ci builds
>>> 
>>> On Mon, Sep 25, 2017 at 8:06 AM, Alex Boisvert <alex.boisv...@gmail.com>
>>> wrote:
>>> 
>>>> +1 (not tested)
>>>> 
>>>> On Sep 24, 2017 3:02 PM, "Antoine Toulme" <anto...@toulme.name> wrote:
>>>> 
>>>>> +1
>>>>> 
>>>>>> On Sep 24, 2017, at 3:03 PM, Antoine Toulme <anto...@toulme.name>
>>>> wrote:
>>>>>> 
>>>>>> We're voting on the source distributions available here:
>>>>>> https://dist.apache.org/repos/dist/dev/buildr/1.5.4/dist/
>>>>>> 
>>>>>> Specifically:
>>>>>> https://dist.apache.org/repos/dist/dev/buildr/1.5.4/dist/
>>>>> buildr-1.5.4.tgz
>>>>>> https://dist.apache.org/repos/dist/dev/buildr/1.5.4/dist/
>>>>> buildr-1.5.4.zip
>>>>>> 
>>>>>> The documentation generated for this release is available here:
>>>>>> https://dist.apache.org/repos/dist/dev/buildr/1.5.4/site/
>>>>>> https://dist.apache.org/repos/dist/dev/buildr/1.5.4/site/buildr.pdf
>>>>>> 
>>>>>> The following changes were made since 1.5.3:
>>>>>> 
>>>>>> * Added: BUILDR-732 - Support bnd version 2.1.0 or more. Submitted
>>>> By
>>>>> Eric Bruneton.
>>>>>> * Added: Support to compiling Kotlin
>>>>>> * Fixed: Remove section on development builds in the Contributing
>>>>> section.
>>>>>> * Added: New way to concatenate file contents when merging several
>>>>> archives together.
>>>>>> * Added: New way to transform file contents when merging several
>>>>> archives together.
>>>>>> * Fixed: Removed .class files from being checked in.
>>>>>> * Added: Support both Jetty 6 and Jetty 9 as addons. Added
>>>> integration
>>>>> tests to cover their use.
>>>>> 
>>>>> 
>>>> 
>>> 
>>> 
>>> 
>>> --
>>> Cheers,
>>> 
>>> Peter Donald
>>> 
>> 
>> 
>> 
>> --
>> Cheers,
>> 
>> Peter Donald
>> 
> 
> 
> 
> --
> Cheers,
> 
> Peter Donald



signature.asc
Description: Message signed with OpenPGP


Re: [VOTE] Buildr 1.5.4 release

2017-09-24 Thread Antoine Toulme
+1

> On Sep 24, 2017, at 3:03 PM, Antoine Toulme <anto...@toulme.name> wrote:
> 
> We're voting on the source distributions available here:
> https://dist.apache.org/repos/dist/dev/buildr/1.5.4/dist/
> 
> Specifically:
> https://dist.apache.org/repos/dist/dev/buildr/1.5.4/dist/buildr-1.5.4.tgz
> https://dist.apache.org/repos/dist/dev/buildr/1.5.4/dist/buildr-1.5.4.zip
> 
> The documentation generated for this release is available here:
> https://dist.apache.org/repos/dist/dev/buildr/1.5.4/site/
> https://dist.apache.org/repos/dist/dev/buildr/1.5.4/site/buildr.pdf
> 
> The following changes were made since 1.5.3:
> 
>  * Added: BUILDR-732 - Support bnd version 2.1.0 or more. Submitted By Eric 
> Bruneton.
>  * Added: Support to compiling Kotlin
>  * Fixed: Remove section on development builds in the Contributing section.
>  * Added: New way to concatenate file contents when merging several archives 
> together.
>  * Added: New way to transform file contents when merging several archives 
> together.
>  * Fixed: Removed .class files from being checked in.
>  * Added: Support both Jetty 6 and Jetty 9 as addons. Added integration tests 
> to cover their use.



[VOTE] Buildr 1.5.4 release

2017-09-24 Thread Antoine Toulme
We're voting on the source distributions available here:
https://dist.apache.org/repos/dist/dev/buildr/1.5.4/dist/

Specifically:
https://dist.apache.org/repos/dist/dev/buildr/1.5.4/dist/buildr-1.5.4.tgz
https://dist.apache.org/repos/dist/dev/buildr/1.5.4/dist/buildr-1.5.4.zip

The documentation generated for this release is available here:
https://dist.apache.org/repos/dist/dev/buildr/1.5.4/site/
https://dist.apache.org/repos/dist/dev/buildr/1.5.4/site/buildr.pdf

The following changes were made since 1.5.3:

  * Added: BUILDR-732 - Support bnd version 2.1.0 or more. Submitted By Eric 
Bruneton.
  * Added: Support to compiling Kotlin
  * Fixed: Remove section on development builds in the Contributing section.
  * Added: New way to concatenate file contents when merging several archives 
together.
  * Added: New way to transform file contents when merging several archives 
together.
  * Fixed: Removed .class files from being checked in.
  * Added: Support both Jetty 6 and Jetty 9 as addons. Added integration tests 
to cover their use.

Re: Cutting 1.5.4?

2017-08-24 Thread Antoine Toulme

> On Aug 24, 2017, at 5:21 PM, Peter Donald <pe...@realityforge.org> wrote:
> 
> Hi hi,
> 
> On Fri, Aug 25, 2017 at 4:26 AM, Antoine Toulme <anto...@toulme.name> wrote:
> 
>> I was wondering about a couple of things we could do.
>> On the one hand, we have this in the changelog right now:
>> 1.5.4 (Pending)
>> * Added: Support to compiling Kotlin
>> * Fixed: Remove section on development builds in the Contributing section.
>> * Added: New way to concatenate file contents when merging several
>> archives together.
>> * Added: New way to transform file contents when merging several archives
>> together.
>> * Fixed: Removed .class files from being checked in.
>> * Added: Support both Jetty 6 and Jetty 9 as addons. Added integration
>> tests to cover their use.
>> We could cut this and release 1.5.4.
>> 
> 
> If we do this route I will also fix BUILDR-732 recently submitted by Eric
> Bruneton
I liked that you asked him to see if he could contribute a fix.
I’d be super stoked to get a contrib, and I can volunteer to do a 1.5.5 just 
for that fix if needed :)
> 
> 
>> At the same time, I am wondering if we could push a few more changes in
>> call it 1.6.0.
>> 
>> Off the top of my head:
>> * Now that we support Kotlin compilation, there is a couple of frameworks
>> we can support for testing, like Spek.
>> * We (ok, maybe just me) could spend some time on the website to revamp
>> it, add more things, remove some more deprecated elements.
>> * Integrate with lock_jar? I started using it in my projects and I think
>> it has unique value most users would not discover on their own.
> 
> 
> I have been meaning to integrate this with or something like it for ages so
> I would love to see this happen.
> 
> 
>> Please let me know what you think.
>> 
> 
> If we decide to go to 1.6.0 I would also like to invest some time and redo
> the way we generate intellij idea project files. I would like to be able to
> support all the different types of projects in idea and all different
> language/artefact types. (Mostly node/typescript and ruby modules).
> 
> I have a library that I have been working on that is ~95% complete at
> https://github.com/realityforge/reality-idea which just helps you generate
> idea project files. Rewriting this as a library is helping me test it
> extensively.
> 
> I have yet to complete the integration back into buildr but I expect I
> should be able to do that while maintaining the existing API. However I am
> about to go on holiday for a bit and in preparation mode for baby2 so I
> suspect I wont be able to get this done until the end of September. If we
> can wait that long for 1.6.0 then I can get off my caboose and work on
> that.
That sounds fine, and congrats! 

Let me know if you’d like help on this.
> 
> Otherwise more than happy for a 1.5.4 release and a 1.6.0 release when we
> get to it.
> 
> -- 
> Cheers,
> 
> Peter Donald



Cutting 1.5.4?

2017-08-24 Thread Antoine Toulme
Hello folks,

I was wondering about a couple of things we could do.
On the one hand, we have this in the changelog right now:
1.5.4 (Pending)
* Added: Support to compiling Kotlin
* Fixed: Remove section on development builds in the Contributing section.
* Added: New way to concatenate file contents when merging several archives 
together.
* Added: New way to transform file contents when merging several archives 
together.
* Fixed: Removed .class files from being checked in.
* Added: Support both Jetty 6 and Jetty 9 as addons. Added integration tests to 
cover their use.
We could cut this and release 1.5.4.

At the same time, I am wondering if we could push a few more changes in call it 
1.6.0.

Off the top of my head:
* Now that we support Kotlin compilation, there is a couple of frameworks we 
can support for testing, like Spek.
* We (ok, maybe just me) could spend some time on the website to revamp it, add 
more things, remove some more deprecated elements.
* Integrate with lock_jar? I started using it in my projects and I think it has 
unique value most users would not discover on their own.

Please let me know what you think.

Cheers,

Antoine

Board report for August 2017

2017-08-01 Thread Antoine Toulme
Hello folks,

I am drafting the board report for August here:
https://cwiki.apache.org/confluence/display/BUILDR/August+2017+Board+Report 


Please feel free to review!

Cheers,

Antoine

Re: Changes to concatenate and transform file contents when merging jars

2017-07-30 Thread Antoine Toulme
To be complete, this came from my experience around Kotlin.

Here is the project I have created working with Kotlin, ,making a Spring boot 
executable jar.
https://github.com/atoulme/cuteuuidgenerator/blob/master/Buildfile 
<https://github.com/atoulme/cuteuuidgenerator/blob/master/Buildfile>

Note the project also comes with a gradle build file so you can compare!

> On Jul 30, 2017, at 8:33 PM, Antoine Toulme <anto...@toulme.name> wrote:
> 
> This is the equivalent - albeit in a more generic way - to the resource 
> transformers of the Maven shade plugin:
> https://maven.apache.org/plugins/maven-shade-plugin/examples/resource-transformers.html
>  
> <https://maven.apache.org/plugins/maven-shade-plugin/examples/resource-transformers.html>
> 
> This also should help with things like the uberjar extension, or in general 
> creating executable, shaded/all-in-one jars.
> 
>> On Jul 30, 2017, at 6:39 PM, Peter Donald <pe...@realityforge.org> wrote:
>> 
>> I am curious what the use case for this is? Is it mostly merged metadata
>> descriptors of one sort or another?
>> 
>> On Sun, Jul 30, 2017 at 7:08 PM, Antoine Toulme <anto...@toulme.name> wrote:
>> 
>>> I have added to the codebase changes to allow concatenating file contents
>>> when merging archives.
>>> 
>>> I am also opening a pull request to do the same thing, but transforming
>>> file contents when they are merged:
>>> 
>>> https://github.com/apache/buildr/pull/28 <https://github.com/apache/
>>> buildr/pull/28>
>>> 
>>> Cheers!
>>> 
>>> Antoine
>> 
>> 
>> 
>> 
>> -- 
>> Cheers,
>> 
>> Peter Donald
> 



Re: Changes to concatenate and transform file contents when merging jars

2017-07-30 Thread Antoine Toulme
This is the equivalent - albeit in a more generic way - to the resource 
transformers of the Maven shade plugin:
https://maven.apache.org/plugins/maven-shade-plugin/examples/resource-transformers.html
 
<https://maven.apache.org/plugins/maven-shade-plugin/examples/resource-transformers.html>

This also should help with things like the uberjar extension, or in general 
creating executable, shaded/all-in-one jars.

> On Jul 30, 2017, at 6:39 PM, Peter Donald <pe...@realityforge.org> wrote:
> 
> I am curious what the use case for this is? Is it mostly merged metadata
> descriptors of one sort or another?
> 
> On Sun, Jul 30, 2017 at 7:08 PM, Antoine Toulme <anto...@toulme.name> wrote:
> 
>> I have added to the codebase changes to allow concatenating file contents
>> when merging archives.
>> 
>> I am also opening a pull request to do the same thing, but transforming
>> file contents when they are merged:
>> 
>> https://github.com/apache/buildr/pull/28 <https://github.com/apache/
>> buildr/pull/28>
>> 
>> Cheers!
>> 
>> Antoine
> 
> 
> 
> 
> -- 
> Cheers,
> 
> Peter Donald



Changes to concatenate and transform file contents when merging jars

2017-07-30 Thread Antoine Toulme
I have added to the codebase changes to allow concatenating file contents when 
merging archives.

I am also opening a pull request to do the same thing, but transforming file 
contents when they are merged:

https://github.com/apache/buildr/pull/28 


Cheers!

Antoine

Re: Pull request to add Kotlin support

2017-07-26 Thread Antoine Toulme
I wasn’t sure either. It looks like we have done that in the past.

Most of the specs are a copy/paste and a little bit of adaptation from Scala 
compiler specs.

I amended the commit over time and added docs.
I also looked at supporting kotlintest, same way we support scalatest. However, 
it turned out to be a thin wrapper/runner for JUnit. I’ll try to use the test 
framework some more before I make more changes.

> On Jul 26, 2017, at 4:00 AM, Peter Donald <pe...@realityforge.org> wrote:
> 
> Hi,
> 
> I have not used Kotlin before so I just eyeballed the code and looks good.
> I do like that there is good test coverage ;)
> 
> The one thing that I did go eh? at was checking in .class files although I
> know we do it for some other addons (nailgun?, testng test filter?). I do
> wonder whether we could get away with not doing that. But other than that I
> like!
> 
> 
> On Wed, Jul 26, 2017 at 3:17 AM, Antoine Toulme <anto...@toulme.name> wrote:
> 
>> Looks like I need to massage the code to work with JRuby.
>> 
>>> On Jul 24, 2017, at 10:30 PM, Peter Donald <pe...@realityforge.org>
>> wrote:
>>> 
>>> Neat ... I will try and have a look towards the end of the week
>>> 
>>> On Mon, Jul 24, 2017 at 4:28 PM, Antoine Toulme <anto...@toulme.name>
>> wrote:
>>> 
>>>> Hello folks,
>>>> 
>>>> Would anybody have time to review my changes to support adding Kotlin to
>>>> the mix of languages we support?
>>>> 
>>>> https://github.com/apache/buildr/pull/26 <https://github.com/apache/
>>>> buildr/pull/26>
>>>> 
>>>> The patch needs polishing, especially docs and handling all the
>> arguments
>>>> the Kotlin compiler provides.
>>>> 
>>>> Cheers,
>>>> 
>>>> Antoine
>>> 
>>> 
>>> 
>>> 
>>> --
>>> Cheers,
>>> 
>>> Peter Donald
>> 
>> 
> 
> 
> -- 
> Cheers,
> 
> Peter Donald



Re: Pull request to add Kotlin support

2017-07-25 Thread Antoine Toulme
Looks like I need to massage the code to work with JRuby.

> On Jul 24, 2017, at 10:30 PM, Peter Donald <pe...@realityforge.org> wrote:
> 
> Neat ... I will try and have a look towards the end of the week
> 
> On Mon, Jul 24, 2017 at 4:28 PM, Antoine Toulme <anto...@toulme.name> wrote:
> 
>> Hello folks,
>> 
>> Would anybody have time to review my changes to support adding Kotlin to
>> the mix of languages we support?
>> 
>> https://github.com/apache/buildr/pull/26 <https://github.com/apache/
>> buildr/pull/26>
>> 
>> The patch needs polishing, especially docs and handling all the arguments
>> the Kotlin compiler provides.
>> 
>> Cheers,
>> 
>> Antoine
> 
> 
> 
> 
> -- 
> Cheers,
> 
> Peter Donald



Pull request to add Kotlin support

2017-07-24 Thread Antoine Toulme
Hello folks,

Would anybody have time to review my changes to support adding Kotlin to the 
mix of languages we support?

https://github.com/apache/buildr/pull/26 


The patch needs polishing, especially docs and handling all the arguments the 
Kotlin compiler provides.

Cheers,

Antoine

Buildr2eclipse - Look, I made something!

2017-05-25 Thread Antoine Toulme
This is very dirty prototype code, but after a little bit of effort, I managed 
to produce the following:

You can see the code at https://github.com/atoulme/b2e 


Refreshing website

2017-05-18 Thread Antoine Toulme
After 1.5.3 is voted on, it might be worthwhile to publish the website. It’s 
still showing 1.5.0 as the latest version right now:
http://buildr.apache.org/ 

Cheers,

Antoine

Re: [VOTE] Buildr 1.5.3 release

2017-05-18 Thread Antoine Toulme
+1 from me, changes look good.


Board report May 2017

2017-05-09 Thread Antoine Toulme
Hi all,

I have prepared the board report for this reporting period. It’s available here:
https://cwiki.apache.org/confluence/display/BUILDR/May+2017+Board+Report 


Please review and modify as needed. I’ll send on Wednesday PST time.

Cheers!

Antoine

Re: [VOTE] Buildr 1.5.2 release

2017-04-03 Thread Antoine Toulme
+1 Thanks for fixing the release scripts :)

> On Apr 3, 2017, at 8:59 AM, Alex Boisvert  wrote:
> 
> +1
> 
> On Sun, Apr 2, 2017 at 4:41 PM, Peter Donald  wrote:
> 
>> +1 from me.
>> 
>> The main reason for the release was to fix pom generation bug that was
>> introduced with the last release.
>> 
>> On Mon, Apr 3, 2017 at 9:39 AM, Peter Donald 
>> wrote:
>> 
>>> We're voting on the source distributions available here:
>>> https://dist.apache.org/repos/dist/dev/buildr/1.5.2/dist/
>>> 
>>> Specifically:
>>> https://dist.apache.org/repos/dist/dev/buildr/1.5.2/dist/
>> buildr-1.5.2.tgz
>>> https://dist.apache.org/repos/dist/dev/buildr/1.5.2/dist/
>> buildr-1.5.2.zip
>>> 
>>> The documentation generated for this release is available here:
>>> https://dist.apache.org/repos/dist/dev/buildr/1.5.2/site/
>>> https://dist.apache.org/repos/dist/dev/buildr/1.5.2/site/buildr.pdf
>>> 
>>> The following changes were made since 1.5.1:
>>> 
>>>  * Change: Update TestNG version to 6.11.
>>>  * Change: BUILDR-731 - Enhance Sonar addon to support configuration of
>>> the project version. Submitted by Ross Mahony.
>>>  * Fixed:  Fix pom generation to eliminate invalid `classifier` element
>>> from being added to POM.
>>> 
>>> 
>> 
>> 
>> --
>> Cheers,
>> 
>> Peter Donald
>> 



Re: [VOTE] Buildr 1.5.1 release

2017-03-29 Thread Antoine Toulme
No problem. I see someone just filed a bug as well (with a patch!).

I'll add a task to test with nexus going forward.

> On Mar 29, 2017, at 02:40, Peter Donald <pe...@realityforge.org> wrote:
> 
> Hi,
> 
> It seems a latent bug in the custom_pom code has been exposed by the latest
> release. In particular the poms that are being generated are invalid as
> they include a classifier. This means if you upload to a repository manager
> that does validation then the upload is blocked.
> 
> I have fixed the problem with the commit
> 
> https://github.com/apache/buildr/commit/c19d2a648e2b9e858a7e6181131ad17539c02ea8
> 
> I was thinking of doing another release in a week or to fix this bug and
> any others that crop up between now and then. Thoughts?
> 
> 
> On Mon, Mar 27, 2017 at 1:17 PM, Peter Donald <pe...@realityforge.org>
> wrote:
> 
>> Great - thanks!
>> 
>> On Mon, Mar 27, 2017 at 12:01 PM, Antoine Toulme <anto...@toulme.name>
>> wrote:
>> 
>>> The release vote passes with 4 binding +1s. I will release the bits soon.
>>> 
>>> Cheers!
>>> 
>>> Antoine
>>> 
>>>> On Mar 26, 2017, at 6:00 PM, Antoine Toulme <anto...@toulme.name>
>>> wrote:
>>>> 
>>>> +1 as well. I didn’t do much testing this time around either, sorry.
>>>> 
>>>>> On Mar 13, 2017, at 2:00 AM, Tammo van Lessen <tvanles...@gmail.com>
>>> wrote:
>>>>> 
>>>>> Couldn't test either yet, but here is my +1.
>>>>> 
>>>>> Best,
>>>>> Tammo
>>>>> 
>>>>> On Mon, Mar 13, 2017 at 1:43 AM, Alex Boisvert <
>>> alex.boisv...@gmail.com>
>>>>> wrote:
>>>>> 
>>>>>> +1 on the release.
>>>>>> 
>>>>>> (I have done no testing.)
>>>>>> 
>>>>>> On Mar 12, 2017 2:16 PM, "Peter Donald" <pe...@realityforge.org>
>>> wrote:
>>>>>> 
>>>>>>> Hi,
>>>>>>> 
>>>>>>> +1
>>>>>>> 
>>>>>>> Tested the MRI variant through our builds nothing popped up.
>>>>>>> 
>>>>>>> We don't have a lot of jruby builds anymore but tested it manually
>>> and
>>>>>> all
>>>>>>> seemed ok.
>>>>>>> 
>>>>>>> 
>>>>>>> On Sun, Mar 12, 2017 at 1:15 PM, Antoine Toulme <anto...@toulme.name
>>>> 
>>>>>>> wrote:
>>>>>>> 
>>>>>>>> 
>>>>>>>> We're voting on the source distributions available here:
>>>>>>>> https://dist.apache.org/repos/dist/dev/buildr/1.5.1/dist/
>>>>>>>> 
>>>>>>>> Specifically:
>>>>>>>> https://dist.apache.org/repos/dist/dev/buildr/1.5.1/dist/
>>>>>>> buildr-1.5.1.tgz
>>>>>>>> https://dist.apache.org/repos/dist/dev/buildr/1.5.1/dist/
>>>>>>> buildr-1.5.1.zip
>>>>>>>> 
>>>>>>>> The documentation generated for this release is available here:
>>>>>>>> https://dist.apache.org/repos/dist/dev/buildr/1.5.1/site/
>>>>>>>> https://dist.apache.org/repos/dist/dev/buildr/1.5.1/site/buildr.pdf
>>>>>>>> 
>>>>>>>> The following changes were made since 1.5.0:
>>>>>>>> 
>>>>>>>> * Change: In the 'buildr/git_auto_version' addon strip out any
>>>>>> versions
>>>>>>>> that start with a 'v' character as
>>>>>>>>  most projects on git repositories prefix version tags with
>>>>>> a
>>>>>>>> "v" to avoid collisions with any branchs
>>>>>>>>  named after the version which are typically without the
>>> "v"
>>>>>>>> character.
>>>>>>>> * Fixed:  GWT Addon: The GWT project publishes invalid jars that can
>>>>>>> not
>>>>>>>> be included on source path when
>>>>>>>>  the javadoc tool is executing. Work around this issue in
>>>>>> GWT
>>>>>>>> by removing them from the documentation
>>>>>>>>  class path.
>>>>&g

Re: [VOTE] Buildr 1.5.1 release

2017-03-26 Thread Antoine Toulme
The release vote passes with 4 binding +1s. I will release the bits soon.

Cheers!

Antoine

> On Mar 26, 2017, at 6:00 PM, Antoine Toulme <anto...@toulme.name> wrote:
> 
> +1 as well. I didn’t do much testing this time around either, sorry.
> 
>> On Mar 13, 2017, at 2:00 AM, Tammo van Lessen <tvanles...@gmail.com> wrote:
>> 
>> Couldn't test either yet, but here is my +1.
>> 
>> Best,
>> Tammo
>> 
>> On Mon, Mar 13, 2017 at 1:43 AM, Alex Boisvert <alex.boisv...@gmail.com>
>> wrote:
>> 
>>> +1 on the release.
>>> 
>>> (I have done no testing.)
>>> 
>>> On Mar 12, 2017 2:16 PM, "Peter Donald" <pe...@realityforge.org> wrote:
>>> 
>>>> Hi,
>>>> 
>>>> +1
>>>> 
>>>> Tested the MRI variant through our builds nothing popped up.
>>>> 
>>>> We don't have a lot of jruby builds anymore but tested it manually and
>>> all
>>>> seemed ok.
>>>> 
>>>> 
>>>> On Sun, Mar 12, 2017 at 1:15 PM, Antoine Toulme <anto...@toulme.name>
>>>> wrote:
>>>> 
>>>>> 
>>>>> We're voting on the source distributions available here:
>>>>> https://dist.apache.org/repos/dist/dev/buildr/1.5.1/dist/
>>>>> 
>>>>> Specifically:
>>>>> https://dist.apache.org/repos/dist/dev/buildr/1.5.1/dist/
>>>> buildr-1.5.1.tgz
>>>>> https://dist.apache.org/repos/dist/dev/buildr/1.5.1/dist/
>>>> buildr-1.5.1.zip
>>>>> 
>>>>> The documentation generated for this release is available here:
>>>>> https://dist.apache.org/repos/dist/dev/buildr/1.5.1/site/
>>>>> https://dist.apache.org/repos/dist/dev/buildr/1.5.1/site/buildr.pdf
>>>>> 
>>>>> The following changes were made since 1.5.0:
>>>>> 
>>>>> * Change: In the 'buildr/git_auto_version' addon strip out any
>>> versions
>>>>> that start with a 'v' character as
>>>>>   most projects on git repositories prefix version tags with
>>> a
>>>>> "v" to avoid collisions with any branchs
>>>>>   named after the version which are typically without the "v"
>>>>> character.
>>>>> * Fixed:  GWT Addon: The GWT project publishes invalid jars that can
>>>> not
>>>>> be included on source path when
>>>>>   the javadoc tool is executing. Work around this issue in
>>> GWT
>>>>> by removing them from the documentation
>>>>>   class path.
>>>>> * Change: IDEA: Change the ordering of dependencies in the IDE module
>>>>> descriptor such that test dependencies are
>>>>>   first to allow test dependencies to override/shadow compile
>>>>> dependencies.
>>>>> * Fixed:  IDEA: Correctly configure the IDE module if the language
>>>> level
>>>>> differs from the root project language level.
>>>>> * Change: Add css2gss task to gwt addon to support conveting from
>>>>> deprecated css syntax to modern gss syntax.
>>>>> * Change: Add support for gwt 2.8.0 to gwt addon.
>>>>> * Change: Remove orderedhash gem.
>>>>> * Change: Update jruby-openssl to 0.9.17
>>>>> * Change: Move hoe to the development dependencies
>>>>> * Fixed:  BUILDR-728 Snapshots metadata incorrectly created
>>>>> * Fixed:  BUILDR-718 Deprecate SVN repository - remove links to SVN
>>>>> * Change: BUILDR-724 Use scalamain to call scala projects
>>>>> * Change: BUILDR-719 Change User-Agent when uploading artifacts
>>>>> * Change: Set the OPEN_IN_BROWSER to false when building idea launch
>>>>> targets via add_glassfish_remote_configuration.
>>>>> * Change: BUILDR-709 Integrate `buildr/custom_pom` into core and just
>>>>> make it the default pom generated.
>>>>> * Fixed:  BUILDR-563 protobuf addon including source directories to
>>>>> protoc breaks build
>>>> 
>>>> 
>>>> 
>>>> 
>>>> --
>>>> Cheers,
>>>> 
>>>> Peter Donald
>>>> 
>>> 
>> 
>> 
>> 
>> -- 
>> Tammo van Lessen - http://www.taval.de
> 



Re: [VOTE] Buildr 1.5.1 release

2017-03-26 Thread Antoine Toulme
+1 as well. I didn’t do much testing this time around either, sorry.

> On Mar 13, 2017, at 2:00 AM, Tammo van Lessen <tvanles...@gmail.com> wrote:
> 
> Couldn't test either yet, but here is my +1.
> 
> Best,
>  Tammo
> 
> On Mon, Mar 13, 2017 at 1:43 AM, Alex Boisvert <alex.boisv...@gmail.com>
> wrote:
> 
>> +1 on the release.
>> 
>> (I have done no testing.)
>> 
>> On Mar 12, 2017 2:16 PM, "Peter Donald" <pe...@realityforge.org> wrote:
>> 
>>> Hi,
>>> 
>>> +1
>>> 
>>> Tested the MRI variant through our builds nothing popped up.
>>> 
>>> We don't have a lot of jruby builds anymore but tested it manually and
>> all
>>> seemed ok.
>>> 
>>> 
>>> On Sun, Mar 12, 2017 at 1:15 PM, Antoine Toulme <anto...@toulme.name>
>>> wrote:
>>> 
>>>> 
>>>> We're voting on the source distributions available here:
>>>> https://dist.apache.org/repos/dist/dev/buildr/1.5.1/dist/
>>>> 
>>>> Specifically:
>>>> https://dist.apache.org/repos/dist/dev/buildr/1.5.1/dist/
>>> buildr-1.5.1.tgz
>>>> https://dist.apache.org/repos/dist/dev/buildr/1.5.1/dist/
>>> buildr-1.5.1.zip
>>>> 
>>>> The documentation generated for this release is available here:
>>>> https://dist.apache.org/repos/dist/dev/buildr/1.5.1/site/
>>>> https://dist.apache.org/repos/dist/dev/buildr/1.5.1/site/buildr.pdf
>>>> 
>>>> The following changes were made since 1.5.0:
>>>> 
>>>>  * Change: In the 'buildr/git_auto_version' addon strip out any
>> versions
>>>> that start with a 'v' character as
>>>>most projects on git repositories prefix version tags with
>> a
>>>> "v" to avoid collisions with any branchs
>>>>named after the version which are typically without the "v"
>>>> character.
>>>>  * Fixed:  GWT Addon: The GWT project publishes invalid jars that can
>>> not
>>>> be included on source path when
>>>>the javadoc tool is executing. Work around this issue in
>> GWT
>>>> by removing them from the documentation
>>>>class path.
>>>>  * Change: IDEA: Change the ordering of dependencies in the IDE module
>>>> descriptor such that test dependencies are
>>>>first to allow test dependencies to override/shadow compile
>>>> dependencies.
>>>>  * Fixed:  IDEA: Correctly configure the IDE module if the language
>>> level
>>>> differs from the root project language level.
>>>>  * Change: Add css2gss task to gwt addon to support conveting from
>>>> deprecated css syntax to modern gss syntax.
>>>>  * Change: Add support for gwt 2.8.0 to gwt addon.
>>>>  * Change: Remove orderedhash gem.
>>>>  * Change: Update jruby-openssl to 0.9.17
>>>>  * Change: Move hoe to the development dependencies
>>>>  * Fixed:  BUILDR-728 Snapshots metadata incorrectly created
>>>>  * Fixed:  BUILDR-718 Deprecate SVN repository - remove links to SVN
>>>>  * Change: BUILDR-724 Use scalamain to call scala projects
>>>>  * Change: BUILDR-719 Change User-Agent when uploading artifacts
>>>>  * Change: Set the OPEN_IN_BROWSER to false when building idea launch
>>>> targets via add_glassfish_remote_configuration.
>>>>  * Change: BUILDR-709 Integrate `buildr/custom_pom` into core and just
>>>> make it the default pom generated.
>>>>  * Fixed:  BUILDR-563 protobuf addon including source directories to
>>>> protoc breaks build
>>> 
>>> 
>>> 
>>> 
>>> --
>>> Cheers,
>>> 
>>> Peter Donald
>>> 
>> 
> 
> 
> 
> -- 
> Tammo van Lessen - http://www.taval.de



[VOTE] Buildr 1.5.1 release

2017-03-11 Thread Antoine Toulme

We're voting on the source distributions available here:
https://dist.apache.org/repos/dist/dev/buildr/1.5.1/dist/

Specifically:
https://dist.apache.org/repos/dist/dev/buildr/1.5.1/dist/buildr-1.5.1.tgz
https://dist.apache.org/repos/dist/dev/buildr/1.5.1/dist/buildr-1.5.1.zip

The documentation generated for this release is available here:
https://dist.apache.org/repos/dist/dev/buildr/1.5.1/site/
https://dist.apache.org/repos/dist/dev/buildr/1.5.1/site/buildr.pdf

The following changes were made since 1.5.0:

  * Change: In the 'buildr/git_auto_version' addon strip out any versions that 
start with a 'v' character as
most projects on git repositories prefix version tags with a "v" to 
avoid collisions with any branchs
named after the version which are typically without the "v" 
character.
  * Fixed:  GWT Addon: The GWT project publishes invalid jars that can not be 
included on source path when
the javadoc tool is executing. Work around this issue in GWT by 
removing them from the documentation
class path.
  * Change: IDEA: Change the ordering of dependencies in the IDE module 
descriptor such that test dependencies are
first to allow test dependencies to override/shadow compile 
dependencies.
  * Fixed:  IDEA: Correctly configure the IDE module if the language level 
differs from the root project language level.
  * Change: Add css2gss task to gwt addon to support conveting from deprecated 
css syntax to modern gss syntax.
  * Change: Add support for gwt 2.8.0 to gwt addon.
  * Change: Remove orderedhash gem.
  * Change: Update jruby-openssl to 0.9.17
  * Change: Move hoe to the development dependencies
  * Fixed:  BUILDR-728 Snapshots metadata incorrectly created
  * Fixed:  BUILDR-718 Deprecate SVN repository - remove links to SVN
  * Change: BUILDR-724 Use scalamain to call scala projects
  * Change: BUILDR-719 Change User-Agent when uploading artifacts
  * Change: Set the OPEN_IN_BROWSER to false when building idea launch targets 
via add_glassfish_remote_configuration.
  * Change: BUILDR-709 Integrate `buildr/custom_pom` into core and just make it 
the default pom generated.
  * Fixed:  BUILDR-563 protobuf addon including source directories to protoc 
breaks build

Re: Buildr board report for February 2017

2017-02-08 Thread Antoine Toulme
I have sent the report. Thanks!

> On Feb 6, 2017, at 8:51 PM, Antoine Toulme <anto...@toulme.name> wrote:
> 
> Hello all!
> 
> I have placed the board report for Buildr here:
> https://cwiki.apache.org/confluence/display/BUILDR/February+2017+Board+Report 
> <https://cwiki.apache.org/confluence/display/BUILDR/February+2017+Board+Report>
> 
> Please feel free to review, I’ll submit it Wednesday PST!
> 
> Cheers,
> 
> Antoine



Buildr board report for February 2017

2017-02-06 Thread Antoine Toulme
Hello all!

I have placed the board report for Buildr here:
https://cwiki.apache.org/confluence/display/BUILDR/February+2017+Board+Report 


Please feel free to review, I’ll submit it Wednesday PST!

Cheers,

Antoine

Re: An update, and happy Thanksgiving

2016-12-29 Thread Antoine Toulme
1.5.1 is slipping into 2017. No worries, we’ll get it down.


> On Dec 4, 2016, at 10:04 PM, Antoine Toulme <anto...@toulme.name> wrote:
> 
>> 
>> On Nov 23, 2016, at 2:22 PM, Peter Donald <pe...@realityforge.org> wrote:
>> 
>> Hi,
>> 
>> On Sat, Nov 19, 2016 at 4:12 PM, Antoine Toulme <anto...@toulme.name> wrote:
>> 
>>> the board meeting went over well.
>>> 
>> 
>> great.
>> 
>> 
>>> We’re still due for a big discussion on how to sustain and attract more
>>> people to the project. I started something, and well now we’re a month
>>> later.
>>> 
>> 
>> Yep. Sorry - I am not going to be much help until after the xmas season :(
>> Small child and large family :)
> No worries.
>> 
>> 1.5.1 is still very much time bound to Christmas time. Interestingly, no
>>> bugs on 1.5.0 have surfaced but one, so far.
>>> 
>> 
>> Nothing popped up here in all our testing. So I think it must be fairly
>> solid.
> Cool.
>> 
>> 
>>> I’m going to try to knock a few things off the bug list.
>>> 
>> 
>> Great. The requests that I hear are often about how to make it easier to
>> integrate into the wider ecosystem. In no particular order the requests are;
>> 
>> * Easier to launch/install (which your docker work may handle)
> OK. Still much to do there.
>> * Integrate `buildr/custom_pom` into core and just make it the default pom
>> generated.
> BUILDR-729 filed.
>> * Add a mechanism to more easily declare "provided" dependencies. It has
>> been suggested that something like "compile.provides << :mydep" may work
>> but not sure how this request interacts with `buildr/custom_pom`. Maybe
>> `custom_pom` could be based of this.
> Added as a comment of BUILDR-729.
>> * Add a way to do a "full" release to maven central. I am not sure exactly
>> what this means but I get the impression that some tools allow you to
>> upload to the maven central staging repository, "close" the repository and
>> "release" the repository. I currently do steps 2 and 3 manually and don't
>> find it too onerous but others have suggested that they would like it
>> "fixed”.
> Wow, not sure about this. I’ve been doing some releases to Maven Central with 
> Buildr and it did look like you need to do those steps manually.
> I filed BUILDR-730 for this.
>> 
>> Anyhoo - just in case you need some new ideas ;)
>> 
>> 
>>> 
>>> I played with making a Docker image using a minified JDK9 image to run
>>> Buildr. RJB doesn’t work well with it right now.
>>> https://github.com/atoulme/docker-buildr/blob/master/Dockerfile <
>>> https://github.com/atoulme/docker-buildr/blob/master/Dockerfile>
>>> 
>> 
>> 
>> Interesting. We use an alpine+jdk7 image locally. I may experiment with it
>> over the weekend ;)
>> 
>> 
>> -- 
>> Cheers,
>> 
>> Peter Donald



Fwd: [jira] [Commented] (BUILDR-274) Support dependency version ranges for transitive dependencies

2016-12-04 Thread Antoine Toulme
This is a good point. Should we have Buildr depend on lock_jar?

> Begin forwarded message:
> 
> From: "Trejkaz (JIRA)" 
> Subject: [jira] [Commented] (BUILDR-274) Support dependency version ranges 
> for transitive dependencies
> Date: November 21, 2016 at 7:19:58 PM PST
> To: buildr-comm...@incubator.apache.org
> Reply-To: dev@buildr.apache.org
> 
> 
>[ 
> https://issues.apache.org/jira/browse/BUILDR-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15685541#comment-15685541
>  ] 
> 
> Trejkaz commented on BUILDR-274:
> 
> 
> Arguably I shouldn't have to install some completely different dependency 
> resolver just to make a build tool resolve dependencies correctly, but maybe 
> that's just me.
> 
> 
>> Support dependency version ranges for transitive dependencies
>> -
>> 
>>Key: BUILDR-274
>>URL: https://issues.apache.org/jira/browse/BUILDR-274
>>Project: Buildr
>> Issue Type: New Feature
>> Components: Dependency management
>>   Reporter: Martin Grotzke
>>Fix For: Wish List
>> 
>> 
>> It seems that right now dependency version ranges as shown here [1] are not 
>> supported.
>> A version range is e.g. used by ehcache-web ([2]), so that when I use
>>  transitive('net.sf.ehcache:ehcache-web:jar:1.6.0-beta2')
>> buildr fails with this error:
>>  Failed to download net.sf.ehcache:ehcache:pom:[1.6.0-beta4,], tried the 
>> following repositories...
>> It would be great to have support for version ranges, otherwise some libs 
>> cannot be used with transitive().
>> [1] 
>> http://www.sonatype.com/books/maven-book/reference/pom-relationships-sect-version-ranges.html
>> [2] 
>> http://repo1.maven.org/maven2/net/sf/ehcache/ehcache-web/1.6.0-beta2/ehcache-web-1.6.0-beta2.pom
> 
> 
> 
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)



Re: November board report

2016-11-07 Thread Antoine Toulme
OK, sending the report now.

> On Nov 2, 2016, at 9:59 PM, Antoine Toulme <anto...@toulme.name> wrote:
> 
> Hello all,
> 
> I have taken a first stab at the board report for Buildr.
> 
> Please review and edit at will:
> 
> https://cwiki.apache.org/confluence/display/BUILDR/November+2016+Board+Report 
> <https://cwiki.apache.org/confluence/display/BUILDR/November+2016+Board+Report>
> 
> I think I will send the report next Monday, to give everybody time to review.
> 
> Cheers,
> 
> Antoine



Re: Access to confluence

2016-11-02 Thread Antoine Toulme
Yep, it works now. Thanks!

> On Nov 2, 2016, at 6:04 PM, Alex Boisvert <alex.boisv...@gmail.com> wrote:
> 
> Weird, it says "No match found" but then it allowed me to add you.
> 
> You should be good to go now.
> 
> On Wed, Nov 2, 2016 at 5:59 PM, Antoine Toulme <anto...@toulme.name> wrote:
> 
>> My login is “toulmean”. Sorry for the confusion.
>> 
>>> On Nov 2, 2016, at 5:56 PM, Alex Boisvert <alex.boisv...@gmail.com>
>> wrote:
>>> 
>>> I have admin access (as well as Peter D.)
>>> 
>>> What's your login?  I'm not finding you through search for "Antoine
>> Toulme".
>>> 
>>> On Wed, Nov 2, 2016 at 12:48 AM, Antoine Toulme <anto...@toulme.name>
>> wrote:
>>> 
>>>> Hey folks,
>>>> 
>>>> I need access to confluence to post the draft of the next board report.
>>>> 
>>>> https://cwiki.apache.org/confluence/display/BUILDR
>>>> 
>>>> Would you please add me to the space?
>>>> 
>>>> Thanks!
>>>> 
>>>> Antoine
>>>> 
>> 
>> 



Access to confluence

2016-11-02 Thread Antoine Toulme
Hey folks,

I need access to confluence to post the draft of the next board report.

https://cwiki.apache.org/confluence/display/BUILDR

Would you please add me to the space?

Thanks!

Antoine


Re: [VOTE] Buildr 1.5.0 release

2016-09-23 Thread Antoine Toulme
OK, sorry it took me a while to circle back and cut RC2.

Here is my +1.

> On Sep 23, 2016, at 10:18 PM, Antoine Toulme <anto...@toulme.name> wrote:
> 
> We're voting on the source distributions available here:
> https://dist.apache.org/repos/dist/dev/buildr/1.5.0.RC2/dist/
> 
> Specifically:
> https://dist.apache.org/repos/dist/dev/buildr/1.5.0.RC2/dist/buildr-1.5.0.tgz
> https://dist.apache.org/repos/dist/dev/buildr/1.5.0.RC2/dist/buildr-1.5.0.zip
> 
> The documentation generated for this release is available here:
> https://dist.apache.org/repos/dist/dev/buildr/1.5.0.RC2/site/
> https://dist.apache.org/repos/dist/dev/buildr/1.5.0.RC2/site/buildr.pdf
> 
> The following changes were made since 1.4.25:
> 
>  * 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
>  * Change: Update ecj to 4.5.1
>  * Change: Added jekyll-textile-converter 0.1.0 to generate the site.
>  * Change: Move to default on Scala 2.11.
>  * Change: Remove Buildr::Project#on_define, deprecated in 1.3
>  * Change: Remove JavaWrapper, deprecated in 1.3
>  * Change: Remove JUnit::REQUIRES, deprecated in 1.3.3
>  * Change: Remove TestNG::REQUIRES, deprecated in 1.3.3
>  * Change: Remove Buildr::Ant::REQUIRES, deprecated in version 1.3.3
>  * Change: Remove Buildr::CompileTask#classpath, deprecated in version 1.3
>  * Change: Remove Buildr::TestTask responding to :using with 
> .using('foo','bar'), deprecated in version 1.3
>  * Change: Remove addon/buildr/cobertura.rb, deprecated since 1.3.4
>  * Change: Remove addon/buildr/emma.rb, deprecated since 1.3.4
>  * Change: Remove support for Rakefile/rakefile, deprecated.
>  * Change: Remove project#target, project#reports, deprecated.
>  * Change: Remove JBehave::REQUIRES, deprecated.
>  * Change: Remove JMock::REQUIRES, deprecated.
>  * Change: Remove ScalaCheck::REQUIRES, deprecated.
>  * Change: Change Eclipse Scala project natures from 
> ch.epfl.lamp.sdt.core.scalanature to org.scala-ide.sdt.core.scalanature
>  * Change: Fix the custom Google search widget on the website.
>  * Change: BUILDR-722 Remove links and image of the buildr book from the 
> website.
>  * Added:  Travis badge to README.rdoc
>  * Added:  Added Rubygems badges to README.rdoc
>  * Added:  BUILDR-577 Allow remote repo to be added with http basic auth 
> support. Submitted by Michael Guymon.
>  * Added:  BUILDR-523 Issue a warning when Java.classpath is modified after 
> Java.load has happened
>  * Added:  BUILDR-594 Added support for changing the verification mode of SSL 
> certificates
>  * Added:  BUILDR-595 Added support to providing custom SSL certificates
>  * Added:  BUILDR-572 Allow to upload unique version (timestamp based) 
> snapshot artifacts to a repository. Submitted by Brice Figureau.
>  * 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
>  * Fixed:  BUILDR-565 resources are not included in the war if defined after 
> package call
>  * Fixed:  BUILDR-621 ZipTask creates zip file with entries not sorted by 
> path causing very slow unzipping.
>  * Fixed:  BUILDR-695 transitive doesn't support ${project.parent.version} in 
> POM.
>  * Fixed:  BUILDR-653 Using Eclipse compiler (ECJ)
>  * Fixed:  BUILDR-476 Buildr doesn't respect company repository manager
>  * Fixed:  BUILDR-454 Definition-level parent-child references-by-name fail 
> in 1.4.0 but not in 1.3.5. Submitted by Rhett Sutphin.
>  * Fixed:  BUILDR-620 resources.filter should not run on non-text files
>  * Fixed:  BUILDR-489 Java + Scala joint compiler fails if default encoding 
> and source file encoding are not same and special characters have been used 
> in source code
>  * Fixed:  BUILDR-486 Buildr-generated poms should include dependencies
>  * Fixed:  BUILDR-723 JavaTestFilter is unable to parse paths containing %2F
>  * Change: Update the custom_pom addon to generate poms with exclusions 
> section that excludes
>all transitive dependencies. This is required as buildr 
> dependencies are not
>transitive while Maven's dependencies are transitive by default.
>  * Change: Remove the BND aqute maven repository, as it was decomissioned. 
> Use Maven Central instead.



signature.asc
Description: Message signed with OpenPGP using GPGMail


Re: [VOTE] Buildr 1.5.0 release

2016-09-18 Thread Antoine Toulme
OK I will start a new vote. Thanks for catching the issue!

> On Sep 18, 2016, at 7:43 PM, Peter Donald <pe...@realityforge.org> wrote:
> 
> Ok - I made the changes to source control and tested the resultant
> artifacts. +1 to release that version ;)
> 
> On Sun, Sep 18, 2016 at 12:28 PM, Peter Donald <pe...@realityforge.org> wrote:
>> Actually it looks like you just need to delete the line at
>> 
>> https://github.com/apache/buildr/blob/master/lib/buildr/core/test.rb#L360
>> 
>> After that is done I am +1 on release.
>> 
>> I don't have access to buildr source right now to do it now but will
>> get to it if you don't beat me to it ;)
>> 
>> On Sun, Sep 18, 2016 at 12:21 PM, Peter Donald <pe...@realityforge.org> 
>> wrote:
>>> Functionally it seems to work. It just looks like there is some
>>> debugging left in there somewhere. The test framework that is used in
>>> each project is printed out in every build. (i.e. we see "junit"
>>> printed for every project that defines junit tests and "testng" for
>>> every project that defines testng tests.
>>> 
>>> I may get a chance on Monday to dig deeper. Other than that - all
>>> seems to be good.
>>> 
>>> On Sat, Sep 17, 2016 at 4:25 PM, Antoine Toulme <anto...@toulme.name> wrote:
>>>> We're voting on the source distributions available here:
>>>> https://dist.apache.org/repos/dist/dev/buildr/1.5.0/dist/
>>>> 
>>>> Specifically:
>>>> https://dist.apache.org/repos/dist/dev/buildr/1.5.0/dist/buildr-1.5.0.tgz
>>>> https://dist.apache.org/repos/dist/dev/buildr/1.5.0/dist/buildr-1.5.0.zip
>>>> 
>>>> The documentation generated for this release is available here:
>>>> https://dist.apache.org/repos/dist/dev/buildr/1.5.0/site/
>>>> https://dist.apache.org/repos/dist/dev/buildr/1.5.0/site/buildr.pdf
>>>> 
>>>> The following changes were made since 1.4.25:
>>>> 
>>>>  * 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
>>>>  * Change: Update ecj to 4.5.1
>>>>  * Change: Added jekyll-textile-converter 0.1.0 to generate the site.
>>>>  * Change: Move to default on Scala 2.11.
>>>>  * Change: Remove Buildr::Project#on_define, deprecated in 1.3
>>>>  * Change: Remove JavaWrapper, deprecated in 1.3
>>>>  * Change: Remove JUnit::REQUIRES, deprecated in 1.3.3
>>>>  * Change: Remove TestNG::REQUIRES, deprecated in 1.3.3
>>>>  * Change: Remove Buildr::Ant::REQUIRES, deprecated in version 1.3.3
>>>>  * Change: Remove Buildr::CompileTask#classpath, deprecated in version 1.3
>>>>  * Change: Remove Buildr::TestTask responding to :using with 
>>>> .using('foo','bar'), deprecated in version 1.3
>>>>  * Change: Remove addon/buildr/cobertura.rb, deprecated since 1.3.4
>>>>  * Change: Remove addon/buildr/emma.rb, deprecated since 1.3.4
>>>>  * Change: Remove support for Rakefile/rakefile, deprecated.
>>>>  * Change: Remove project#target, project#reports, deprecated.
>>>>  * Change: Remove JBehave::REQUIRES, deprecated.
>>>>  * Change: Remove JMock::REQUIRES, deprecated.
>>>>  * Change: Remove ScalaCheck::REQUIRES, deprecated.
>>>>  * Change: Change Eclipse Scala project natures from 
>>>> ch.epfl.lamp.sdt.core.scalanature to org.scala-ide.sdt.core.scalanature
>>>>  * Change: Fix the custom Google search widget on the website.
>>>>  * Change: BUILDR-722 Remove links and image of the buildr book from the 
>>>> website.
>>>>  * Added:  Travis badge to README.rdoc
>>>>  * Added:  Added Rubygems badges to README.rdoc
>>>>  * Added:  BUILDR-577 Allow remote repo to be added with http basic auth 
>>>> support. Submitted by Michael Guymon.
>>>>  * Added:  BUILDR-523 Issue a warning when Java.classpath is modified 
>>>> after Java.load has happened
>>>>  * Added:  BUILDR-594 Added support for changing the verification mode of 
>>>> SSL certificates
>>>>  * Added:  BUILDR-595 Added support to providing custom SSL certificates
>>>>  * Added:  BUI

[VOTE] Buildr 1.5.0 release

2016-09-17 Thread Antoine Toulme
We're voting on the source distributions available here:
https://dist.apache.org/repos/dist/dev/buildr/1.5.0/dist/

Specifically:
https://dist.apache.org/repos/dist/dev/buildr/1.5.0/dist/buildr-1.5.0.tgz
https://dist.apache.org/repos/dist/dev/buildr/1.5.0/dist/buildr-1.5.0.zip

The documentation generated for this release is available here:
https://dist.apache.org/repos/dist/dev/buildr/1.5.0/site/
https://dist.apache.org/repos/dist/dev/buildr/1.5.0/site/buildr.pdf

The following changes were made since 1.4.25:

  * 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
  * Change: Update ecj to 4.5.1
  * Change: Added jekyll-textile-converter 0.1.0 to generate the site.
  * Change: Move to default on Scala 2.11.
  * Change: Remove Buildr::Project#on_define, deprecated in 1.3
  * Change: Remove JavaWrapper, deprecated in 1.3
  * Change: Remove JUnit::REQUIRES, deprecated in 1.3.3
  * Change: Remove TestNG::REQUIRES, deprecated in 1.3.3
  * Change: Remove Buildr::Ant::REQUIRES, deprecated in version 1.3.3
  * Change: Remove Buildr::CompileTask#classpath, deprecated in version 1.3
  * Change: Remove Buildr::TestTask responding to :using with 
.using('foo','bar'), deprecated in version 1.3
  * Change: Remove addon/buildr/cobertura.rb, deprecated since 1.3.4
  * Change: Remove addon/buildr/emma.rb, deprecated since 1.3.4
  * Change: Remove support for Rakefile/rakefile, deprecated.
  * Change: Remove project#target, project#reports, deprecated.
  * Change: Remove JBehave::REQUIRES, deprecated.
  * Change: Remove JMock::REQUIRES, deprecated.
  * Change: Remove ScalaCheck::REQUIRES, deprecated.
  * Change: Change Eclipse Scala project natures from 
ch.epfl.lamp.sdt.core.scalanature to org.scala-ide.sdt.core.scalanature
  * Change: Fix the custom Google search widget on the website.
  * Change: BUILDR-722 Remove links and image of the buildr book from the 
website.
  * Added:  Travis badge to README.rdoc
  * Added:  Added Rubygems badges to README.rdoc
  * Added:  BUILDR-577 Allow remote repo to be added with http basic auth 
support. Submitted by Michael Guymon.
  * Added:  BUILDR-523 Issue a warning when Java.classpath is modified after 
Java.load has happened
  * Added:  BUILDR-594 Added support for changing the verification mode of SSL 
certificates
  * Added:  BUILDR-595 Added support to providing custom SSL certificates
  * Added:  BUILDR-572 Allow to upload unique version (timestamp based) 
snapshot artifacts to a repository. Submitted by Brice Figureau.
  * 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
  * Fixed:  BUILDR-565 resources are not included in the war if defined after 
package call
  * Fixed:  BUILDR-621 ZipTask creates zip file with entries not sorted by path 
causing very slow unzipping.
  * Fixed:  BUILDR-695 transitive doesn't support ${project.parent.version} in 
POM.
  * Fixed:  BUILDR-653 Using Eclipse compiler (ECJ)
  * Fixed:  BUILDR-476 Buildr doesn't respect company repository manager
  * Fixed:  BUILDR-454 Definition-level parent-child references-by-name fail in 
1.4.0 but not in 1.3.5. Submitted by Rhett Sutphin.
  * Fixed:  BUILDR-620 resources.filter should not run on non-text files
  * Fixed:  BUILDR-489 Java + Scala joint compiler fails if default encoding 
and source file encoding are not same and special characters have been used in 
source code
  * Fixed:  BUILDR-486 Buildr-generated poms should include dependencies
  * Fixed:  BUILDR-723 JavaTestFilter is unable to parse paths containing %2F
  * Change: Update the custom_pom addon to generate poms with exclusions 
section that excludes
all transitive dependencies. This is required as buildr 
dependencies are not
transitive while Maven's dependencies are transitive by default.
  * Change: Remove the BND aqute maven repository, as it was decomissioned. Use 
Maven Central instead.


signature.asc
Description: Message signed with OpenPGP using GPGMail


Buildr book

2016-08-26 Thread Antoine Toulme
Hey folks,

the Buildr website mentions the Buildr book:
https://www.amazon.com/Buildr/dp/1442160942/ 


Would you like to keep a link from the official site to the book? Should we 
create a second edition with the latest material?

Cheers,

Antoine


signature.asc
Description: Message signed with OpenPGP using GPGMail


Re: Creating 1.5.1 and jira access rights

2016-08-23 Thread Antoine Toulme
Thanks Peter, much appreciated!

> On Aug 23, 2016, at 5:43 PM, Peter Donald <pe...@realityforge.org> wrote:
> 
> Hi,
> 
> On Wed, Aug 24, 2016 at 3:54 AM, Antoine Toulme <anto...@toulme.name> wrote:
>> How can I go about creating version 1.5.1 in Jira? Alex, would you mind 
>> creating it or giving me rights?
> 
> I can't give you access rights - I assume only infrastructure@apache
> can but I created that version, marked a few previous versions as
> released and archived some historic versions. Holler if you need
> anything else
> 
> 
> --
> Cheers,
> 
> Peter Donald



signature.asc
Description: Message signed with OpenPGP using GPGMail


Creating 1.5.1 and jira access rights

2016-08-23 Thread Antoine Toulme
How can I go about creating version 1.5.1 in Jira? Alex, would you mind 
creating it or giving me rights?

Cheers!

Antoine


signature.asc
Description: Message signed with OpenPGP using GPGMail


Re: require 'buildr/scala'

2016-08-21 Thread Antoine Toulme
No worries, I’ll look into that.

Looks like I got all the 1.5 deprecation notices done. The last CI build is 
green.

I have started testing the dev gem, and just pushed dev2, with a few fixes.

Here is a toy project with Buildr, running Scalatest and Java:
https://github.com/tmio/scalamain/blob/master/Buildfile 
<https://github.com/tmio/scalamain/blob/master/Buildfile>

> On Aug 21, 2016, at 9:24 PM, Alex Boisvert <alex.boisv...@gmail.com> wrote:
> 
> Also curious how that would work but if it's just a simple check for,
> e.g.,src/main/scala/**.scala. then all is well.
> 
> On Sun, Aug 21, 2016 at 6:33 PM, Peter Donald <pe...@realityforge.org>
> wrote:
> 
>> What is the impact if the project does not use scala?
>> 
>> On Mon, Aug 22, 2016 at 11:32 AM, Antoine Toulme
>> <anto...@lunar-ocean.com> wrote:
>>> Hello all,
>>> 
>>> would it make sense to remove the need to explicitly require
>> ‘buildr/scala’? I’d like to have my Scala sources detected by default.
>>> 
>>> Please let me know what you think?
>>> 
>>> Antoine
>> 
>> 
>> 
>> --
>> Cheers,
>> 
>> Peter Donald
>> 



Re: Update on development for 1.5

2016-08-16 Thread Antoine Toulme
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 <anto...@toulme.name> wrote:
> 
> On Aug 15, 2016, at 3:47 PM, Alex Boisvert <alex.boisv...@gmail.com> wrote:
>> 
>> On Mon, Aug 15, 2016 at 3:24 PM, Antoine Toulme <anto...@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

2016-08-15 Thread Antoine Toulme
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 <anto...@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
>>> 
>>> 
>>>   com.biz
>>>   app
>>>   1.0
>>> 
>>> 
>>> to
>>> 
>>> 
>>>   com.biz
>>>   app
>>>   1.0
>>>   
>>>   
>>>   *
>>>   *
>>>   
>>>   
>>> 
>>> 
>>> As Maven assumes transitive dependencies and buildr assumes no
>>> transitive dependencies.
>> 
>> 
>> -- 
>> Cheers,
>> 
>> Peter Donald
> 



BUILDR-572: Allow to upload unique version (timestamp based) snapshot artifacts to a repository

2016-08-14 Thread Antoine Toulme
See discussion here:
https://issues.apache.org/jira/browse/BUILDR-572 


> Brice, good stuff! I'm tempted to make snapshot-timestamping default instead 
> of an opt-in option. I'll take this discussion to the mailing list first.

I agree with Alex, this is the behavior users have come to expect from the 
build.

Anybody with a different opinion?

Thanks,

Antoine

Update on development for 1.5

2016-05-20 Thread Antoine Toulme
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

Green build

2016-05-03 Thread Antoine Toulme
We have a green build! It only passes with Oracle JDK though. I filed a bug for 
Arton to look at it:
https://github.com/arton/rjb/issues/44 

We might have to downgrade RJB back to 1.5.1.

Cheers,

Antoine

Re: [DISCUSS] Only support official supported Ruby versions

2016-05-01 Thread Antoine Toulme
Can we do this?
-1.4.x is the stable stream with 1.8.7 support (JRuby 1.6.7.2)
-1.5.x is MRI 2.2.5, 2.3.1, JRuby 1.7.25 and Jruby 9.0.5.0.

Also looking at Travis:
JDK6 for 1.4.x. stream
JDK7 for 1.4.x and 1.5.x
JDK8 for 1.5.x and going forward


> On Apr 30, 2016, at 2:26 PM, Peter Donald <pe...@realityforge.org> wrote:
> 
> On Sun, May 1, 2016 at 5:00 AM, Antoine Toulme <anto...@lunar-ocean.com> 
> wrote:
>> I would like to look into dropping all versions of Ruby except for the ones 
>> officially supported. Looking at MRI, this means 2.1.9, 2.2.5 and 2.3.1.
>> For JRuby, that is 1.7.25 and 9.0.50.
>> 
>> Does that make sense?
> 
> It makes sense however we are stuck supporting jruby-1.6.7.2 as we use
> buildr for several 2.x rails apps so I would like to support that as
> well ... assuming it is not too much work.
> 
> -- 
> Cheers,
> 
> Peter Donald



[DISCUSS] Scala support

2016-04-30 Thread Antoine Toulme
Hi all,

an other discussion thread, this time on Scala support.

Does it make sense to move to 2.11.8, or should we move to the latest 2.12 
milestone? I would like to shoot for the latter.

We are still using JDK7 for now but need to think of moving to JDK8 soon.

With version 1.5, we can make the jump.

Any feedback is welcome!

Antoine

[DISCUSS] Only support official supported Ruby versions

2016-04-30 Thread Antoine Toulme
Hi all,

I would like to look into dropping all versions of Ruby except for the ones 
officially supported. Looking at MRI, this means 2.1.9, 2.2.5 and 2.3.1.
For JRuby, that is 1.7.25 and 9.0.50.

Does that make sense?

Cheers,

Antoine

[ANNOUNCE] Apache Buildr 1.4.25 released

2016-04-29 Thread Antoine Toulme
Apache Buildr is a build system for Java-based applications, including support
for Scala, Groovy and a growing number of JVM languages and tools.  We wanted
something that's simple and intuitive to use, so we only need to tell it what
to do, and it takes care of the rest.  But also something we can easily extend
for those one-off tasks, with a language that's a joy to use.


New in this release:

  * Change: BUILDR-712 Update jruby-openssl dependency version or support a 
range of versions
  * Change: Update gwt addon to add the GWT artifacts to project dependencies 
as specs rather
than files.
  * Change: Support the project.root_project utility method to retrieve the top 
level project.


To learn more about Buildr and get started:
http://buildr.apache.org/

Thanks!
The Apache Buildr Team

[VOTE] Buildr 1.4.25 release

2016-04-19 Thread Antoine Toulme
We're voting on the source distributions available here:
http://home.apache.org/~toulmean/buildr/1.4.25/dist/

Specifically:
http://home.apache.org/~toulmean/buildr/1.4.25/dist/buildr-1.4.25.tgz
http://home.apache.org/~toulmean/buildr/1.4.25/dist/buildr-1.4.25.zip

The documentation generated for this release is available here:
http://home.apache.org/~toulmean/buildr/1.4.25/site/
http://home.apache.org/~toulmean/buildr/1.4.25/site/buildr.pdf

The following changes were made since 1.4.24:

  * Change: BUILDR-712 Update jruby-openssl dependency version or support a 
range of versions
  * Change: Update gwt addon to add the GWT artifacts to project dependencies 
as specs rather
than files.
  * Change: Support the project.root_project utility method to retrieve the top 
level project.

1.4.25 release

2016-04-05 Thread Antoine Toulme
I would like to cut a release at the end of the month, as users have asked
for an immediate fix to the JRuby OpenSSL update (BUILDR-712).

Does that make sense?


Re: Site publication broken

2016-03-29 Thread Antoine Toulme
… and we’re back! The site is now updated as of 1.4.24.

Now we need to:
-check why mirrors are not populated with downloads.
-check the new process for hosting RCs (hosting on home.apache.org is frown 
upon).

> On Mar 29, 2016, at 10:40 AM, Antoine Toulme <anto...@lunar-ocean.com> wrote:
> 
> Looks like the site publication doesn’t work. I tried to run “rake publish” 
> but the site is not updating.
> 
> I am looking into the situation and might pull infra in if needed, I’ll let 
> you know when things clear up.
> 
> Antoine



[ANNOUNCE] Apache Buildr 1.4.24 released

2016-03-28 Thread Antoine Toulme
Apache Buildr is a build system for Java-based applications, including support
for Scala, Groovy and a growing number of JVM languages and tools.  We wanted
something that's simple and intuitive to use, so we only need to tell it what
to do, and it takes care of the rest.  But also something we can easily extend
for those one-off tasks, with a language that's a joy to use.


New in this release:

  * Added:  Support the :no_invoke parameter being passed to Buildr.project() 
and
Buildr.projects() to avoid attempting to call invoke when 
retrieving the projects.
  * Added:  Add `exclude_paths` setting to pmd addon to allow paths to be 
explicitly excluded.
  * Fixed:  Update jDepend addon to ensure target directories are invoked prior 
to attempting
to analyze directories.
  * Added:  Add jdepend.additional_project_names configuration to jDepend addon 
to
ease merging in the source paths from multiple projects into one 
jDepend task.
  * Added:  Add findbugs.additional_project_names configuration to Findbugs 
addon to
ease merging in the source paths from multiple projects into one 
Findbugs task.
  * Added:  Add checkstyle.additional_project_names configuration to Checkstyle 
addon to
ease merging in the source paths from multiple projects into one 
Checkstyle task.
  * Added:  Add pmd.additional_project_names configuration to PMD addon to ease 
merging in
the source paths from multiple projects into one PMD task.
  * Fixed:  In the PMD addon, check that the source directory exists before 
adding to
sources directories to include.
  * Fixed:  BUILDR-709 - Fix "Exception in jacoco.rb [TypeError : can't convert 
Array into
String]". Submitted By Ross Mahony.
  * Added:  Define the 'activate_jruby_facet' addon that activates the jruby 
facet in
generated IDEA project modules.
  * Change: Update the Intellij IDEA plugin to support marking directories as 
generated.
  * Change: Update the Intellij IDEA plugin to correctly identify project paths 
as resource
directories.
  * Change: Update the default GWT version used in the GWT addon to the latest 
release 2.7.0.
  * Fixed:  Fix GWT addon to explicitly add gwt-dev artifact to gwt compile 
path now that
the bug that allowed unintended sharing has been fixed.
  * Fixed:  Fix bug in IDEA module generation that resulted in dependencies in 
IDEA module
using shared references to compile dependencies.
  * Change: Update the checkstyle addon to use checkstyle 6.12.1.


To learn more about Buildr and get started:
http://buildr.apache.org/

Thanks!
The Apache Buildr Team

Re: [VOTE] Buildr 1.4.24 release

2016-03-28 Thread Antoine Toulme
The vote is now closed. We have 2 +1 votes, binding, from Antoine Toulme and 
Peter Donald.

Thanks everybody! I’m pushing the bits and getting ready for 1.4.25 and 1.5.
 
> On Mar 23, 2016, at 3:04 PM, Antoine Toulme <anto...@lunar-ocean.com> wrote:
> 
> I will keep the vote open for another 24h. So far we have 2 +1s.
> 
>> On Mar 19, 2016, at 11:58 PM, Antoine Toulme <anto...@lunar-ocean.com> wrote:
>> 
>> OK, here is my +1.
>> 
>>> On Mar 19, 2016, at 10:29 PM, Antoine Toulme <anto...@toulme.name> wrote:
>>> 
>>> I rebased off your fix and released a new RC.
>>> 
>>> I still need to try a few examples of my own before I vote.
>>> 
>>> 
>>>> On Mar 19, 2016, at 2:30 AM, Peter Donald <pe...@realityforge.org> wrote:
>>>> 
>>>> Hi,
>>>> 
>>>> I ran through 14 projects that used different sets of plugins and
>>>> found one bug and pushed a fix for bug. Once that fix is in I am +1 on
>>>> the release.
>>>> 
>>>> On Wed, Mar 16, 2016 at 2:53 PM, Antoine Toulme <anto...@lunar-ocean.com> 
>>>> wrote:
>>>>> We're voting on the source distributions available here:
>>>>> http://home.apache.org/~toulmean/buildr/1.4.24/dist/
>>>>> 
>>>>> Specifically:
>>>>> http://home.apache.org/~toulmean/buildr/1.4.24/dist/buildr-1.4.24.tgz
>>>>> http://home.apache.org/~toulmean/buildr/1.4.24/dist/buildr-1.4.24.zip
>>>>> 
>>>>> The documentation generated for this release is available here:
>>>>> http://home.apache.org/~toulmean/buildr/1.4.24/site/
>>>>> http://home.apache.org/~toulmean/buildr/1.4.24/site/buildr.pdf
>>>>> 
>>>>> The following changes were made since 1.4.23:
>>>>> 
>>>>> * Added:  Support the :no_invoke parameter being passed to 
>>>>> Buildr.project() and
>>>>> Buildr.projects() to avoid attempting to call invoke when 
>>>>> retrieving the projects.
>>>>> * Added:  Add `exclude_paths` setting to pmd addon to allow paths to be 
>>>>> explicitly excluded.
>>>>> * Fixed:  Update jDepend addon to ensure target directories are invoked 
>>>>> prior to attempting
>>>>> to analyze directories.
>>>>> * Added:  Add jdepend.additional_project_names configuration to jDepend 
>>>>> addon to
>>>>> ease merging in the source paths from multiple projects into one 
>>>>> jDepend task.
>>>>> * Added:  Add findbugs.additional_project_names configuration to Findbugs 
>>>>> addon to
>>>>> ease merging in the source paths from multiple projects into one 
>>>>> Findbugs task.
>>>>> * Added:  Add checkstyle.additional_project_names configuration to 
>>>>> Checkstyle addon to
>>>>> ease merging in the source paths from multiple projects into one 
>>>>> Checkstyle task.
>>>>> * Added:  Add pmd.additional_project_names configuration to PMD addon to 
>>>>> ease merging in
>>>>> the source paths from multiple projects into one PMD task.
>>>>> * Fixed:  In the PMD addon, check that the source directory exists before 
>>>>> adding to
>>>>> sources directories to include.
>>>>> * Fixed:  BUILDR-709 - Fix "Exception in jacoco.rb [TypeError : can't 
>>>>> convert Array into
>>>>> String]". Submitted By Ross Mahony.
>>>>> * Added:  Define the 'activate_jruby_facet' addon that activates the 
>>>>> jruby facet in
>>>>> generated IDEA project modules.
>>>>> * Change: Update the Intellij IDEA plugin to support marking directories 
>>>>> as generated.
>>>>> * Change: Update the Intellij IDEA plugin to correctly identify project 
>>>>> paths as resource
>>>>> directories.
>>>>> * Change: Update the default GWT version used in the GWT addon to the 
>>>>> latest release 2.7.0.
>>>>> * Fixed:  Fix GWT addon to explicitly add gwt-dev artifact to gwt compile 
>>>>> path now that
>>>>> the bug that allowed unintended sharing has been fixed.
>>>>> * Fixed:  Fix bug in IDEA module generation that resulted in dependencies 
>>>>> in IDEA module
>>>>> using shared references to compile dependencies.
>>>>> * Change: Update the checkstyle addon to use checkstyle 6.12.1.
>>>> 
>>>> 
>>>> 
>>>> -- 
>>>> Cheers,
>>>> 
>>>> Peter Donald
>>> 
>> 
> 



Re: Managing versions in Jira

2016-03-24 Thread Antoine Toulme
No dice. I get a page that says: 
You cannot edit the configuration of this project.

> On Mar 24, 2016, at 2:04 PM, Peter Donald <pe...@realityforge.org> wrote:
> 
> Hi,
> 
> 
> 
> On Thu, Mar 24, 2016 at 9:01 AM, Antoine Toulme <anto...@lunar-ocean.com> 
> wrote:
>> I’d like to manage versions in Jira. Some of them need to be marked 
>> released. I think I don’t have rights to manage versions. I believe I did in 
>> the past.
> 
> I had a look around and I thought I was in the same boat. It seems
> that the Jira api has changed significantly from the versions I have
> used in the past. So I found it with a bit of browsing around. Can you
> access the following?
> 
> https://issues.apache.org/jira/plugins/servlet/project-config/BUILDR/versions
> 
> 
> Anyhoo - I marked all the historic versions as released and archived
> all the versions from 2014 and earlier.
> 
> -- 
> Cheers,
> 
> Peter Donald



smime.p7s
Description: S/MIME cryptographic signature


Re: [VOTE] Buildr 1.4.24 release

2016-03-23 Thread Antoine Toulme
I will keep the vote open for another 24h. So far we have 2 +1s.

> On Mar 19, 2016, at 11:58 PM, Antoine Toulme <anto...@lunar-ocean.com> wrote:
> 
> OK, here is my +1.
> 
>> On Mar 19, 2016, at 10:29 PM, Antoine Toulme <anto...@toulme.name> wrote:
>> 
>> I rebased off your fix and released a new RC.
>> 
>> I still need to try a few examples of my own before I vote.
>> 
>> 
>>> On Mar 19, 2016, at 2:30 AM, Peter Donald <pe...@realityforge.org> wrote:
>>> 
>>> Hi,
>>> 
>>> I ran through 14 projects that used different sets of plugins and
>>> found one bug and pushed a fix for bug. Once that fix is in I am +1 on
>>> the release.
>>> 
>>> On Wed, Mar 16, 2016 at 2:53 PM, Antoine Toulme <anto...@lunar-ocean.com> 
>>> wrote:
>>>> We're voting on the source distributions available here:
>>>> http://home.apache.org/~toulmean/buildr/1.4.24/dist/
>>>> 
>>>> Specifically:
>>>> http://home.apache.org/~toulmean/buildr/1.4.24/dist/buildr-1.4.24.tgz
>>>> http://home.apache.org/~toulmean/buildr/1.4.24/dist/buildr-1.4.24.zip
>>>> 
>>>> The documentation generated for this release is available here:
>>>> http://home.apache.org/~toulmean/buildr/1.4.24/site/
>>>> http://home.apache.org/~toulmean/buildr/1.4.24/site/buildr.pdf
>>>> 
>>>> The following changes were made since 1.4.23:
>>>> 
>>>> * Added:  Support the :no_invoke parameter being passed to 
>>>> Buildr.project() and
>>>>  Buildr.projects() to avoid attempting to call invoke when 
>>>> retrieving the projects.
>>>> * Added:  Add `exclude_paths` setting to pmd addon to allow paths to be 
>>>> explicitly excluded.
>>>> * Fixed:  Update jDepend addon to ensure target directories are invoked 
>>>> prior to attempting
>>>>  to analyze directories.
>>>> * Added:  Add jdepend.additional_project_names configuration to jDepend 
>>>> addon to
>>>>  ease merging in the source paths from multiple projects into one 
>>>> jDepend task.
>>>> * Added:  Add findbugs.additional_project_names configuration to Findbugs 
>>>> addon to
>>>>  ease merging in the source paths from multiple projects into one 
>>>> Findbugs task.
>>>> * Added:  Add checkstyle.additional_project_names configuration to 
>>>> Checkstyle addon to
>>>>  ease merging in the source paths from multiple projects into one 
>>>> Checkstyle task.
>>>> * Added:  Add pmd.additional_project_names configuration to PMD addon to 
>>>> ease merging in
>>>>  the source paths from multiple projects into one PMD task.
>>>> * Fixed:  In the PMD addon, check that the source directory exists before 
>>>> adding to
>>>>  sources directories to include.
>>>> * Fixed:  BUILDR-709 - Fix "Exception in jacoco.rb [TypeError : can't 
>>>> convert Array into
>>>>  String]". Submitted By Ross Mahony.
>>>> * Added:  Define the 'activate_jruby_facet' addon that activates the jruby 
>>>> facet in
>>>>  generated IDEA project modules.
>>>> * Change: Update the Intellij IDEA plugin to support marking directories 
>>>> as generated.
>>>> * Change: Update the Intellij IDEA plugin to correctly identify project 
>>>> paths as resource
>>>>  directories.
>>>> * Change: Update the default GWT version used in the GWT addon to the 
>>>> latest release 2.7.0.
>>>> * Fixed:  Fix GWT addon to explicitly add gwt-dev artifact to gwt compile 
>>>> path now that
>>>>  the bug that allowed unintended sharing has been fixed.
>>>> * Fixed:  Fix bug in IDEA module generation that resulted in dependencies 
>>>> in IDEA module
>>>>  using shared references to compile dependencies.
>>>> * Change: Update the checkstyle addon to use checkstyle 6.12.1.
>>> 
>>> 
>>> 
>>> -- 
>>> Cheers,
>>> 
>>> Peter Donald
>> 
> 



[VOTE] Buildr 1.4.24 release

2016-03-15 Thread Antoine Toulme
We're voting on the source distributions available here:
http://home.apache.org/~toulmean/buildr/1.4.24/dist/

Specifically:
http://home.apache.org/~toulmean/buildr/1.4.24/dist/buildr-1.4.24.tgz
http://home.apache.org/~toulmean/buildr/1.4.24/dist/buildr-1.4.24.zip

The documentation generated for this release is available here:
http://home.apache.org/~toulmean/buildr/1.4.24/site/
http://home.apache.org/~toulmean/buildr/1.4.24/site/buildr.pdf

The following changes were made since 1.4.23:

  * Added:  Support the :no_invoke parameter being passed to Buildr.project() 
and
Buildr.projects() to avoid attempting to call invoke when 
retrieving the projects.
  * Added:  Add `exclude_paths` setting to pmd addon to allow paths to be 
explicitly excluded.
  * Fixed:  Update jDepend addon to ensure target directories are invoked prior 
to attempting
to analyze directories.
  * Added:  Add jdepend.additional_project_names configuration to jDepend addon 
to
ease merging in the source paths from multiple projects into one 
jDepend task.
  * Added:  Add findbugs.additional_project_names configuration to Findbugs 
addon to
ease merging in the source paths from multiple projects into one 
Findbugs task.
  * Added:  Add checkstyle.additional_project_names configuration to Checkstyle 
addon to
ease merging in the source paths from multiple projects into one 
Checkstyle task.
  * Added:  Add pmd.additional_project_names configuration to PMD addon to ease 
merging in
the source paths from multiple projects into one PMD task.
  * Fixed:  In the PMD addon, check that the source directory exists before 
adding to
sources directories to include.
  * Fixed:  BUILDR-709 - Fix "Exception in jacoco.rb [TypeError : can't convert 
Array into
String]". Submitted By Ross Mahony.
  * Added:  Define the 'activate_jruby_facet' addon that activates the jruby 
facet in
generated IDEA project modules.
  * Change: Update the Intellij IDEA plugin to support marking directories as 
generated.
  * Change: Update the Intellij IDEA plugin to correctly identify project paths 
as resource
directories.
  * Change: Update the default GWT version used in the GWT addon to the latest 
release 2.7.0.
  * Fixed:  Fix GWT addon to explicitly add gwt-dev artifact to gwt compile 
path now that
the bug that allowed unintended sharing has been fixed.
  * Fixed:  Fix bug in IDEA module generation that resulted in dependencies in 
IDEA module
using shared references to compile dependencies.
  * Change: Update the checkstyle addon to use checkstyle 6.12.1.

New release

2016-03-14 Thread Antoine Toulme
Hey folks,

it’s been a while since the last release. There’s about a dozen changes in the 
CHANGELOG:
https://github.com/apache/buildr/blob/master/CHANGELOG 


I believe it would be a good time to run a release. With your permission, I’ll 
get started on rolling out a RC.

Cheers,

Antoine

Re: [VOTE] Buildr 1.4.23 release

2015-06-15 Thread Antoine Toulme
+1
 On Jun 12, 2015, at 6:26 AM, Peter Donald dona...@apache.org wrote:
 
 We're voting on the source distributions available here:
 http://people.apache.org/~donaldp/buildr/1.4.23/dist/
 
 Specifically:
 http://people.apache.org/~donaldp/buildr/1.4.23/dist/buildr-1.4.23.tgz
 http://people.apache.org/~donaldp/buildr/1.4.23/dist/buildr-1.4.23.zip
 
 The documentation generated for this release is available here:
 http://people.apache.org/~donaldp/buildr/1.4.23/site/
 http://people.apache.org/~donaldp/buildr/1.4.23/site/buildr.pdf
 
 The following changes were made since 1.4.22:
 
 * Change: BUILDR-706 - Update the checkstyle addon use checkstyle 6.6.
  Submitted by Dieter Vrancken.
 * Fixed:  Fix Buildr.rspec_present? so that it works under jruby 1.6.7.2
 * Change: BUILDR-705 - Avoid attempting to load rspec classes unless
  Buildr.rspec_present? returns true. Reported By rbpandey.
 * Fixed:  Remove debug output left in ipr.sql_dialect_mappings.



smime.p7s
Description: S/MIME cryptographic signature


Re: [VOTE] Buildr 1.4.21 release

2014-12-02 Thread Antoine Toulme
+1 for me. Sorry I didn't have time to test things this time around.

On Fri, Nov 28, 2014 at 4:28 PM, Peter Donald pe...@realityforge.org
wrote:

 Sounds like a plan. I just updated the version of Antwrap and updated the
 version at http://people.apache.org/~donaldp/buildr/1.4.21/dist/ and will
 run the tests over the next couple of hours.

 On Sat, Nov 29, 2014 at 12:42 AM, Pepijn Van Eeckhoudt 
 pep...@vaneeckhoudt.net wrote:

  Since you're doing small incremental improvements, Antoine integrated a
 PR
  for Antwrap that gets rid of deprecation warnings when used with Juby.
  Buildr under JRuby also prints these warnings every time it's run. Might
 be
  nice to bump the Antwrap dependency to resolve this.
 
  Pepijn
 
 
  On 28/11/14 14:11, Peter Donald wrote:
 
  Hi,
 
  This release does not really include anything other than small
 incremental
  improvements but I thought it would be good to get a another release
 out.
  FWIW the tests are all green [1] and I have tested it with all our our
  local builds.
 
  [1] https://travis-ci.org/apache/buildr
 
  On Sat, Nov 29, 2014 at 12:09 AM, Peter Donald pe...@realityforge.org
  wrote:
 
   We're voting on the source distributions available here:
  http://people.apache.org/~donaldp/buildr/1.4.21/dist/
 
  Specifically:
  http://people.apache.org/~donaldp/buildr/1.4.21/dist/buildr-1.4.21.tgz
  http://people.apache.org/~donaldp/buildr/1.4.21/dist/buildr-1.4.21.zip
 
  The documentation generated for this release is available here:
  http://people.apache.org/~donaldp/buildr/1.4.21/site/
  http://people.apache.org/~donaldp/buildr/1.4.21/site/buildr.pdf
 
  The following changes were made since 1.4.20:
 
 * Change: Update the gwt addon to add the validation dependencies
  required for GWT
   compiles without requiring that the user specify the
  dependency.
 * Change: Update ipr.add_gwt_configuration method to support GWT 2.7
  configuration
   parameters and IDEA 14 parameters.
 * Change: Upgrade jacoco to 0.7.2. Submitted by neher.
 * Change: Update checkstyle addon to use Checkstyle 6.0.
 * Added:  Updated the gwt addon to support the upcoming GWT 2.7.x
  release.
 * Change: Enhance ipr.add_glassfish_configuration to support the
  ability
  to
   define the version of GlassFish in uses. Change the
 default
  to
  4.1.0
   as that is the latest supported variant.
 * Fixed:  Change the name of the GlassFish install in
  ipr.add_glassfish_configuration
   to use the same convention that IDEA uses by default. i.e.
  Name the
   installation GlassFish 4.1.0 rather than Glassfish
  4.1.0.
 * Change: Change the default version of the jdk in IDEA project
 files
  to
  1.7.
 * Change: Change the default version of the IDEA project files
 created
  to the
   current release version 13. To revert to the older
 versions
  specify
   ipr.version = '12' in your buildfile.
 * Added:  Enhance the IdeaFile class to easily support mixing in of
  custom
   components from either the filesystem or from an artifact.
 * Change: Update rjb to version 1.5.1.
 * Added:  Update checkstyle addon to support downloading checkstyle
  checks
   as an artifact.
 * Added:  Update checkstyle addon to supply checkstyle.config.dir
  property.
 * Added:  Update pmd addon to support downloading rule files as an
  artifact.
 * Change: Update pmd addon to use pmd version 5.1.3.
 * Fixed:  BUILDR-702 - Retain Unix permission flags when merging
   zip files into another zip or tar archive. Submitted by
  Pepijn
  Van Eeckhoudt.
 
 
 
 
 


 --
 Cheers,

 Peter Donald



Re: [VOTE] Buildr 1.4.19 release

2014-07-06 Thread Antoine Toulme
+1


On Sat, Jul 5, 2014 at 6:12 PM, Peter Donald pe...@realityforge.org wrote:

 And this is a re-send with a correct subject line ;)

 We're voting on the source distributions available here:
 http://people.apache.org/~donaldp/buildr/1.4.19/dist/

 Specifically:
 http://people.apache.org/~donaldp/buildr/1.4.19/dist/buildr-1.4.19.tgz
 http://people.apache.org/~donaldp/buildr/1.4.19/dist/buildr-1.4.19.zip

 The documentation generated for this release is available here:
 http://people.apache.org/~donaldp/buildr/1.4.19/site/
 http://people.apache.org/~donaldp/buildr/1.4.19/site/buildr.pdf

 The following changes were made since 1.4.18:

   * Fixed:  BUILDR-700 - Ensure SNAPSHOT artifacts, constructed using the
 download(artifact('group:artifact:jar:1-SNAPSHOT') =
 'http://example.com/...') construct will correctly download
 the
 artifacts from configured URL.
   * Fixed:  BUILDR-700 - Fix bug where buildr was truncating SNAPSHOT files
 that had not changed since last update check and HTTP was
 returning
 HTTP Not Modified status.
   * Fixed:  Fix bug introduced in 1.4.18 version of custom_pom addon where
 poms are created for artifacts that have a classifier.


 --
 Cheers,

 Peter Donald



Re: [VOTE] Buildr 1.4.17 release

2014-05-25 Thread Antoine Toulme
+1. No testing from me - long week-end here.


On Sun, May 25, 2014 at 12:59 AM, Peter Donald pe...@realityforge.orgwrote:

 A few bugs were reported ... and fixed. A new candidate has been pushed up.

 --
 Cheers,

 Peter Donald



Re: [VOTE] Buildr 1.4.10 release

2013-02-19 Thread Antoine Toulme
+1 for the release, thanks for the hard work!


On Sun, Feb 10, 2013 at 2:30 AM, Peter Donald pe...@realityforge.orgwrote:

 We're voting on the source distributions available here:
 http://people.apache.org/~donaldp/buildr/1.4.10/dist/

 Specifically:
 http://people.apache.org/~donaldp/buildr/1.4.10/dist/buildr-1.4.10.tgz
 http://people.apache.org/~donaldp/buildr/1.4.10/dist/buildr-1.4.10.zip

 The documentation generated for this release is available here:
 http://people.apache.org/~donaldp/buildr/1.4.10/site/
 http://people.apache.org/~donaldp/buildr/1.4.10/site/buildr.pdf

 The following changes were made since 1.4.9:

   * Added:  Support a single intermediate directory for each project
 hierarchy
 through an addon 'buildr/single_intermediate_layout'.
   * Fixed:  BUILDR-660 possible build issue when using build.yaml and
 tasks/*.rake
 (Félix Enrique Llorente Pastora)
   * Added:  Support the :dir option in the Java::Commands.java method.
   * Fixed:  Scala 2.10 support - compiler now uses additional/separate jars
 introduced in 2.10 such as scala-reflect.jar and
 scala-actor.jar
   * Added:  Add an addon for NSIS.
   * Change: BUILDR-612 - Support the TestNG 6.x versions and default
 to 6.8.
   * Added:  BUILDR-599 - Support the passing of arguments to testng
 test runner.
   * Fixed:  Observer the per-project source version when generating
 IDEA module files.
   * Change: Sort the components in IDEA project files in the same
 order the idea sorts them.
   * Fixed:  Findbugs addon correctly handles String dependencies
 (vs task dependencies)
   * Fixed:  Checkstyle addon correctly handles String dependencies
 (vs task dependencies)
   * Added:  Created an addon 'buildr/wsgen' for generating wsdls from java
 and java from wsdls using the underlying wsgen tool.
   * Change: Defer the expansion of generated poms by wrapping the
 generation
 in a Proc.
   * Change: Rework Artifact.content(value) method to accept a Proc that
 will be called before the artifact is written rather than
 requiring a string.
   * Added:  Create a 'buildr/gpg' addon that signs and uploads signatures
 when uploading artifacts. Inspired by a similar extension in
 the Apache ODE project by Tammo van Lessen.
   * Change: Updated dependency versions;
 - jruby-openssl (0.8.2)
 - atoulme-Antwrap (0.7.4)
   * Change: Require 'bundler/setup' as part of buildr startup to ensure
 that
 buildr always runs with up to date dependencies if a Gemfile is
 present.
   * Added:  Add FrameworkDetectionExcludesConfiguration facet to Idea
 project
 file creation by default.
   * Fixed:  In the IntelliJ extension, defer the materialization of the
 default_components until expansion time to avoid loss of sub-
 components added after an add_component call.
   * Fixed:  BUILDR-633 - Remove hardcoded shebang lines in all-in-one
 release.
   * Added:  Create a simple extension that modifies the project layout to
 place
 generated files at the top level.

 --
 Cheers,

 Peter Donald



Re: [VOTE] Buildr 1.4.10 release

2013-02-11 Thread Antoine Toulme
It looks like the site is missing images ? The zip and tar.gz look good,
the PDF looks ok.

I haven't had time to play with the gem yet.


On Sun, Feb 10, 2013 at 2:30 AM, Peter Donald pe...@realityforge.orgwrote:

 We're voting on the source distributions available here:
 http://people.apache.org/~donaldp/buildr/1.4.10/dist/

 Specifically:
 http://people.apache.org/~donaldp/buildr/1.4.10/dist/buildr-1.4.10.tgz
 http://people.apache.org/~donaldp/buildr/1.4.10/dist/buildr-1.4.10.zip

 The documentation generated for this release is available here:
 http://people.apache.org/~donaldp/buildr/1.4.10/site/
 http://people.apache.org/~donaldp/buildr/1.4.10/site/buildr.pdf

 The following changes were made since 1.4.9:

   * Added:  Support a single intermediate directory for each project
 hierarchy
 through an addon 'buildr/single_intermediate_layout'.
   * Fixed:  BUILDR-660 possible build issue when using build.yaml and
 tasks/*.rake
 (Félix Enrique Llorente Pastora)
   * Added:  Support the :dir option in the Java::Commands.java method.
   * Fixed:  Scala 2.10 support - compiler now uses additional/separate jars
 introduced in 2.10 such as scala-reflect.jar and
 scala-actor.jar
   * Added:  Add an addon for NSIS.
   * Change: BUILDR-612 - Support the TestNG 6.x versions and default
 to 6.8.
   * Added:  BUILDR-599 - Support the passing of arguments to testng
 test runner.
   * Fixed:  Observer the per-project source version when generating
 IDEA module files.
   * Change: Sort the components in IDEA project files in the same
 order the idea sorts them.
   * Fixed:  Findbugs addon correctly handles String dependencies
 (vs task dependencies)
   * Fixed:  Checkstyle addon correctly handles String dependencies
 (vs task dependencies)
   * Added:  Created an addon 'buildr/wsgen' for generating wsdls from java
 and java from wsdls using the underlying wsgen tool.
   * Change: Defer the expansion of generated poms by wrapping the
 generation
 in a Proc.
   * Change: Rework Artifact.content(value) method to accept a Proc that
 will be called before the artifact is written rather than
 requiring a string.
   * Added:  Create a 'buildr/gpg' addon that signs and uploads signatures
 when uploading artifacts. Inspired by a similar extension in
 the Apache ODE project by Tammo van Lessen.
   * Change: Updated dependency versions;
 - jruby-openssl (0.8.2)
 - atoulme-Antwrap (0.7.4)
   * Change: Require 'bundler/setup' as part of buildr startup to ensure
 that
 buildr always runs with up to date dependencies if a Gemfile is
 present.
   * Added:  Add FrameworkDetectionExcludesConfiguration facet to Idea
 project
 file creation by default.
   * Fixed:  In the IntelliJ extension, defer the materialization of the
 default_components until expansion time to avoid loss of sub-
 components added after an add_component call.
   * Fixed:  BUILDR-633 - Remove hardcoded shebang lines in all-in-one
 release.
   * Added:  Create a simple extension that modifies the project layout to
 place
 generated files at the top level.

 --
 Cheers,

 Peter Donald



Re: ApacheCon / Thoughtworks TechRadar

2012-11-12 Thread Antoine Toulme
FWIW the all-in-one bundle was there before and Alex coded most if not all
of it :)

If I remember correctly, building the all-in-one is supported by a rake
task.


On Fri, Nov 9, 2012 at 7:04 PM, Peter Donald pe...@realityforge.org wrote:

 Huya,

 On Sat, Nov 10, 2012 at 5:21 AM, Tammo van Lessen tvanles...@gmail.com
 wrote:
  First, I got a Buildr talk accepted at ApacheCon EU in Sinsheim, Germany,
  which I held just yesterday.

 congrats!

  I got a lot of positive feedback, people seem
  to like the buildr idea although it also seems that Maven improved since
  the inception of Buildr and some things are less worse. The most visible
  argument against buildr was, however, that people are used to use Maven
 and
  that, if they want to make their project accessible for a broad audience,
  they think they'd need to stick to Maven.

 That does seem to be a common view.

  I guess Gradle tries to address
  this issue by providing a gradle-wrapper, which is a small jar file
 along
  a shell script that you can include into your project and that will
  bootstrap a gradle installation automatically. I also figured, that still
  many Java developers don't have rubies at hand and don't know how to
 easily
  install a gem.

 And one stage, Antoine was working on the all-in-one distribution
 that essentially bundled a version of jruby with buildr and all it's
 dependencies in one easy installer. I wonder if we could work on this
 to ease adoption of buildr for the casual user.

 Where I work we use Chef (http://www.opscode.com/chef/) extensively
 and they release their tool in omnibus editions that are essentially
 a complete version of ruby for n-different platforms. They preinstall
 the chef gems in the ruby they distribute but they make sure that the
 only things that are added to the path are the che executables. I
 wonder if this would be a good thing for us to consider?

  Second, I stumbled upon ThoughtWorks TechRadar [2]. In particular, I
 liked
  the first paragraph of the Tools section ;)

 It is kinda neat. Possibly the best thing we can do is to increase
 awareness ... I think your approach to giving a talk is a good idea.

 --
 Cheers,

 Peter Donald



Re: [VOTE] Buildr 1.4.9 release

2012-11-09 Thread Antoine Toulme
+1 (binding) as well.


On Fri, Nov 9, 2012 at 4:00 PM, Alex Boisvert alex.boisv...@gmail.comwrote:

 Ok, thanks for the info.  I haven't been able to reproduce myself.

 Here's my +1 (binding) for the release.

 alex

 On Thu, Nov 8, 2012 at 11:29 AM, Peter Donald pe...@realityforge.org
 wrote:

  Hi,
 
  I actually found it quite hard to reproduce. It seems to depend on the
  order in which the gems are installed and I seemed to be able to
  reproduce it by random touch commands in gem directory.
 
  However, a symptom is present on non windows boxes if you do something
 like
 
  $ cat  buildfile
  task X do
rm_rf 
  end
  ^D
  $ buildr X
 
  and you see a line like rm -rf XX then there may be an issue.
 
  I also observed that some times there was also problems with buildr
  install on windows boxes. (You would receive a ArgumentError for
  calling the install method).
 
  On Fri, Nov 9, 2012 at 3:03 AM, Alex Boisvert alex.boisv...@gmail.com
  wrote:
   Hi Peter,
  
   How does one go about testing/replicating the issue that was fixed?
  Just
   wondering if I can help confirm that it was fixed.
  
   alex
  
   On Thursday, November 8, 2012, Peter Donald wrote:
  
   It looks like there was an intermittent bug that bit some people in
 the
   last
   release so I thought I would start the release process for a new
 release
   with the required fix.
  
   We're voting on the source distributions available here:
   http://people.apache.org/~donaldp/buildr/1.4.9/dist/
  
   Specifically:
   http://people.apache.org/~donaldp/buildr/1.4.9/dist/buildr-1.4.9.tgz
   http://people.apache.org/~donaldp/buildr/1.4.9/dist/buildr-1.4.9.zip
  
   The documentation generated for this release is available here:
   http://people.apache.org/~donaldp/buildr/1.4.9/site/
   http://people.apache.org/~donaldp/buildr/1.4.9/site/buildr.pdf
  
   The following changes were made since 1.4.8:
  
 * Fixed:  Fixed the interaction with the FileUtils classes. The last
   release
   introduced a non-deterministic bug that sometimes caused
   logging
   preferences to be ignored and the install method to be
   inadvertently overwritten.
  
 
 
 
  --
  Cheers,
 
  Peter Donald
 



Re: [VOTE] Buildr 1.4.7 release

2012-05-28 Thread Antoine Toulme
 from :gem packaging
  type
   * Change: BUILDR-602 Fail the build when gem dependencies are missing
  rather than
 attempting to install the dependencies
   * Change: BUILDR-601 Remove Buildr::Util::Gems
   * Change: BUILDR-600 Centralize the common ad internal requires into one
  location.
   * Change: Upgrade to JRuby 1.6.2
   * Change: Move to Bundler to manage the project dependencies
   * Change: BUILDR-548 Remove support for JTestR as it is no longer
  maintained (Antoine Toulme)
   * Change: BUILDR-614 Buildr development - Using rvm, bundler and OSX
  installs the wrong rjb (Russell Teabeault)
   * Change: Upgrade to RJB 1.4.0
   * Fixed:  ArtifactNamespace fails when using artifacts with classfier.
   * Fixed:  Buildr.artifacts() should handle any object with :to_spec method
 (i.e., any object that ActsAsArtifact)
   * Fixed:  Handle HTTP Unauthorized (501) result code when downloading
  artifacts.
   * Fixed:  BUILDR-611 Buildr should not unnecessarily recompile Java files
 explicitly added to compile.from
   * Fixed:  scaladoc generation with scala 2.9.x
   * Fixed:  Bnd Plugin: Add each artifact individually as a prerequisite to
 bundle / package task when passed to classpath_element method
   * Fixed:  BUILDR-439 The command line is too long when running TestNG
  tests (Tammo Van Lessen)
   * Fixed:  BUILDR-595 Add option to specifiy location of ca cert
   * Fixed:  BUILDR-596 Update installation notes to talk about the
  all-in-one bundle
  
 
 
 
 
 -- 
 Cheers,
 
 Peter Donald 



Re: Releasing 1.4.7 -- was: [VOTE] Buildr 1.4.7 RC1

2012-02-08 Thread Antoine Toulme
Please go ahead. Our son showed up last week and I'm busy changing diapers
for the foreseeable future.

On Wed, Feb 8, 2012 at 08:07, Alex Boisvert alex.boisv...@gmail.com wrote:

 Antoine,

 If you don't mind, I'll take up the release and get started this week.
  We're far into overdue territory :)

 Pepijn:  can you file an issue with the JRuby/Rubygems warning you're
 seeing?  Just to make sure I can reproduce the same and address the issue.

 alex


 On Tue, Jan 31, 2012 at 5:28 AM, Pepijn Van Eeckhoudt 
 pep...@vaneeckhoudt.net wrote:

  Any news on the 1.4.7 release? 1.4.6 with JRuby 1.6.6 is giving me tons
 of
  rubygems related deprecation warnings which is rather annoying.
 
  Pepijn
 
 
  On 13/01/2012 20:32, Antoine Toulme wrote:
 
  I was hoping to come back here and give better news. Alas my time has
 run
  so scarce, I couldn't even come up with time to write up an email for
 the
  last months.
 
  I apologize for leaving this release open-ended. I have recently changed
  jobs (now a Rails developer at collaborative drug.com) and got a baby
 on
  the way.
 
  If you don't hear much from me in the coming months, don't panic :)
 
  I would like to try again releasing 1.4.7 before things get out of
 control
  at home. I'll give it a shot this weekend. Please let me know if you
 have
  objections.
 
  Cheers,
 
  Antoine
 
 
 
 
  On Fri, Nov 25, 2011 at 12:59, Antoine Toulmeanto...@lunar-ocean.com**
  wrote:
 
   OK, will do.
 
 
  On Fri, Nov 25, 2011 at 12:51, Alex Boisvertalex.boisvert@gmail.
 **comalex.boisv...@gmail.com
  wrote:
 
   Since we're voting on the source release, here's my +1.
 
  I believe the binary distros need to be re-generated -- at least the
  -java one.
 
  Antoine, you should run gem update --system and bundle update on
  your
  system to generate binaries that will install correctly.   I've done
 so
  on
  my system and now all the distros install cleanly (assuming latest
  rubygems
  is installed)
 
  alex
 
 
  On Fri, Nov 25, 2011 at 11:22 AM, Antoine Toulme
  anto...@lunar-ocean.com
 
  wrote:
  I am in favor of giving this vote one more week to conclude - with
  Thanksgiving, I didn't have time to run all tests yet.
 
  Please let me know if you favor a different solution.
 
  Antoine
 
  On Wed, Nov 23, 2011 at 13:35, Alex Boisvertalex.boisvert@gmail.
 **comalex.boisv...@gmail.com
 
  wrote:
  On Tue, Nov 22, 2011 at 6:05 PM, Peter Donald
 pe...@realityforge.org
 
  wrote:
  Hi,
 
  I attempted to get the packages at
  http:/people.apache.org/~**toulmean/buildr/1.4.7/dist/
 http://people.apache.org/~toulmean/buildr/1.4.7/dist/working but ran
  into some issues. I then did a blank rvm install and attempted
 again
  with no success. Here is what happened...
 
  $ wget
 
   http://people.apache.org/~**toulmean/buildr/1.4.7/dist/**
  buildr-1.4.7.gem
 http://people.apache.org/~toulmean/buildr/1.4.7/dist/buildr-1.4.7.gem
 
  $ rvm use ruby-1.8.7-p352
  $ gem install buildr-1.4.7.gem
  ERROR:  While executing gem ... (ArgumentError)
 Illformed requirement [#YAML::Syck::DefaultKey:**
  0x2b2e99223290
  2.0.23]
 
   Looks like a bug in rubygems (see below);  try running gem update
  --system.
 
  $ rvm install ruby-1.8.7-p352^C
  [...]
  $ rvm use 1.8.7-p352
  Using /home/boisvert/.rvm/gems/ruby-**1.8.7-p352
  $ gem -v
  1.6.2
  $ gem install buildr-1.4.7.gem
  ERROR:  While executing gem ... (ArgumentError)
  Illformed requirement [#YAML::Syck::DefaultKey:**
  0x7fdfa1c9c448
  2.0.23]
  $ gem update --system
  Fetching: rubygems-update-1.8.11.gem (100%)
  Installing RubyGems 1.8.11
  RubyGems 1.8.11 installed
  [...]
  $ gem install buildr-1.4.7.gem
  [...]
  Successfully installed buildr-1.4.7
  19 gems installed
 
 
   $ wget
 
   http://people.apache.org/~**toulmean/buildr/1.4.7/dist/**
  buildr-1.4.7-java.gem
 http://people.apache.org/~toulmean/buildr/1.4.7/dist/buildr-1.4.7-java.gem
 
 
  $ rvm use jruby-1.6.3
  $ gem install buildr-1.4.7-java.gemERROR:  While executing gem ...
  (NoMethodError)undefined method `call' for nil:NilClass
 
  Any ideas?
 
   Also a rubygems issue... although upgrading to 1.8.11 led to a
 
  different
 
  issue:
  https://github.com/carlhuda/**bundler/issues/1235
 https://github.com/carlhuda/bundler/issues/1235
 
  Not sure how to resolve this yet.
 
  alex
 
 
 
 



Releasing 1.4.7 -- was: [VOTE] Buildr 1.4.7 RC1

2012-01-13 Thread Antoine Toulme
I was hoping to come back here and give better news. Alas my time has run
so scarce, I couldn't even come up with time to write up an email for the
last months.

I apologize for leaving this release open-ended. I have recently changed
jobs (now a Rails developer at collaborative drug.com) and got a baby on
the way.

If you don't hear much from me in the coming months, don't panic :)

I would like to try again releasing 1.4.7 before things get out of control
at home. I'll give it a shot this weekend. Please let me know if you have
objections.

Cheers,

Antoine




On Fri, Nov 25, 2011 at 12:59, Antoine Toulme anto...@lunar-ocean.comwrote:

 OK, will do.


 On Fri, Nov 25, 2011 at 12:51, Alex Boisvert alex.boisv...@gmail.comwrote:

 Since we're voting on the source release, here's my +1.

 I believe the binary distros need to be re-generated -- at least the
 -java one.

 Antoine, you should run gem update --system and bundle update on your
 system to generate binaries that will install correctly.   I've done so on
 my system and now all the distros install cleanly (assuming latest rubygems
 is installed)

 alex


 On Fri, Nov 25, 2011 at 11:22 AM, Antoine Toulme anto...@lunar-ocean.com
  wrote:

 I am in favor of giving this vote one more week to conclude - with
 Thanksgiving, I didn't have time to run all tests yet.

 Please let me know if you favor a different solution.

 Antoine

 On Wed, Nov 23, 2011 at 13:35, Alex Boisvert alex.boisv...@gmail.com
 wrote:

  On Tue, Nov 22, 2011 at 6:05 PM, Peter Donald pe...@realityforge.org
  wrote:
 
   Hi,
  
   I attempted to get the packages at
   http:/people.apache.org/~toulmean/buildr/1.4.7/dist/ working but ran
   into some issues. I then did a blank rvm install and attempted again
   with no success. Here is what happened...
  
   $ wget
  
 http://people.apache.org/~toulmean/buildr/1.4.7/dist/buildr-1.4.7.gem
   $ rvm use ruby-1.8.7-p352
   $ gem install buildr-1.4.7.gem
   ERROR:  While executing gem ... (ArgumentError)
  Illformed requirement [#YAML::Syck::DefaultKey:0x2b2e99223290
   2.0.23]
  
 
  Looks like a bug in rubygems (see below);  try running gem update
  --system.
 
  $ rvm install ruby-1.8.7-p352^C
  [...]
  $ rvm use 1.8.7-p352
  Using /home/boisvert/.rvm/gems/ruby-1.8.7-p352
  $ gem -v
  1.6.2
  $ gem install buildr-1.4.7.gem
  ERROR:  While executing gem ... (ArgumentError)
  Illformed requirement [#YAML::Syck::DefaultKey:0x7fdfa1c9c448
  2.0.23]
  $ gem update --system
  Fetching: rubygems-update-1.8.11.gem (100%)
  Installing RubyGems 1.8.11
  RubyGems 1.8.11 installed
  [...]
  $ gem install buildr-1.4.7.gem
  [...]
  Successfully installed buildr-1.4.7
  19 gems installed
 
 
   $ wget
  
 
 http://people.apache.org/~toulmean/buildr/1.4.7/dist/buildr-1.4.7-java.gem
   $ rvm use jruby-1.6.3
   $ gem install buildr-1.4.7-java.gemERROR:  While executing gem ...
   (NoMethodError)undefined method `call' for nil:NilClass
  
   Any ideas?
  
 
  Also a rubygems issue... although upgrading to 1.8.11 led to a
 different
  issue:
  https://github.com/carlhuda/bundler/issues/1235
 
  Not sure how to resolve this yet.
 
  alex
 






Re: [VOTE] Buildr 1.4.7 RC1

2011-11-25 Thread Antoine Toulme
I am in favor of giving this vote one more week to conclude - with
Thanksgiving, I didn't have time to run all tests yet.

Please let me know if you favor a different solution.

Antoine

On Wed, Nov 23, 2011 at 13:35, Alex Boisvert alex.boisv...@gmail.comwrote:

 On Tue, Nov 22, 2011 at 6:05 PM, Peter Donald pe...@realityforge.org
 wrote:

  Hi,
 
  I attempted to get the packages at
  http:/people.apache.org/~toulmean/buildr/1.4.7/dist/ working but ran
  into some issues. I then did a blank rvm install and attempted again
  with no success. Here is what happened...
 
  $ wget
  http://people.apache.org/~toulmean/buildr/1.4.7/dist/buildr-1.4.7.gem
  $ rvm use ruby-1.8.7-p352
  $ gem install buildr-1.4.7.gem
  ERROR:  While executing gem ... (ArgumentError)
 Illformed requirement [#YAML::Syck::DefaultKey:0x2b2e99223290
  2.0.23]
 

 Looks like a bug in rubygems (see below);  try running gem update
 --system.

 $ rvm install ruby-1.8.7-p352^C
 [...]
 $ rvm use 1.8.7-p352
 Using /home/boisvert/.rvm/gems/ruby-1.8.7-p352
 $ gem -v
 1.6.2
 $ gem install buildr-1.4.7.gem
 ERROR:  While executing gem ... (ArgumentError)
 Illformed requirement [#YAML::Syck::DefaultKey:0x7fdfa1c9c448
 2.0.23]
 $ gem update --system
 Fetching: rubygems-update-1.8.11.gem (100%)
 Installing RubyGems 1.8.11
 RubyGems 1.8.11 installed
 [...]
 $ gem install buildr-1.4.7.gem
 [...]
 Successfully installed buildr-1.4.7
 19 gems installed


  $ wget
 
 http://people.apache.org/~toulmean/buildr/1.4.7/dist/buildr-1.4.7-java.gem
  $ rvm use jruby-1.6.3
  $ gem install buildr-1.4.7-java.gemERROR:  While executing gem ...
  (NoMethodError)undefined method `call' for nil:NilClass
 
  Any ideas?
 

 Also a rubygems issue... although upgrading to 1.8.11 led to a different
 issue:
 https://github.com/carlhuda/bundler/issues/1235

 Not sure how to resolve this yet.

 alex



Re: [VOTE] Buildr 1.4.7 RC1

2011-11-25 Thread Antoine Toulme
OK, will do.

On Fri, Nov 25, 2011 at 12:51, Alex Boisvert alex.boisv...@gmail.comwrote:

 Since we're voting on the source release, here's my +1.

 I believe the binary distros need to be re-generated -- at least the -java
 one.

 Antoine, you should run gem update --system and bundle update on your
 system to generate binaries that will install correctly.   I've done so on
 my system and now all the distros install cleanly (assuming latest rubygems
 is installed)

 alex


 On Fri, Nov 25, 2011 at 11:22 AM, Antoine Toulme 
 anto...@lunar-ocean.comwrote:

 I am in favor of giving this vote one more week to conclude - with
 Thanksgiving, I didn't have time to run all tests yet.

 Please let me know if you favor a different solution.

 Antoine

 On Wed, Nov 23, 2011 at 13:35, Alex Boisvert alex.boisv...@gmail.com
 wrote:

  On Tue, Nov 22, 2011 at 6:05 PM, Peter Donald pe...@realityforge.org
  wrote:
 
   Hi,
  
   I attempted to get the packages at
   http:/people.apache.org/~toulmean/buildr/1.4.7/dist/ working but ran
   into some issues. I then did a blank rvm install and attempted again
   with no success. Here is what happened...
  
   $ wget
   http://people.apache.org/~toulmean/buildr/1.4.7/dist/buildr-1.4.7.gem
   $ rvm use ruby-1.8.7-p352
   $ gem install buildr-1.4.7.gem
   ERROR:  While executing gem ... (ArgumentError)
  Illformed requirement [#YAML::Syck::DefaultKey:0x2b2e99223290
   2.0.23]
  
 
  Looks like a bug in rubygems (see below);  try running gem update
  --system.
 
  $ rvm install ruby-1.8.7-p352^C
  [...]
  $ rvm use 1.8.7-p352
  Using /home/boisvert/.rvm/gems/ruby-1.8.7-p352
  $ gem -v
  1.6.2
  $ gem install buildr-1.4.7.gem
  ERROR:  While executing gem ... (ArgumentError)
  Illformed requirement [#YAML::Syck::DefaultKey:0x7fdfa1c9c448
  2.0.23]
  $ gem update --system
  Fetching: rubygems-update-1.8.11.gem (100%)
  Installing RubyGems 1.8.11
  RubyGems 1.8.11 installed
  [...]
  $ gem install buildr-1.4.7.gem
  [...]
  Successfully installed buildr-1.4.7
  19 gems installed
 
 
   $ wget
  
 
 http://people.apache.org/~toulmean/buildr/1.4.7/dist/buildr-1.4.7-java.gem
   $ rvm use jruby-1.6.3
   $ gem install buildr-1.4.7-java.gemERROR:  While executing gem ...
   (NoMethodError)undefined method `call' for nil:NilClass
  
   Any ideas?
  
 
  Also a rubygems issue... although upgrading to 1.8.11 led to a different
  issue:
  https://github.com/carlhuda/bundler/issues/1235
 
  Not sure how to resolve this yet.
 
  alex
 





Re: [VOTE] Buildr 1.4.7 RC1

2011-11-22 Thread Antoine Toulme
Please let me know if it looks good on your end. It would be great to get
validation that it works for Scala projects (the new version brings in
support for 2.9.1).

Cheers,

Antoine

On Fri, Nov 18, 2011 at 20:00, Peter Donald pe...@realityforge.org wrote:

 It looks good so far but I plan on putting it through a larger suite
 of tests of Monday.

 Thanks for the good work!

 On Fri, Nov 18, 2011 at 6:06 PM, Antoine Toulme anto...@lunar-ocean.com
 wrote:
  Vote is opened for a week.
 
  We're voting on the source distributions available here:
  http:/people.apache.org/~toulmean/buildr/1.4.7/dist/
 
  Specifically:
  http:/people.apache.org/~toulmean/buildr/1.4.7/dist/buildr-1.4.7.tgz
  http:/people.apache.org/~toulmean/buildr/1.4.7/dist/buildr-1.4.7.zip
 
  The documentation generated for this release is available here:
  http:/people.apache.org/~toulmean/buildr/1.4.7/site/
  http:/people.apache.org/~toulmean/buildr/1.4.7/site/buildr.pdf
 
  The official specification against which this release was tested:
  http:/people.apache.org/~toulmean/buildr/1.4.7/site/specs.html
 
  Test coverage report:
  http:/people.apache.org/~toulmean/buildr/1.4.7/site/coverage/index.html
 
  1.4.7 (2011-11-17)
  * Added:  Add a Findbugs extension.
  * Added:  Add a Checkstyle extension.
  * Added:  Add a JavaNCSS extension.
  * Added:  Add a PMD extension.
  * Added:  MultiTest framework that allows combining multiple test
 frameworks
   for a single project.
  * Added:  Scala Specs2 framework support.
  * Added:  Buildr.transitive() now accepts hash with :scopes, :optional
 and
   :scopes_transitive parameters
  * Added:  Improved scala file change detection
   (to avoid recompiling  unnecessarily)
  * Added:  ScalaTest now automatically loads the Mockito library
  * Added:  Enhance the Intellij IDEA extension to support the addition of
  artifacts
   and configurations to the generated project file.
  * Added:  BUILDR-598 TestNG support for :groups and :excludegroups
  (Christopher Coco)
  * Added:  BUILDR-616 Buildr development - If using rvm a default .rvmrc
  file would be helpful (Russell Teabeault)
  * Change: Scala Specs upgraded to 1.6.9 if using Scala 2.9.1
  * Change: Scala 2.9.1 is now default
  * Change: Make it possible to parameterize the JDepend extension and
  control the
   projects that are included in the analysis and to enable support
  for
   loading a per project jdepend.properties.
  * Change: Parameterize the the directory where the top level cobertura
  tasks will generate
   reports. Specify using Buildr::Cobertura.report_dir = ''
  * Change: Stop pretty printing the Intellij IDEA project files to avoid
  IDEA breaking
   in the presence of non-normalized whitespace content.
  * Change: Change the Intellij IDEA extension to always rebuild the
 project
  files.
  * Change: Upgrade to require atoulme-Antwrap 0.7.2
  * Change: Changed the default output directory for Intellij IDEA
 extension
  to be
   _(:target, :main, :idea, :classes) from _(:target, :main, :java)
  and the
   default test output directory to be _(:target, :test, :idea,
  :classes)
   from _(:target, :test, :java)
  * Change: Upgrade to highline 1.6.2
  * Change: Upgrade to jekyll 0.11.0, jekylltask 1.1.0, RedCloth 4.2.7,
 rdoc
  3.8 for
   generating documentation
  * Change: Upgrade to require rubygems  1.8.6
  * Change: BUILDR-603 Remove install/uninstall actions from :gem packaging
  type
  * Change: BUILDR-602 Fail the build when gem dependencies are missing
  rather than
   attempting to install the dependencies
  * Change: BUILDR-601 Remove Buildr::Util::Gems
  * Change: BUILDR-600 Centralize the common ad internal requires into one
  location.
  * Change: Upgrade to JRuby 1.6.2
  * Change: Move to Bundler to manage the project dependencies
  * Change: BUILDR-548 Remove support for JTestR as it is no longer
  maintained (Antoine Toulme)
  * Change: BUILDR-614 Buildr development - Using rvm, bundler and OSX
  installs the wrong rjb (Russell Teabeault)
  * Change: Upgrade to RJB 1.3.7
  * Fixed:  ArtifactNamespace fails when using artifacts with classfier.
  * Fixed:  Buildr.artifacts() should handle any object with :to_spec
 method
   (i.e., any object that ActsAsArtifact)
  * Fixed:  Handle HTTP Unauthorized (501) result code when downloading
  artifacts.
  * Fixed:  BUILDR-611 Buildr should not unnecessarily recompile Java files
   explicitly added to compile.from
  * Fixed:  scaladoc generation with scala 2.9.x
  * Fixed:  Bnd Plugin: Add each artifact individually as a prerequisite to
   bundle / package task when passed to classpath_element method
  * Fixed:  BUILDR-439 The command line is too long when running TestNG
  tests (Tammo Van Lessen)
  * Fixed:  BUILDR-595 Add option to specifiy location of ca cert
  * Fixed:  BUILDR-596 Update installation notes to talk about the
 all-in-one

Moving to RJB 1.3.7 ?

2011-11-17 Thread Antoine Toulme
Hi folks,

it looks like the version of RJB we use is a bit outdated.

It would also effectively fix issues on Mac with RVM if we moved to the
latest version.

What do you think ?

Antoine


  1   2   3   >