Re: February 2021 board report

[Alex Boisvert]

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

Re: August board report

[Alex Boisvert]

LGTM, Antoine.  Thanks!

On Tue, Aug 6, 2019 at 12:47 AM Antoine Toulme  wrote:

> Hey everybody,
>
> I prepared the board report for August:
> https://cwiki.apache.org/confluence/display/BUILDR/August+2019+Board+Report
> <
> 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

Re: [VOTE] Buildr 1.5.8 release

[Alex Boisvert]

+1 thanks Donald!

On Sun, Jul 14, 2019, 7:55 AM Antoine Toulme  wrote:

> +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/`  <
> 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
>
>

Re: May board report

[Alex Boisvert]

LGTM.  Thanks Antoine.

On Sun, Apr 28, 2019 at 10:30 AM Antoine Toulme  wrote:

> 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 <
> https://cwiki.apache.org/confluence/display/BUILDR/May+2019+Board+Report>
>
> Cheers,
>
> Antoine

Re: [VOTE] Buildr 1.5.7 release

[Alex Boisvert]

+1!

On Fri, Feb 15, 2019, 7:19 PM 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: [Vote] Move to using GitBox/GitHub as our git repository

[Alex Boisvert]

+1

Agreed, nicer to use GitHub in general.

On Wed, Dec 12, 2018, 9:31 PM Olle Jonsson  +1 from me.
>
> Good for my workflow.
>
> > On 13 Dec 2018, at 00:26, Antoine Toulme  wrote:
> >
> > +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
> >
>

Re: [VOTE] Buildr 1.5.6 release

[Alex Boisvert]

+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: [VOTE] Buildr 1.5.4 release

[Alex Boisvert]

+1 from me too.

On Nov 29, 2017 12:04 AM, "Antoine Toulme"  wrote:

> 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

[Alex Boisvert]

+1 (not tested)

On Sep 24, 2017 3:02 PM, "Antoine Toulme"  wrote:

> +1
>
> > On Sep 24, 2017, at 3:03 PM, Antoine Toulme  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.
>
>

Re: [VOTE] Buildr 1.5.3 release

[Alex Boisvert]

+1

On May 18, 2017 9:34 PM, "Antoine Toulme"  wrote:

> +1 from me, changes look good.
>

Re: [VOTE] Buildr 1.5.1 release

[Alex Boisvert]

+1 on the release.

(I have done no testing.)

On Mar 12, 2017 2:16 PM, "Peter Donald"  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 
> 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
>

Re: Access to confluence

[Alex Boisvert]

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
> >>
>
>

Re: Access to confluence

[Alex Boisvert]

Peter - you can look for the "Space tools" dropdown in the lower left
corner of the UI, then select "Permissions".

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


On Wed, 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
>>
>
>

Re: Access to confluence

[Alex Boisvert]

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  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
>

Re: Buildr book

[Alex Boisvert]

Generally I don't think a book about our website is useful ... Has the book
ever sold?

On Aug 26, 2016 3:46 PM, "Peter Donald"  wrote:

> Hi,
>
> On Sat, Aug 27, 2016 at 3:14 AM, Antoine Toulme 
> wrote:
> > 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?
>
> If we do keep it, we should definitely update it.
>
> However I am inclined to remove it, I am not sure how easy it would be
> to keep it up to date with our releases. If need be we could figure
> out a mechanism to generate epubs as well as other formats during our
> build process and just publish it on our website.
>
> I guess the one advantage about publishing it to Amazon is that they
> would automagically update downstream clients.
>
> --
> Cheers,
>
> Peter Donald
>

Re: Update on development for 1.5

[Alex Boisvert]

Nice, thanks for bringing zinc back.

On Mon, Aug 15, 2016 at 11:38 PM, Antoine Toulme <anto...@toulme.name>
wrote:

> Just brought zinc back in. Had to do a little dancing around with a Java
> class to call out to the Scala main object.
>
> Here is the commit:
>
> [master 749acfe] Bring back zinc compiler, using the latest version and a
> runner class
>  5 files changed, 183 insertions(+), 5 deletions(-)
>  create mode 100644 lib/buildr/scala/org/apache/buildr/ZincRunner.class
>  create mode 100644 lib/buildr/scala/org/apache/buildr/ZincRunner.java
>
> > On Aug 15, 2016, at 4:49 PM, Antoine Toulme <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.
>
>

Buildr Status Report

[Alex Boisvert]

-
Attachment L: Report from the Apache Buildr Project  [Alex Boisvert]


Apache Buildr is a Ruby-based build system for Java-based applications,
including support for Scala, Groovy and a growing number of JVM languages
and tools.

Our last release (v1.4.25) happened on April 4th, 2016.

Development and community activity remains low, with only a handful of
emails and Jira updates on average every month (due to low activity,
activity tend to be "bursty" around releases). Our last committer/PMC
change happened in October 2013.

As reported in March, I (Alex Boisvert) have been thinking about stepping
down as PMC Chair for the Buildr project.  Following discussion, we have
determined Peter Donald is the best candidate replacement, being the most
active & sustained committer for the last few years.   Next step is to
vote on this and send the board a resolution.

Otherwise, we have no issues that require board attention

Re: [ANNOUNCE] Apache Buildr 1.4.25 released

[Alex Boisvert]

Thanks Antoine!  Happy to see you hacking on Buildr again.

On Fri, Apr 29, 2016 at 10:30 PM, Antoine Toulme 
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:
>
>   * 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

Re: [DISCUSS] Scala support

[Alex Boisvert]

On Sat, Apr 30, 2016 at 12:04 PM, Antoine Toulme 
wrote:

> 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.
>

Nobody is using 2.12 yet; so I think we should move to 2.11.x.


> 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.
>

Version 1.5 should support 2.10, 2.11 and 2.12.   (And support for 2.12
will require JDK 8, but we should still support 2.10 and 2.11 with JDK 7).

Agree with can drop support for JDK6.

Do we have motivation to target only JDK 8?   If so, what is it?

Re: [DISCUSS] Only support official supported Ruby versions

[Alex Boisvert]

Agree with have to move on ... many gems no longer maintained for 1.8.7.


On Sat, Apr 30, 2016 at 11:42 PM, Antoine Toulme 
wrote:

> 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 
> wrote:
> >
> > On Sun, May 1, 2016 at 5:00 AM, Antoine Toulme 
> 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
>
>

Re: 1.4.25 release

[Alex Boisvert]

Good with me too.
On Apr 5, 2016 4:16 PM, "Peter Donald"  wrote:

> On Wed, Apr 6, 2016 at 5:03 AM, Antoine Toulme 
> wrote:
> > 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?
>
> Works for me!
>
> --
> Cheers,
>
> Peter Donald
>

Re: [VOTE] Buildr 1.4.23 release

[Alex Boisvert]

+1 for release.

(I haven't tested yet due to issue I just posted about re: Yosemite upgrade)

On Fri, Jun 12, 2015 at 8: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.

Buildr OSX Yosemite (10.10.3)

[Alex Boisvert]

Since upgrading to OSX Yosemite (10.10.3), whenever I run buildr I get a
popup that says:

To open This Java application you need to install the legacy Java SE 6
runtime.
[More info...] [Ok]

My environment remains the same (AFAIK) and I have JAVA_HOME set to:

$ echo $JAVA_HOME
/Library/Java/JavaVirtualMachines/jdk1.7.0_67.jdk/Contents/Home/

Any ideas?

Re: Buildr OSX Yosemite (10.10.3)

[Alex Boisvert]

Thanks.  I fixed my issue by creating the following two empty directories:

/System/Library/Java/JavaVirtualMachines/1.6.0.jdk
/System/Library/Java/Support/Deploy.bundle

(The hint came from http://stackoverflow.com/a/29800140/199174)

On Sun, Jun 14, 2015 at 11:09 AM, Michael michael.guy...@gmail.com wrote:

 I stumbled upon this the other day. The installers for Mac (from Oracle)
 have JNI disabled. I don't have a link handy (on mobile), but tweaking the
 permission to include JNI fixes the popup.
 On Jun 14, 2015 11:15 AM, Alex Boisvert alex.boisv...@gmail.com wrote:

  Since upgrading to OSX Yosemite (10.10.3), whenever I run buildr I get a
  popup that says:
 
  To open This Java application you need to install the legacy Java SE 6
  runtime.
  [More info...] [Ok]
 
  My environment remains the same (AFAIK) and I have JAVA_HOME set to:
 
  $ echo $JAVA_HOME
  /Library/Java/JavaVirtualMachines/jdk1.7.0_67.jdk/Contents/Home/
 
  Any ideas?
 

Re: [VOTE] Buildr 1.4.20 release

[Alex Boisvert]

+1 for release.

I've tested the (previous-to-last) release candidate on Linux (Ubuntu
14.04).


On Mon, Aug 25, 2014 at 2:14 PM, Peter Donald pe...@realityforge.org
wrote:

 Hi,

 I merged in that pull request, tested it locally and pushed a new
 release candidate up. If you could verify the package works as
 expected that would be great..

 On Mon, Aug 25, 2014 at 9:35 PM, Pepijn Van Eeckhoudt
 pep...@vaneeckhoudt.net wrote:
  Hi Peter,
 
  Is it too late to sneak https://github.com/apache/buildr/pull/14 in?
 
  Thanks,
 
  Pepijn
 
 
  On 2014-08-23 06:33, Peter Donald wrote:
 
  Hi,
 
  I would like to get this release out as soon as possible as the
  previous release has problems with the latest version of jruby which
  seems to have impacted a few people. I am also going offline after
  next Thursday and if possible it would be great to get a release out
  before then or have someone else pick up the release instead.
 
  Our CI builds [1] are looking much better and all green. But it would
  still be good to have people test this particular build across a
  number of environments.
 
  Thanks!
 
  [1] https://travis-ci.org/apache/buildr/builds/33342231
 
 
  On Sat, Aug 23, 2014 at 2:29 PM, Peter Donald pe...@realityforge.org
  wrote:
 
  We're voting on the source distributions available here:
  http://people.apache.org/~donaldp/buildr/1.4.20/dist/
 
  Specifically:
  http://people.apache.org/~donaldp/buildr/1.4.20/dist/buildr-1.4.20.tgz
  http://people.apache.org/~donaldp/buildr/1.4.20/dist/buildr-1.4.20.zip
 
  The documentation generated for this release is available here:
  http://people.apache.org/~donaldp/buildr/1.4.20/site/
  http://people.apache.org/~donaldp/buildr/1.4.20/site/buildr.pdf
 
  The following changes were made since 1.4.19:
 
 * Fixed : Work around bug/feature of jruby 1.7.13 that caches
  Gem::Version
   objects based on constructor parameters that causes issues
  with
   Buildr as we mutate the version objects through monkey
  patching.
 * Change: Upgrade rjb dependency to 1.4.9.
 * Change: BUILDR-701 - Update to JUnit 4.11. Submitted by
  Jean-Philippe Caruana.
 * Added:  Support the 'report_level' property on findbugs addon.
 * Change: Update the findbugs addon to use the 3.0.0 version of
  Findbugs.
 * Change: Update the findbugs addon to use the built-in findbugs
  stylesheet
   to generate the html report.
 * Fixed:  Ensure that the 'source_paths' and 'extra_dependencies'
  properties
   in the findbugs addon does not contain arrays or nils.
 * Fixed:  Ensure that the 'single_intermediate_layout' addon removes
  the top
   level target and reports directories during 'clean' phase.
 * Added:  Enhance idea project generation of ejb facet by looking
 for
  ejb
   descriptors in location compatible with ejb-jars.
 * Fixed:  Ensure that the 'source_paths' property in the pmd addon
  does not
   contain arrays or nils.
 
  --
  Cheers,
 
  Peter Donald
 
 
 
 



 --
 Cheers,

 Peter Donald

August board report

[Alex Boisvert]

FYI, I prepared our August board report:
https://cwiki.apache.org/confluence/display/BUILDR/August+2014+Board+Report

Feel free to edit/comment.  Will send to board@ in about 24 hours.

Curious if anybody has comments/feedback on the github integration so far.

Re: [VOTE] Buildr 1.4.19 release

[Alex Boisvert]

A belated +1 from me (since I just saw the release announcement)... I was
doing some basic testing with some projects on Ubuntu.


On Mon, Jul 7, 2014 at 9:48 AM, Tammo van Lessen tvanles...@gmail.com
wrote:

 +1


 On Sun, Jul 6, 2014 at 10:23 PM, Antoine Toulme anto...@lunar-ocean.com
 wrote:

  +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
  
 



 --
 Tammo van Lessen - http://www.taval.de

Re: [VOTE] Buildr 1.4.17 release

[Alex Boisvert]

+1.  No testing, currently vacationing.


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.16 release

[Alex Boisvert]

+1 in spirit for the release.  (I have not done any sort of testing.)


On Sun, May 4, 2014 at 9:27 AM, Tammo van Lessen tvanles...@gmail.comwrote:

 +1,
   Tammo


 On Sat, May 3, 2014 at 7:23 AM, Peter Donald pe...@realityforge.org
 wrote:

  Hi,
 
  It has been a long time since the last release. So I would
   like to put out a release with the accumulated fixes.
 
  We're voting on the source distributions available here:
  http://people.apache.org/~donaldp/buildr/1.4.16/dist/
 
  Specifically:
  http://people.apache.org/~donaldp/buildr/1.4.16/dist/buildr-1.4.16.tgz
  http://people.apache.org/~donaldp/buildr/1.4.16/dist/buildr-1.4.16.zip
 
  The documentation generated for this release is available here:
  http://people.apache.org/~donaldp/buildr/1.4.16/site/
  http://people.apache.org/~donaldp/buildr/1.4.16/site/buildr.pdf
 
  The following changes were made since 1.4.15:
 
* Added:  Add the ability to generate a html report when using the
  jacoco addon. Extracted from the ode project.
* Fixed:  Remove the projectname.ids file when rebuilding the idea
  project file avoiding conflict with idea.
* Fixed:  Avoid passing duplicate -keep parameters to wsimport from
  wsgen addon.
* Change: Improved the error handling when generating java from wsdl
  in the wsgen addon.
* Change: Upgraded the Checkstyle plugin to use checkstyle 5.7 that
  improves Java 7 compatibility.
* Added:  Add support for configuration of the schema-pattern,
  table-pattern and default-schemas settings in idea's
  data source definitions.
* Change: Upgraded the PMD plugin to use pmd 5.0.5 which for Java 7
  compatibility.
* Change: Derive the version of GWT in gwt addon from supplied
  dependencies.
* Fixed:  Include the compiled classes on path for GWT addon to
  ensure the GWT compiler can load annotations.
* Change: Derive the GWT version from build settings if not
  explicitly specified by GWT addon.
* Change: Support prefixing the version generated by the
  gwt_auto_version addon with the environment
  variable VERSION_PREFIX.
* Fixed:  Support overriding the GWT version used by the GWT addon.
* Fixed:  Fix problem when the :dependencies option was not
  passed to the GWT addon.
* Fixed:  Avoid crash in GPG addon if unable to create a pom
  for an artifact.
* Fixed:  Correct location of Git mirror in the README. Submitted
  by Marcos Sainz.
 



 --
 Tammo van Lessen - http://www.taval.de

Status report for the Buildr project

[Alex Boisvert]

-
Attachment H: Report from the Apache Buildr Project  [Alex Boisvert]

Apache Buildr is a Ruby-based build system for Java-based applications,
including support for Scala, Groovy and a growing number of JVM languages
and
tools.

Our last release (1.4.15) happened in November. Development and community
activity (mailing lists, bug reports, etc.) has been low since then. Our
last
committer/PMC changes happened in October.

In February, we discussed and agreed to move to git as our primary
version-control system, as well as turning on the improved GitHub
integration
(
https://blogs.apache.org/infra/entry/improved_integration_between_apache_and
).

We have no issues that require board attention.

Re: Improved integration between Apache and GitHub

[Alex Boisvert]

Hi Jim,

Not sure what you mean exactly.  Of course there's a difference between git
and GitHub... but we're talking specifically about GitHub integration.  See
the article linked on the original post:
https://blogs.apache.org/infra/entry/improved_integration_between_apache_and

I'm +1 for the integration too.

alex



On Fri, Feb 14, 2014 at 6:34 AM, Jim Jagielski j...@jagunet.com wrote:

 git != Gitub. ie: moving to git is not the same as
 using Github.
 On Feb 13, 2014, at 12:34 PM, Antoine Toulme anto...@lunar-ocean.com
 wrote:

  I would be delighted if we move to git and open ourselves to a wider
  audience of developers. You have my vote of course.
 
 
  On Wed, Feb 12, 2014 at 1:25 PM, Peter Donald pe...@realityforge.org
 wrote:
 
  Hi,
 
  The infrastructure team just announced [1] that they now support
  improved integration with GitHub. In a nutshell this means
 
  
  * Any Pull Request that gets opened, closed, reopened or commented on
  now gets recorded on the project's mailing list
  * If a project has a JIRA instance, any PRs or comments on PRs that
  include a JIRA ticket ID will trigger an update on that specific
  ticket
  * Replying to a GitHub comment on the dev@ mailing list will trigger a
  comment being placed on GitHub (yes, it works both ways!)
  
 
  If there is no objections I would like to see it turned on for Buildr.
 
  [1]
 
 https://blogs.apache.org/infra/entry/improved_integration_between_apache_and
 
  --
  Cheers,
 
  Peter Donald
 

New Committer: Tammo van Lessen

[Alex Boisvert]

Today is a day of announcements ... and I'm happy to also announce that
Tammo has been voted as new committer to the Buildr project.

Tammo has been active on the mailing list for a long time and has submitted
a number of quality patches (bug fixes + minor enhancements).   It's worth
nothing that Tammo continues to suppport our biggest known open-source
Buildfile [1] which is used in the Apache Ode project.

Welcome aboard Tammo!

[1] https://github.com/apache/ode/blob/master/Rakefile

Re: [VOTE] Buildr 1.4.14 release

[Alex Boisvert]

+1 for the release

with minimal testing on Ubuntu 13.04 with Ruby 1.8.7 and JRuby 1.7.5.


On Thu, Oct 10, 2013 at 12:52 PM, Peter Donald pe...@realityforge.org
wrote:

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

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

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

 The following changes were made since 1.4.13:

   * Change: Remove highline dependency.
   * Fixed:  BUILDR-682 - Fix the documentation for releasing using
 your own versioning scheme. Submitted by Jean-Philippe
 Caruana.
   * Fixed:  BUILDR-681 - Stop empty projects creating target/webapp.
   * Change: Add dependency from generated jws client source directory
 to the source wsdl in the wsgen addon.
   * Fixed:  Fixed regression in gwt addon due to pathing_jar
 functionality in Java::Commands.java.
   * Change: Support disabling the new pathing_jar functionality in
 Java::Commands.java utility method. Required for tools
 that introspect the classpath.
   * Change: Update wsgen addon to generate source into a directory
 hierarchy based on maven conventions.
   * Fixed:  Fixed regression using transitive dependencies due to
 presence of :scope option in Artifacts.to_hash.
   * Fixed:  Fixed bug in GWT addon that required that the user supply
 the :dependencies option.
   * Fixed:  Fixed bug in Intellij project file generation when adding
 a web facet.

Re: [VOTE] Buildr 1.4.13 release

[Alex Boisvert]

+1 (only minimally tested on Ubuntu 13.04 with Ruby 1.8.7 and JRuby 1.7.4)



On Tue, Oct 1, 2013 at 4:19 PM, Peter Donald pe...@realityforge.org wrote:

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

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

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

 The following changes were made since 1.4.12:

   * Added:  BUILDR-678 - Improve support for gpg signing artifacts
 using a single method.
   * Fixed:  BUILDR-677 - GPG addon hangs when .asc files are still in
 target. Submitted By Tammo van Lessen.
   * Added:  Initial support for data source creation in Intellij IDEA
 project files.
   * Fixed:  BUILDR-676 - Rework Java::Command:java so that it does not
 reject the :dir option. Reported by John Roth.
   * Added:  Auto-detect jpa provider in Intellij IDEA facet generation if
 persistence.xml file is present and provider not specified.
   * Added:  Auto-detect jruby version in Intellij IDEA facet generation if
 .ruby-version file is present.
   * Added:  Improve support for auto-detection of ejb and web descriptors
 within Intellij IDEA project generation.
   * Change: Default to setting the User-Agent header to Buildr-VERSION
 when accessing http resources. Maven Central rejects requests
 without a User-Agent string.
   * Change: Change default scope of dependencies to 'compile'. Submitted
 by Ingo Schmidt.
   * Change: BUILDR-675 - Set Cache-Control to 'no-cache' when downloading
 artifacts. Submitted by Félix Enrique Llorente Pastora.
   * Added:  Initial support for simple integration of an asset pipeline.
 See Compiling Assets section in the manual.
   * Fixed:  BUILDR-673 - Fix the option handling of the MultiTest test
 framework to behave as documented. Only the framework specific
 options are passed to the test. Submitted by John Roth.
   * Added:  BUILDR-672 - Persist the properties field in the checkstyle
 addon so that they can be modified by the user. Submitted
 by Wim C.
   * Fixed:  Make the package_as_* methods public so that the methods are
 detected in Ruby = 2.0.0 via the respond_to? method.
   * Change: Updated dependency versions;
 - rspec-expectations (2.14.3)
 - rspec-mocks (2.14.3)
 - rspec-core (2.14.5)
 - rspec (2.14.1)
 - minitar (0.5.4)
 - ci_reporter (1.8.4)
 - xml-simple (1.1.2)
 - rjb (1.4.8)
 - diff-lcs (1.2.4)
 - builder (3.2.2)
 - net-ssh (2.7.0)
 - net-sftp (2.1.2)
 - hoe (3.7.1)
 - json_pure (1.8.0)
 - highline (1.6.19)
   * Fixed:  BUILDR-668 - Specify File::FNM_EXTGLOB for include globs
 where needed in Ruby = 2.0.0. Reported by Yavor Nikolov.
   * Fixed:  Ensure generation of buildfiles from eclipse projects will
 finds .project files in Ruby = 2.0.0.
   * Fixed:  Patch Rake::FileList in Ruby = 2.0.0 to match dot files if
 a .* pattern is supplied as in earlier versions of ruby.
   * Fixed:  Make Archive-related operations (e.g. zip.merge) deterministic
 using
 OrderedHash.
   * Change: Update to TestNG 6.8.5.


 --
 Cheers,

 Peter Donald

Re: Dependencies and build order

[Alex Boisvert]

The scalac compiler understand java code and can perform mixed compilation
without specifying an order.

Basically, it goes in 3 phases if there are java files present

1) scalac compiler extract all java class/interface signatures
2) scalac compiler compiles all .scala files using extracted signatures
from #1
3) scalac compiler compiler all Java code (using compiled .scala classes
from #2)

so it doesn't matter if the Java code depends on Scala code or vice-versa.


On Tue, Jul 30, 2013 at 8:48 PM, Peter Donald pe...@realityforge.orgwrote:

 Hi,

 I don't use the scala plugin so this may be wrong but looking at the
 source, it seems that the scala compilers are responsible for
 compiling the java dependencies as well as the scala code. It seems
 that the only reason that the scala plugin also runs the javac
 compiler is to pick up java files that are not transitive dependencies
 of the scala code. Or thats what it looks like to me ...

 On Thu, Jul 25, 2013 at 6:14 PM, Marius Kjeldahl
 marius.kjeld...@gmail.com wrote:
  In the process of adding tests to my kawa module for buildr, I'm
 struggling
  with build order. The scala module that I've modelled my kawa module on
  seems to simply build the scala code first, then the java code for mixed
  mode compilation. The code can be found in scala/compiler.rb in the
 method
  compile_with_scalac.
 
  One of the tests that comes with the module then defines a java package
  Foo, and a scala package Bar, where Bar inherits from Foo.
 
  When I model my own compile_with_kawac method similar to the scala
 method,
  this test fails. The reason it fails is because the java module Foo
 hasn't
  been compiled when the kawa module Bar is being compiled.
 
  At first I suspected there might be something wrong in my compile_map
 code,
  but after looking at it, it seems that the method does not even try to
  figure out build order at all, only mapping from source file to class
 file.
 
  So how is build order decided in buildr?
 
  For this one test I added a workaround where I retry kawa compilation if
 it
  fails the first time, but considering that I'm doing everything in a
  simliar way and order as the scala module, there's got to be something
 I'm
  missing. Worst case, the scala compiler handles such dependencies itself.
 
  Anyway, figured I would ask, hoping somebody could clue me in.
 
  Thanks,
 
  Marius Kjeldahl



 --
 Cheers,

 Peter Donald

Re: Installing from source not working?

[Alex Boisvert]

Hi Marius,

Those instructions are obsolete ... sorry we haven't updated the page
recently.

I would advice doing:

% bundle install   # installs all the dependencies
% rake gem # create .gem from source
% gem install pkg/buildr-1.4.13.dev.gem  # or whichever other version (e.g.
java, mswin32)

Let me know if you need any other help!

alex


On Mon, Jul 22, 2013 at 5:59 AM, Marius Kjeldahl
marius.kjeld...@gmail.comwrote:

 I'm following the instructions on
 http://buildr.apache.org/contributing.html for
 trying to install from source, i.e. rake setup install, after checking
 the code out from the apache git repo. It seems rake is unable to find
 either task (setup, install). I'm looking at the Rakefile and can't find it
 either.

 I realize there are easier ways to install buildr, but I'm trying add
 support for building Kawa (a JVM based scheme) programs, and would prefer
 to do this using a base that at least works...

 Any ideas what I'm doing wrong, or what needs to be done to be able to
 build/install buildr from a local source tree?

 FWIW, I'm on Ubuntu Linux 13.04.

 Thanks,

 Marius K.

Status report for the Buildr project

[Alex Boisvert]

-
Attachment D: Report from the Apache Buildr Project  [Alex Boisvert]


Apache Buildr is a Ruby-based build system for Java-based applications,
including support for Scala, Groovy and a growing number of JVM languages
and tools.

Since the last report, we have released Buildr 1.4.11 that fixed a single
regression in v1.4.10.

We have also just voted for the release of Buildr 1.4.12; this release will
contain 5 enhancements, 4 bug fixes and 2 minor changes. 3 of these were
contributed by non-committers. The mailing lists remain relatively quiet.

Our last committer addition dates back to October 2010. Our last PMC
addition
dates back to September 2010, though we are currently in the voting process
to
add Peter Donald (our most active committer in the past 2 years) into our
PMC.

We have no issues that require board attention.

Re: [VOTE] Buildr 1.4.12 release

[Alex Boisvert]

+1


On Sat, May 4, 2013 at 11:49 AM, Antoine Toulme anto...@lunar-ocean.comwrote:

 +1, of course.


 On Sat, May 4, 2013 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.12/dist/
 
  Specifically:
  http://people.apache.org/~donaldp/buildr/1.4.12/dist/buildr-1.4.12.tgz
  http://people.apache.org/~donaldp/buildr/1.4.12/dist/buildr-1.4.12.zip
 
  The documentation generated for this release is available here:
  http://people.apache.org/~donaldp/buildr/1.4.12/site/
  http://people.apache.org/~donaldp/buildr/1.4.12/site/buildr.pdf
 
  The following changes were made since 1.4.11:
 
* Added:  BUILDR-648 Add new package(:test_jar) packaging type.
  Submitted by Mike Pettypiece.
* Fixed:  BUILDR-666 ZipFile.open modifies file regardless of usage.
  Reported by Pepijn Van Eeckhoudt, fix by Alex Boisvert.
* Change: Moved to using TravisCI to test the Linux variants.
* Added:  Make the location of the wsdl in generated source
 configurable
  in the wsgen addon.
* Added:  When generating the GWT facet for Intellij IDEA modules, use
  the gwt-dev maven artifact dependency if present as the SDK,
  falling back to the existing behaviour if not possible.
* Added:  Improved support for auto-detection of VCS dirs when creating
  IDEA projects.
* Added:  Added support for SuperDevMode in gwt addon and upgraded to
  GWT 2.5.1 by default.
* Change: BUILDR-664 Update Checkstyle addon so that extra_dependencies
  is
  empty by default. Submitted by Dieter Vrancken.
* Fixed:  BUILDR-663 require 'buildr' fails for Ruby 2.0.0.
* Fixed:  BUILDR-665 Java artifacts in build.yaml breaking ArchiveTask.
  Submitted by Antonio Pérez Barrero.
* Fixed:  BUILDR-662 reported time is much shorter than actual
 
 
 
  --
  Cheers,
 
  Peter Donald
 

Re: Buildr Release?

[Alex Boisvert]

Go for it.  +1


On Tue, Apr 30, 2013 at 2:38 AM, Peter Donald pe...@realityforge.orgwrote:

 Hi,

 I was thinking about starting the ball rolling for a release this
 weekend. In particular, I would like to see BUILDR-666 released as
 soon as possible. This has managed to speed up a whole bunch of our
 builds. Any objections?

 --
 Cheers,

 Peter Donald

Re: TravisCI for Buildr?

[Alex Boisvert]

I'm not going to provide very useful feedback since I've never used
TravisCI ... but I think it's a good idea.  Anything that saves us time and
gets to the same/better results is a good thing for the project.

A quick googling turned up Apache Jackrabbit using it:
https://travis-ci.org/apache/jackrabbit-oak



On Wed, Apr 17, 2013 at 3:20 PM, Peter Donald pe...@realityforge.orgwrote:

 Hi,

 So a couple of days ago I played around with TravisCI. TravisCI for
 those not familiar is a ci as a service offering that will run tests
 against github repositories. I have been experimenting withit in my
 account and you can see a sample (failed) build at [1]. I was curious
 - what do you think of using this for our Linux builds? I tend to
 spend a lot of time trying to care and feed Apaches CI infrastructure
 given how old it is. This would avoid the scenario altogether ...
 thoughts? Also is any other Apache projects using TravisCI?

 [1] https://travis-ci.org/realityforge/buildr/builds/6326113


 --
 Cheers,

 Peter Donald

Re: [VOTE] Buildr 1.4.11 release

[Alex Boisvert]

That was quick!

+1 for me (tested on Ubuntu 12.10).

On Thu, Mar 14, 2013 at 12:58 PM, Peter Donald pe...@realityforge.orgwrote:

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

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

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

 The following changes were made since 1.4.10:

   * Fixed:  Multiple tests in TestNG 6.x versions were being
 incorrectly passed to
 the command line application.



 --
 Cheers,

 Peter Donald

Re: Migration to Apache CMS svnpubsub

[Alex Boisvert]

Sweet.  Thanks for pushing on that!

On Wed, Mar 13, 2013 at 4:08 PM, Peter Donald pe...@realityforge.orgwrote:

 Hi,

 We have finally got our site into SvnPubSub so it should be relatively
 easy to update from now on.

 On Thu, Dec 13, 2012 at 4:58 AM, Alex Boisvert alex.boisv...@gmail.com
 wrote:
  Folks,
 
  The Apache infrastructure team are phasing out Confluence and rsync-based
  website publishing by the end of the year.  Related information can be
  found at http://www.apache.org/dev/project-site.html.
 
  Correspondingly, I've created an infrastructure task to migrate our
  Confluence content to Apache CMS and setup a SVN area for site
 publishing:
  https://issues.apache.org/jira/browse/INFRA-5632
 
  alex



 --
 Cheers,

 Peter Donald

Re: [VOTE] Buildr 1.4.10 release

[Alex Boisvert]

Is there a Jira for the TestNG issue?  (Or is it already fixed?)

I believe it's worth pushing a release to fix a non-trivial regression, yes.

alex

On Wed, Mar 13, 2013 at 4:11 PM, Peter Donald pe...@realityforge.orgwrote:

 Hi,

 On Thu, Feb 21, 2013 at 9:49 AM, Peter Donald pe...@realityforge.org
 wrote:
  On Wed, Feb 20, 2013 at 3:47 PM, Antoine Toulme anto...@lunar-ocean.com
 wrote:
  +1 for the release, thanks for the hard work!
 
  Great. So I have kicked off the start of the release but it looks like
  we can't update the website through the old mechanisms. So I have
  started the process of getting it into svnpubsub but it may take a day
  or two to get fully released.

 So the latest release has finally gone out and the website updated.
 Unfortunately it was released with a break to the TestNG test
 infrastructure. Do you think it is doing another quick release to fix
 this or should be just leave it to accumulate changes until the next
 release roles round?


 --
 Cheers,

 Peter Donald

Re: [VOTE] Buildr 1.4.10 release

[Alex Boisvert]

Here's my +1 for the release (vote on source package).

However, there's a minor issue on the .gem binaries ... I think the file
permissions are too restrictive which leads to this kind of problem after
install:

boisvert@smudge:~$ buildr
/usr/local/bin/buildr:23:in `load': no such file to load --
/var/lib/gems/1.8/gems/buildr-1.4.10/bin/buildr (LoadError)
from /usr/local/bin/buildr:23

boisvert@smudge:~/git/pixii$ ls -la
/var/lib/gems/1.8/gems/buildr-1.4.10/bin/buildr
-rwx--x--x 1 root root 885 Feb 16 08:05
/var/lib/gems/1.8/gems/buildr-1.4.10/bin/buildr

I think the permissions should include g+r and o+r as it was on previous
releases.

On Mon, Feb 11, 2013 at 12:35 PM, Peter Donald pe...@realityforge.orgwrote:

 Hi,

 On Tue, Feb 12, 2013 at 6:17 AM, Antoine Toulme anto...@lunar-ocean.com
 wrote:
  It looks like the site is missing images ?

 Oops - it looks like they were there but had bad permissions. Fixed now.

 --
 Cheers,

 Peter Donald

Re: Release Soon?

[Alex Boisvert]

HA!  Looks like our emails crossed.  I'm +1 for the release and happy if
you'd like to lead it.

On Wed, Jan 23, 2013 at 1:47 PM, Peter Donald pe...@realityforge.orgwrote:

 Hi,

 Would it be useful to do a release sometime soon? A few useful bug fixes
 have gone in, even if there has not been any major changes.

 I know that the CI jobs are intermittently failing, but I think that is
 mostly todo with problems on the build server rather than with buildr as
 such. I have run the tests locally and they all seem fine - I will look
 into the failures in about 10 days and then start a release vote if no one
 has any objections.

 --
 Cheers,

 Peter Donald

Re: Release Soon?

[Alex Boisvert]

Ok, I'll see if I can get started this weekend and tackle BUILDR-634.

On Wed, Jan 23, 2013 at 2:06 PM, Peter Donald pe...@realityforge.orgwrote:

 Hi,

 On Thu, Jan 24, 2013 at 8:53 AM, Alex Boisvert alex.boisv...@gmail.com
 wrote:

  HA!  Looks like our emails crossed.  I'm +1 for the release and happy if
  you'd like to lead it.
 

 I have nothing I need to add and wont get a chance to even start the
 release process till 5th or later so feel free to go for it.

 If you do go ahead then feel free to further refine the release scripts. I
 think I have got most of the things in place. However if you could also
 address BUILDR-634 at the same time that would be great ;)


 --
 Cheers,

 Peter Donald

Migration to Apache CMS svnpubsub

[Alex Boisvert]

Folks,

The Apache infrastructure team are phasing out Confluence and rsync-based
website publishing by the end of the year.  Related information can be
found at http://www.apache.org/dev/project-site.html.

Correspondingly, I've created an infrastructure task to migrate our
Confluence content to Apache CMS and setup a SVN area for site publishing:
https://issues.apache.org/jira/browse/INFRA-5632

alex

Re: buildr project website

[Alex Boisvert]

Cool, glad you like our website (credits go to Assaf Arkin who originally
designed it).

The Table of contents is generated through a small extension; you can see
the details here:
https://github.com/apache/buildr/blob/trunk/rakelib/doc.rake

alex

On Wednesday, November 28, 2012, Clark, Nick wrote:


 Hi all,

 I really like the clean website design and was thinking of using the
 source as a basis for one of my own open source projects. I cloned the
 project from GitHub and ran `jekyll --server` in the doc directory to
 render the site. It looks ok, but I do not get the automatically generated
 table of contents at the top of each page. Is there some kind of `toc`
 plugin that I'm missing?

 Sorry if this is a little off topic!

 Best,

 Nick

Status report for the Apache Buildr project

[Alex Boisvert]

-
Attachment G: Status report for the Apache Buildr Project

Apache Buildr is a Ruby-based build system for Java-based applications,
including support for Scala, Groovy and a growing number of JVM languages
and
tools.

We released Buildr 1.4.8 on November 1st containing 7 enhancements, 7 bug
fixes
and a few minor changes from 5 different contributors/committers. We
released a
subsequent hot-fix release (1.4.9) a week later to address a
non-deterministic
bug affecting some users. Thanks to the work of Peter Donald (committer), we
have continuous integration testing working again on Jenkins covering
multiple
versions of Ruby (1.8.7, 1.9.2, JRuby 1.7.0) and platforms (Linux, Windows)
and
our automated release scripts have been cleaned up.

The mailing lists remain relatively quiet and we continue to receive
contributions at a rate of about one per month on average.

We have no issues that require board attention.

Re: Moving _(:target, :generated) to top level of project

[Alex Boisvert]

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


 layout = Layout::Default.new
 layout[:target, :generated] = generated

 define myproject, :layout = layout do
   ...
   project.clean { rm_rf _(:target, :generated) }
 end

 The main reason for this seems to be ease of integration into IDEs.

 I only really use IntelliJs IDEA but I know that at least for that IDE
 we exclude the intermediate directory (i.e. _(:target) ) from the
 project and this makes it impossible to view the generated source in
 the IDE. So to enable development in the IDE they move it out of the
 target hierarchy.

 * Do you think we should make this the default?


We use target/generated because it's the Maven standard and the least
surprising for most people. Since it's the default, it's hard(er) to find
evidence that it suits people's needs.

I think it would rather stick with what we have now given the precedent and
the somewhat arbitrary nature of layouts.


 * Alternatively, should we create an addon that makes this the
 default behaviour?


Yep, I think that would be the right way to go.

alex

Re: [VOTE] Buildr 1.4.9 release

[Alex Boisvert]

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.orgwrote:

 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.9 release

[Alex Boisvert]

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.

Re: svn commit: r1406490 - /buildr/trunk/rakelib/doc.rake

[Alex Boisvert]

Hi Donald,

Just wondering the reason behind removing the partial publish task ... it's
been useful in the past to make website updates (e.g. update installation
instructions) between releases.

alex

On Wed, Nov 7, 2012 at 12:17 AM, dona...@apache.org wrote:

 Author: donaldp
 Date: Wed Nov  7 08:17:22 2012
 New Revision: 1406490

 URL: http://svn.apache.org/viewvc?rev=1406490view=rev
 Log:
 Remove the partial publish task and document the remaining publish task

 Modified:
 buildr/trunk/rakelib/doc.rake

 Modified: buildr/trunk/rakelib/doc.rake
 URL:
 http://svn.apache.org/viewvc/buildr/trunk/rakelib/doc.rake?rev=1406490r1=1406489r2=1406490view=diff

 ==
 --- buildr/trunk/rakelib/doc.rake (original)
 +++ buildr/trunk/rakelib/doc.rake Wed Nov  7 08:17:22 2012
 @@ -90,6 +90,7 @@ ForceType 'text/plain; charset=UTF-8'
  end

  # Publish prerequisites to Web site.
 +desc Publish web site 
  task 'publish' = 'site' do
target = people.apache.org:/www/#{spec.name}.apache.org/
puts Uploading new site to #{target} ...
 @@ -98,16 +99,6 @@ task 'publish' = 'site' do
puts 'Done'
  end

 -# Update HTML + PDF documentation (but not entire site; no specs,
 coverage, etc.)
 -task 'publish-doc' = %w(buildr.pdf _site) do
 -  cp 'buildr.pdf', '_site'
 -  target = people.apache.org:/www/#{spec.name}.apache.org/
 -  puts Uploading new site to #{target} ...
 -  sh 'rsync', '--progress', '--recursive', '_site/', target # Note: no
 --delete
 -  sh 'ssh', 'people.apache.org', 'chmod', '-f', '-R', 'g+w', /www/#{
 spec.name}.apache.org/*
 -  puts 'Done'
 -end
 -
  task 'clobber' do
rm_rf '_site'
rm_f 'buildr.pdf'

Re: [VOTE] Buildr 1.4.8 release

[Alex Boisvert]

Confirmed fixed.  Tested on Linux (Ubuntu 12.04) and OSX 10.6 (Snow
Leopard).

+1 for release.

alex

On Sat, Oct 27, 2012 at 2:52 PM, Peter Donald pe...@realityforge.orgwrote:

 Hi,

 Okay. Fixed and the fixed version has been re-uploaded to
 http://people.apache.org/~donaldp/buildr/1.4.8/dist/

 It turns out we follow different rules regarding the verbose flag
 than rake. (Essentially we treat it as a tri-state where unset means
 verbose buildr tasks but non verbose file tasks)

 On Sun, Oct 28, 2012 at 2:10 AM, Alex Boisvert alex.boisv...@gmail.com
 wrote:
  Hi Peter,
 
  There seems to be a minor issue with output... we're missing task output,
  e.g.,
 
  $ buildr _1.4.7_ clean
  (in /home/boisvert/tmp/buildr-example, development)
  Cleaning buildr-example
  Completed in 0.008s
 
  $ buildr _1.4.8_ clean
  (in /home/boisvert/tmp/buildr-example, development)
 
  $
 
  On Sat, Oct 27, 2012 at 3: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.8/dist/
 
  Specifically:
  http://people.apache.org/~donaldp/buildr/1.4.8/dist/buildr-1.4.8.tgz
  http://people.apache.org/~donaldp/buildr/1.4.8/dist/buildr-1.4.8.zip
 
  The documentation generated for this release is available here:
  http://people.apache.org/~donaldp/buildr/1.4.8/site/
  http://people.apache.org/~donaldp/buildr/1.4.8/site/buildr.pdf
 
  The following changes were made since 1.4.7:
 
* Change: Revert to importing non-verbose FileUtils utility methods
  to match buildr 1.4.6 release and earlier.
* Added:  Experimental support for jacoco code coverage tool.
* Fixed:  BUILDR-655 - Support JDK1.7 under OSX
* Change: Updated dependency versions;
  - builder (3.1.3)
  - highline (1.6.15)
  - rubyforge (2.0.4)
  - net-ssh (2.6.0)
  - hoe (3.1.0)
  - rjb (1.4.2)
  - rdoc (3.12)
  - xml-simple (1.1.1)
  - rspec-expectations (2.11.3)
  - rspec-mocks (2.11.3)
  - rspec-core (2.11.1)
  - rspec (2.11.0)
  - rubyzip (0.9.9)
* Added:  BUILDR-652 Generate buildfile from Eclipse workspace.
  (Niklaus Giger)
* Fixed:  BUILDR-627 Support explicitly listed source files in
  buildr cc task. (Christopher Tiwald)
* Fixed:  BUILDR-606 Transitive artifact resolution should not
  include artifacts in 'provided' scope in poms to
  match maven behaviour. (Julio Arias)
* Change: BUILDR-640 Enable building jekyll and rdoc under more
  rubies. (Niklaus Giger)
* Change: Mark Buildr:Bnd.remote_repository as deprecated as
  dependencies appear in maven central.
* Added:  BUILDR-654 Add the ability to configure the version of BND
  used by bnd addon. (Niklaus Giger)
* Added:  Create the git_auto_version addon that automatically
  specifies a version for a git project based
  on git describe.
* Added:  Integrate with Zinc (incremental compilation wrapper for
  scalac 2.9+)
* Change: Default to Scala 2.9.2, ScalaTest 1.8, Scala Specs2 1.11,
  ScalaCheck 1.10.0.
* Change: Scala artifact repository changed to
  http://oss.sonatype.org/content/repositories/releases
* Added:  BUILDR-645 Support Mercurial as a version control system
 (Tan
  Quach)
* Fixed:  BUILDR-646 TGZ files do not keep their permissions when
  extracted
  via Buildr::Unzip#extract
* Added:  Add add_exploded_ear_artifact and
  add_exploded_ejb_artifact to the idea project extension.
* Change: Default to using Checkstyle 5.5 in the checkstyle addon.
* Fixed:  Fix the add_exploded_war_artifact method on the idea
  project by adding in missing method
  `partition_dependencies`.
* Fixed:  Fix the extension of the gwt plugin so that it can be
  required as an addon.
* Fixed:  Fix the undefined default_web_xml variable in the
  add_web_facet method on the idea project.
 
  --
  Cheers,
 
  Peter Donald
 



 --
 Cheers,

 Peter Donald

Re: [VOTE] Buildr 1.4.8 release

[Alex Boisvert]

Hi Peter,

There seems to be a minor issue with output... we're missing task output,
e.g.,

$ buildr _1.4.7_ clean
(in /home/boisvert/tmp/buildr-example, development)
Cleaning buildr-example
Completed in 0.008s

$ buildr _1.4.8_ clean
(in /home/boisvert/tmp/buildr-example, development)

$

On Sat, Oct 27, 2012 at 3:09 AM, Peter Donald pe...@realityforge.orgwrote:

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

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

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

 The following changes were made since 1.4.7:

   * Change: Revert to importing non-verbose FileUtils utility methods
 to match buildr 1.4.6 release and earlier.
   * Added:  Experimental support for jacoco code coverage tool.
   * Fixed:  BUILDR-655 - Support JDK1.7 under OSX
   * Change: Updated dependency versions;
 - builder (3.1.3)
 - highline (1.6.15)
 - rubyforge (2.0.4)
 - net-ssh (2.6.0)
 - hoe (3.1.0)
 - rjb (1.4.2)
 - rdoc (3.12)
 - xml-simple (1.1.1)
 - rspec-expectations (2.11.3)
 - rspec-mocks (2.11.3)
 - rspec-core (2.11.1)
 - rspec (2.11.0)
 - rubyzip (0.9.9)
   * Added:  BUILDR-652 Generate buildfile from Eclipse workspace.
 (Niklaus Giger)
   * Fixed:  BUILDR-627 Support explicitly listed source files in
 buildr cc task. (Christopher Tiwald)
   * Fixed:  BUILDR-606 Transitive artifact resolution should not
 include artifacts in 'provided' scope in poms to
 match maven behaviour. (Julio Arias)
   * Change: BUILDR-640 Enable building jekyll and rdoc under more
 rubies. (Niklaus Giger)
   * Change: Mark Buildr:Bnd.remote_repository as deprecated as
 dependencies appear in maven central.
   * Added:  BUILDR-654 Add the ability to configure the version of BND
 used by bnd addon. (Niklaus Giger)
   * Added:  Create the git_auto_version addon that automatically
 specifies a version for a git project based
 on git describe.
   * Added:  Integrate with Zinc (incremental compilation wrapper for
 scalac 2.9+)
   * Change: Default to Scala 2.9.2, ScalaTest 1.8, Scala Specs2 1.11,
 ScalaCheck 1.10.0.
   * Change: Scala artifact repository changed to
 http://oss.sonatype.org/content/repositories/releases
   * Added:  BUILDR-645 Support Mercurial as a version control system (Tan
 Quach)
   * Fixed:  BUILDR-646 TGZ files do not keep their permissions when
 extracted
 via Buildr::Unzip#extract
   * Added:  Add add_exploded_ear_artifact and
 add_exploded_ejb_artifact to the idea project extension.
   * Change: Default to using Checkstyle 5.5 in the checkstyle addon.
   * Fixed:  Fix the add_exploded_war_artifact method on the idea
 project by adding in missing method
 `partition_dependencies`.
   * Fixed:  Fix the extension of the gwt plugin so that it can be
 required as an addon.
   * Fixed:  Fix the undefined default_web_xml variable in the
 add_web_facet method on the idea project.

 --
 Cheers,

 Peter Donald

Re: [VOTE] Buildr 1.4.7 release

[Alex Boisvert]

The vote passed with 5 +1's (4 binding), one +0 (binding) and no -1.

Pushing the release to the mirrors ...

On Mon, May 28, 2012 at 11:53 AM, Alex Boisvert alex.boisv...@gmail.comwrote:

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

 Specifically:
 http://people.apache.org/~boisvert/buildr/1.4.7/dist/buildr-1.4.7.tgz
 http://people.apache.org/~boisvert/buildr/1.4.7/dist/buildr-1.4.7.zip

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

 The official specification against which this release was tested:
 http://people.apache.org/~boisvert/buildr/1.4.7/site/specs.html

 Test coverage report:
 http://people.apache.org/~boisvert/buildr/1.4.7/site/coverage/index.html


 The following changes were made since 1.4.6:

   * Added:  Add a Sonar extension.
   * Change: BUILDR-638 Update to rake 0.9.2.2 (Russell Teabeault)
   * Added:  BUILDR-316 Add a GWT extension
   * Change: BUILDR-624 Update rspec version to 2.9.0 (Russell Teabeault)
   * Change: BUILDR-632 Update net-ssh version to 2.3.0 (Russell Teabeault)
   * Change: BUILDR-632 Update net-sftp version to 2.0.5 (Russell Teabeault)
   * Fixed:  BUILDR-635 JRE container entry to be declared before user
 sources and dependencies (Dani Perez)
   * Change: BUILDR-639 Stop requiring pygmentize to run rake -T (Russell
 Teabeault)
   * Added:  Enhance the IDEA extension to support the addition of several
 explicit facets such as
 ejb, jruby, jpa, web and gwt.
   * Added:  Add several utility methods to IDEA extension for defining
 artifacts and configurations.
 Add some explicit methods to support a gwt configuration and a
 Exploded War artifact.
   * Change: Upgraded to Apache Ant 1.8.3
   * Change: Default maven2 repository is now repo1.maven.org/maven2.
   * Change: Make minimumTokenCount and encoding configurable for the
 PMD/CPD action
 and default encoding to UTF-8 for compatibility with external
 tools (i.e. Jenkins)
   * Change: BUILDR-615 VersionRequirement.version? now returns true for
 versions following pattern r, e.g. r09
   * Change: BUILDR-630 Run task should not add test dependencies (Russell
 Teabeault)
   * Change: BUILDR-629 JavaRunner should include target/resources in
 classpath (Russell Teabeault)
   * Fixed:  BUILDR-617 pom exclusion does not work (Kafka Liu)
   * 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

Re: svn commit: r1343392 - in /buildr/trunk: CHANGELOG buildr.gemspec

[Alex Boisvert]

Turned out to be just a small (and legal) variation between XML parsers
used by CRuby/JRuby.  Fixed.  Resuming release process ...

On Mon, May 28, 2012 at 6:23 PM, Alex Boisvert alex.boisv...@gmail.comwrote:

 Update:  Doesn't seem to be related to RJB after all.   I get the same
 failure with RJB 1.3.7.

 I don't get the failure if I run with JRuby -- only with CRuby.


 On Mon, May 28, 2012 at 5:58 PM, Alex Boisvert alex.boisv...@gmail.comwrote:

 I can reproduce the failure ... will look into it.


 On Mon, May 28, 2012 at 3:30 PM, Peter Donald pe...@realityforge.orgwrote:

 Hi,

 I have yet to look into it but it seems like the RJB upgrade has
 caused tests to start to fail (at least o OSX). eg.

 peter-donalds-macbook-pro:buildr peter$ bundle exec rspec
 spec/java/pom_spec.rb
 .F

 Failures:

  1) Buildr::POM should respect exclusions when computing transitive
 dependencies when the pom includes properties
 Failure/Error: pom.properties.should eql(specs)

   expected: {a.version=1.1, b.version=1.1,
 project.groupId=group, pom.groupId=group,
 groupId=group, project.artifactId=app,
 pom.artifactId=app, artifactId=app}
got: {a.version=[\1.1\], b.version=1.1,
 project.groupId=group, pom.groupId=group,
 groupId=group, project.artifactId=app,
 pom.artifactId=app, artifactId=app}

   (compared using eql?)

   Diff:
   @@ -1,4 +1,4 @@
   -a.version = 1.1,
   +a.version = [\1.1\],
artifactId = app,
b.version = 1.1,
groupId = group,
 # ./spec/java/pom_spec.rb:123:in `block (2 levels) in top
 (required)'

 Finished in 2.35 seconds
 2 examples, 1 failure

 Failed examples:

 rspec ./spec/java/pom_spec.rb:120 # Buildr::POM should respect
 exclusions when computing transitive dependencies when the pom
 includes properties


 On Tue, May 29, 2012 at 7:15 AM,  boisv...@apache.org wrote:
  Author: boisvert
  Date: Mon May 28 21:15:38 2012
  New Revision: 1343392
 
  URL: http://svn.apache.org/viewvc?rev=1343392view=rev
  Log:
  Upgrade to jekyll 0.11.2 (fix @substitutions@)
  Upgrade to RJB 1.4.0 (avoid compile issue on Windows)
 
  Modified:
 buildr/trunk/CHANGELOG
 buildr/trunk/buildr.gemspec
 
  Modified: buildr/trunk/CHANGELOG
  URL:
 http://svn.apache.org/viewvc/buildr/trunk/CHANGELOG?rev=1343392r1=1343391r2=1343392view=diff
 
 ==
  --- buildr/trunk/CHANGELOG (original)
  +++ buildr/trunk/CHANGELOG Mon May 28 21:15:38 2012
  @@ -65,7 +65,7 @@
   * 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
  +* 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)
 
  Modified: buildr/trunk/buildr.gemspec
  URL:
 http://svn.apache.org/viewvc/buildr/trunk/buildr.gemspec?rev=1343392r1=1343391r2=1343392view=diff
 
 ==
  --- buildr/trunk/buildr.gemspec (original)
  +++ buildr/trunk/buildr.gemspec Mon May 28 21:15:38 2012
  @@ -63,7 +63,7 @@ for those one-off tasks, with a language
spec.add_dependency 'json_pure','1.4.3'
spec.add_dependency 'rubyforge','2.0.3'
spec.add_dependency 'hoe',  '2.3.3'
  -  spec.add_dependency 'rjb',  '1.3.7' if
 ($platform.to_s == 'x86-mswin32' || $platform.to_s == 'ruby')
  +  spec.add_dependency 'rjb',  '1.4.0' if
 ($platform.to_s == 'x86-mswin32' || $platform.to_s == 'ruby')
spec.add_dependency 'atoulme-Antwrap',  '~ 0.7.2'
spec.add_dependency 'diff-lcs', '1.1.3'
spec.add_dependency 'rspec-expectations',   '2.9.0'
  @@ -76,7 +76,7 @@ for those one-off tasks, with a language
 
# The documentation is currently not generated whe building via jruby
unless $platform.to_s == 'java'
  -spec.add_development_dependency 'jekyll', '0.11.0'
  +spec.add_development_dependency 'jekyll', '0.11.2'
  spec.add_development_dependency 'RedCloth', '4.2.9'
  spec.add_development_dependency 'jekylltask', '1.1.0'
  spec.add_development_dependency 'rdoc', '3.8'
 
 



 --
 Cheers,

 Peter Donald

[VOTE] Buildr 1.4.7 release

[Alex Boisvert]

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

Specifically:
http://people.apache.org/~boisvert/buildr/1.4.7/dist/buildr-1.4.7.tgz
http://people.apache.org/~boisvert/buildr/1.4.7/dist/buildr-1.4.7.zip

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

The official specification against which this release was tested:
http://people.apache.org/~boisvert/buildr/1.4.7/site/specs.html

Test coverage report:
http://people.apache.org/~boisvert/buildr/1.4.7/site/coverage/index.html


The following changes were made since 1.4.6:

  * Added:  Add a Sonar extension.
  * Change: BUILDR-638 Update to rake 0.9.2.2 (Russell Teabeault)
  * Added:  BUILDR-316 Add a GWT extension
  * Change: BUILDR-624 Update rspec version to 2.9.0 (Russell Teabeault)
  * Change: BUILDR-632 Update net-ssh version to 2.3.0 (Russell Teabeault)
  * Change: BUILDR-632 Update net-sftp version to 2.0.5 (Russell Teabeault)
  * Fixed:  BUILDR-635 JRE container entry to be declared before user
sources and dependencies (Dani Perez)
  * Change: BUILDR-639 Stop requiring pygmentize to run rake -T (Russell
Teabeault)
  * Added:  Enhance the IDEA extension to support the addition of several
explicit facets such as
ejb, jruby, jpa, web and gwt.
  * Added:  Add several utility methods to IDEA extension for defining
artifacts and configurations.
Add some explicit methods to support a gwt configuration and a
Exploded War artifact.
  * Change: Upgraded to Apache Ant 1.8.3
  * Change: Default maven2 repository is now repo1.maven.org/maven2.
  * Change: Make minimumTokenCount and encoding configurable for the
PMD/CPD action
and default encoding to UTF-8 for compatibility with external
tools (i.e. Jenkins)
  * Change: BUILDR-615 VersionRequirement.version? now returns true for
versions following pattern r, e.g. r09
  * Change: BUILDR-630 Run task should not add test dependencies (Russell
Teabeault)
  * Change: BUILDR-629 JavaRunner should include target/resources in
classpath (Russell Teabeault)
  * Fixed:  BUILDR-617 pom exclusion does not work (Kafka Liu)
  * 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 

Re: svn commit: r1343392 - in /buildr/trunk: CHANGELOG buildr.gemspec

[Alex Boisvert]

Update:  Doesn't seem to be related to RJB after all.   I get the same
failure with RJB 1.3.7.

I don't get the failure if I run with JRuby -- only with CRuby.

On Mon, May 28, 2012 at 5:58 PM, Alex Boisvert alex.boisv...@gmail.comwrote:

 I can reproduce the failure ... will look into it.


 On Mon, May 28, 2012 at 3:30 PM, Peter Donald pe...@realityforge.orgwrote:

 Hi,

 I have yet to look into it but it seems like the RJB upgrade has
 caused tests to start to fail (at least o OSX). eg.

 peter-donalds-macbook-pro:buildr peter$ bundle exec rspec
 spec/java/pom_spec.rb
 .F

 Failures:

  1) Buildr::POM should respect exclusions when computing transitive
 dependencies when the pom includes properties
 Failure/Error: pom.properties.should eql(specs)

   expected: {a.version=1.1, b.version=1.1,
 project.groupId=group, pom.groupId=group,
 groupId=group, project.artifactId=app,
 pom.artifactId=app, artifactId=app}
got: {a.version=[\1.1\], b.version=1.1,
 project.groupId=group, pom.groupId=group,
 groupId=group, project.artifactId=app,
 pom.artifactId=app, artifactId=app}

   (compared using eql?)

   Diff:
   @@ -1,4 +1,4 @@
   -a.version = 1.1,
   +a.version = [\1.1\],
artifactId = app,
b.version = 1.1,
groupId = group,
 # ./spec/java/pom_spec.rb:123:in `block (2 levels) in top
 (required)'

 Finished in 2.35 seconds
 2 examples, 1 failure

 Failed examples:

 rspec ./spec/java/pom_spec.rb:120 # Buildr::POM should respect
 exclusions when computing transitive dependencies when the pom
 includes properties


 On Tue, May 29, 2012 at 7:15 AM,  boisv...@apache.org wrote:
  Author: boisvert
  Date: Mon May 28 21:15:38 2012
  New Revision: 1343392
 
  URL: http://svn.apache.org/viewvc?rev=1343392view=rev
  Log:
  Upgrade to jekyll 0.11.2 (fix @substitutions@)
  Upgrade to RJB 1.4.0 (avoid compile issue on Windows)
 
  Modified:
 buildr/trunk/CHANGELOG
 buildr/trunk/buildr.gemspec
 
  Modified: buildr/trunk/CHANGELOG
  URL:
 http://svn.apache.org/viewvc/buildr/trunk/CHANGELOG?rev=1343392r1=1343391r2=1343392view=diff
 
 ==
  --- buildr/trunk/CHANGELOG (original)
  +++ buildr/trunk/CHANGELOG Mon May 28 21:15:38 2012
  @@ -65,7 +65,7 @@
   * 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
  +* 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)
 
  Modified: buildr/trunk/buildr.gemspec
  URL:
 http://svn.apache.org/viewvc/buildr/trunk/buildr.gemspec?rev=1343392r1=1343391r2=1343392view=diff
 
 ==
  --- buildr/trunk/buildr.gemspec (original)
  +++ buildr/trunk/buildr.gemspec Mon May 28 21:15:38 2012
  @@ -63,7 +63,7 @@ for those one-off tasks, with a language
spec.add_dependency 'json_pure','1.4.3'
spec.add_dependency 'rubyforge','2.0.3'
spec.add_dependency 'hoe',  '2.3.3'
  -  spec.add_dependency 'rjb',  '1.3.7' if
 ($platform.to_s == 'x86-mswin32' || $platform.to_s == 'ruby')
  +  spec.add_dependency 'rjb',  '1.4.0' if
 ($platform.to_s == 'x86-mswin32' || $platform.to_s == 'ruby')
spec.add_dependency 'atoulme-Antwrap',  '~ 0.7.2'
spec.add_dependency 'diff-lcs', '1.1.3'
spec.add_dependency 'rspec-expectations',   '2.9.0'
  @@ -76,7 +76,7 @@ for those one-off tasks, with a language
 
# The documentation is currently not generated whe building via jruby
unless $platform.to_s == 'java'
  -spec.add_development_dependency 'jekyll', '0.11.0'
  +spec.add_development_dependency 'jekyll', '0.11.2'
  spec.add_development_dependency 'RedCloth', '4.2.9'
  spec.add_development_dependency 'jekylltask', '1.1.0'
  spec.add_development_dependency 'rdoc', '3.8'
 
 



 --
 Cheers,

 Peter Donald

Buildr 1.4.7 release candidate #1

[Alex Boisvert]

Buildrs -- I've created a release candidate for Buildr 1.4.7...  could you
help me test it before we start a vote?

thanks!
alex


Source distributions available here:
http://people.apache.org/~boisvert/buildr/1.4.7/dist/

Specifically:
http://people.apache.org/~boisvert/buildr/1.4.7/dist/buildr-1.4.7.tgz
http://people.apache.org/~boisvert/buildr/1.4.7/dist/buildr-1.4.7.zip

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

The official specification against which this release was tested:
http://people.apache.org/~boisvert/buildr/1.4.7/site/specs.html

Test coverage report:
http://people.apache.org/~boisvert/buildr/1.4.7/site/coverage/index.html


The following changes were made since 1.4.6:

  * Added:  Add a Sonar extension.
  * Change: BUILDR-638 Update to rake 0.9.2.2 (Russell Teabeault)
  * Added:  BUILDR-316 Add a GWT extension
  * Change: BUILDR-624 Update rspec version to 2.9.0 (Russell Teabeault)
  * Change: BUILDR-632 Update net-ssh version to 2.3.0 (Russell Teabeault)
  * Change: BUILDR-632 Update net-sftp version to 2.0.5 (Russell Teabeault)
  * Fixed:  BUILDR-635 JRE container entry to be declared before user
sources and dependencies (Dani Perez)
  * Change: BUILDR-639 Stop requiring pygmentize to run rake -T (Russell
Teabeault)
  * Added:  Enhance the IDEA extension to support the addition of several
explicit facets such as
ejb, jruby, jpa, web and gwt.
  * Added:  Add several utility methods to IDEA extension for defining
artifacts and configurations.
Add some explicit methods to support a gwt configuration and a
Exploded War artifact.
  * Change: Upgraded to Apache Ant 1.8.3
  * Change: Default maven2 repository is now repo1.maven.org/maven2.
  * Change: Make minimumTokenCount and encoding configurable for the
PMD/CPD action
and default encoding to UTF-8 for compatibility with external
tools (i.e. Jenkins)
  * Change: BUILDR-615 VersionRequirement.version? now returns true for
versions following pattern r, e.g. r09
  * Change: BUILDR-630 Run task should not add test dependencies (Russell
Teabeault)
  * Change: BUILDR-629 JavaRunner should include target/resources in
classpath (Russell Teabeault)
  * Fixed:  BUILDR-617 pom exclusion does not work (Kafka Liu)
  * 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 

Re: Time between releases

[Alex Boisvert]

On Mon, May 14, 2012 at 4:38 PM, Peter Donald pe...@realityforge.orgwrote:

 Hi,

 On Tue, May 15, 2012 at 6:53 AM, Russ Teabeault rteabea...@rallydev.com
 wrote:
  I thought I had already sent this to the dev group but I don't see it in
  the archives.  So here it goes:
 
  I really like buildr and the sanity it has brought from using it to
 replace
  maven.  I would like to see it grow and prosper.  One complaint I have is
  how infrequent the releases are.  It has been nearly a year since the
 last
  minor patch release and over 5 months since the pre release of the next
  minor patch release.  It seems that if there are one or more bug fixes in
  place then a minor patch release could be done every couple of weeks,
 every
  week or even every couple of days.  I think this is important to the long
  term adoption and health of the project.  I don't want to have to build
 and
  host my own version of the gem while waiting months for an official
  release.  Now I understand that the maintainers have lives but doing a
  release should be quick and simple, especially if it is a patch release.
 
  So, is there a good reason that buildr can't be released more often?

 I don't believe so. Nothing other than someone stepping up to do the
 release I think.

 So what needs to be done for the release? Do we have it documented
 somewhere? Is it as simple as getting the tests passing and pushing
 out changes to rubygems?


The process is documented here:
https://cwiki.apache.org/confluence/display/BUILDR/Release+process
(could use some minor updating on specifics but the overall process is
still valid)

The most challenging for me in the past was getting to a local setup where
all the tests passed on all platforms.  Things have improved a bit with
bundler but I find it's still a bit challenging.

alex

Re: Time between releases

[Alex Boisvert]

On Mon, May 14, 2012 at 5:52 PM, Peter Donald pe...@realityforge.orgwrote:

 My preference would be to aim for supporting/blessing
 * jruby-1.6.7
 * ruby-1.9.2-p320
 * ruby-1.8.7-p358


These would be my preferences too.

alex

Re: JMock in java/tests.rb

[Alex Boisvert]

On Mon, Feb 27, 2012 at 2:09 AM, Pepijn Van Eeckhoudt 
pep...@vaneeckhoudt.net wrote:

 The JUnit and TestNG support automatically pull in JMock without an option
 to disable this. Any idea why this is done? It seems rather arbitrary to
 pull in one specific testing library.

 This is causing problems in my builds because jmock pulls in hamcrest 1.1
 while my unit tests depend on hamcrest 1.2.

 Anyone against removing this or at least making it optional?


The reason was convenience since they are/were often used together.

I'm good with an option to make it optional and/or configure the version
used.

alex

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

[Alex Boisvert]

On Thu, Feb 9, 2012 at 3:10 AM, Peter Donald pe...@realityforge.org wrote:

 On Thu, Feb 9, 2012 at 3:07 AM, Alex Boisvert alex.boisv...@gmail.com
 wrote:
  If you don't mind, I'll take up the release and get started this week.
   We're far into overdue territory :)

 I just fixed a few issues with some addons I added so it may be a good
 idea to take trunk when doing the release :)


Yes, that's the plan.  I'll be releasing trunk.

alex

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

[Alex Boisvert]

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 Donaldpe...@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.gemhttp://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.gemhttp://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/1235https://github.com/carlhuda/bundler/issues/1235

 Not sure how to resolve this yet.

 alex

February 2012 Board Report

[Alex Boisvert]

FYI, I sent the following report to the Board:

-
Attachment D: Status report for the Apache Buildr Project

Buildr is a Ruby-based build system for Java-based applications, including
support for Scala, Groovy and a growing number of JVM languages and tools.

Our latest release happened in June -- we were hoping for a release in
November
but efforts stalled after discovering platform installation issues in a
release
candidate. The release will likely happen in February. The changelog
currently
shows about 50 fixes/changes/enhancements since our last release.
Subversion log
show about 100 commits since June with commits from 3 different committers
and
patches accepted from 3 external contributors.

Mailing lists have quiet in the past 3 months.

We have no issues that require board attention.

(also achived on our wiki at
https://cwiki.apache.org/confluence/display/BUILDR/February+2012+Board+Report
)

Re: Experiences with transitive dependencies in buildr

[Alex Boisvert]

Neat!

I think something missing (unless I missed it) is the notion of
scopes/groups for artifacts.

With respect to Buildr integration, it would be nice if it could reuse the
repositories specified in the buildfile (e.g. Buildr.repositories.remote)
and maybe allow mapping of groups to Buildr's built-in
compile/test/package/run/... tasks, similar to how ivy4r does it, e.g.,

  ivy.conf(
:compile = ['buildtime', 'default', 'hadoop'],
:test = ['buildtime', 'default', 'test'],
:package = 'default'
  )

(there are alternate syntaxes for this, I'm just copying  pasting the
closest example I had).

alex

On Wed, Dec 28, 2011 at 11:43 AM, Michael Guymon
michael.guy...@gmail.comwrote:


 So I have slowly being making progress on a dependency manager for buildr
 and have put together a very simple implementation based on Bundler using
 Aether for the transitive resolution. I would love some feed back on what I
 have pieced together so far.

 https://github.com/mguymon/**lockjar https://github.com/mguymon/lockjar

 A Jarfile is used to specify the repos and dependencies, an example:

 repository 'http://repository.jboss.org/**nexus/content/groups/public-**
 jboss http://repository.jboss.org/nexus/content/groups/public-jboss'
 jar com.slackworks:model-citizen:**0.1
 jar org.apache.mina:mina-core:2.**0.4 do exclude com.package,
 com.another.package:blah:7 end

 Would produce a Jarfile.lock with absolute paths to the local jars, an
 example:

 ---

 dependencies:
  com.slackworks:model-citizen:**0.1: /home/zinger/devel/projects/**
 swx/lockjar/tmp/test-repo/com/**slackworks/model-citizen/0.1/**
 model-citizen-0.1.jar
  org.apache.mina:mina-core:jar:**2.0.4: /home/zinger/devel/projects/**
 swx/lockjar/tmp/test-repo/org/**apache/mina/mina-core/2.0.4/**
 mina-core-2.0.4.jar
  org.slf4j:slf4j-api:jar:1.6.1: /home/zinger/devel/projects/**
 swx/lockjar/tmp/test-repo/org/**slf4j/slf4j-api/1.6.1/slf4j-**
 api-1.6.1.jar

 repositories:
  - 
 http://repository.jboss.org/**nexus/content/groups/public-**jbosshttp://repository.jboss.org/nexus/content/groups/public-jboss


 The Jarfile.lock is standard yaml, not sure if a custom dsl is needed.
 Similar to bundler, the Jarfile.lock has to be generated before getting
 access to the dependencies. Once the Jarfile.lock is generated, Buildr can
 reuse it instead of checking for transitive dependencies every time.

 Next step is moving the project towards something that integrates nicely
 with Buildr. Maybe allow the Jarfile to be defined directly in the
 buildfile?

 thanks,
 Michael


 On 11/04/2011 06:13 AM, Peter Tillotson wrote:

 This sounds pretty good - some thoughts inline below

  Dependency Resolution

 * Dependency resolution is optional
 * Resolve Transitive Dependencies for an artifact(s)
 * Create/Rebuild a dependency file
 * Lock dependencies based on the dependency file


 Transitive resolution should be capable of producing the same
 dependencies as maven ( possibly via an interface compatible plugin ) and
 support the full maven spec.

 I'd add  filtering and blacklist has been useful as well. I always have
 to package(:war).libs.reject! { |lib| lib.group == 'servlet-api' } this is
 a reasonable compile dependency that shouldn't get into runtime. If the
 dependencies file something like the following

 runtime:
- org.apache.cassandra:**cassalndra-all:1.0.1
exclude:
- *:servlet-api:*
- *:junit:*

 That would be pretty handy - I really like the idea of the dependency
 report effectively acting as the whitelist / blacklist so when the universe
 changes my build file doesn't necessarily have to :-)

  Maven interop

 * Generate a maven POM based on a Buildr project
 * Create  deploy maven friendly artifacts based on a Buildr project


 Would there be any benefit for having Ivy interoperability as well?


 p

 __**__
 From: Michael Guymonmichael.guymon@gmail.**commichael.guy...@gmail.com
 
 To: dev@buildr.apache.org
 Sent: Thursday, 3 November 2011, 23:16
 Subject: Re: Experiences with transitive dependencies in buildr


 So based on the discussion, it sounds like the following solutions would
 work well:

 Dependency Resolution

 * Dependency resolution is optional
 * Resolve Transitive Dependencies for an artifact(s)
 * Create/Rebuild a dependency file
 * Lock dependencies based on the dependency file

 Maven interop

 * Generate a maven POM based on a Buildr project
 * Create  deploy maven friendly artifacts based on a Buildr project


 Would there be any benefit for having Ivy interoperability as well?

 On 11/02/2011 09:59 PM, Peter Donald wrote:

 Hi,

 On Thu, Nov 3, 2011 at 12:26 AM, Chiaming Hsucamy...@yahoo.com
 wrote:

 If this becomes part of the core of buildr as Peter suggested, would
 there be performance impact when not using transitive dependencies?

 I would hope not.

 I am not a huge fan of transitive closure across the builds when you
 can't lock it down to a specific set (like Gemfile.lock or 

Re: [VOTE] Buildr 1.4.7 RC1

[Alex Boisvert]

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

[Alex Boisvert]

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

 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: Moving to RJB 1.3.7 ?

[Alex Boisvert]

Still doesn't install directly on JRuby...  This is a clean rvm install
jruby-1.6.5 install:

boisvert@honeybrown:~$ rvm use jruby-1.6.5
Using /home/boisvert/.rvm/gems/jruby-1.6.5

boisvert@honeybrown:~$ which gem
/home/boisvert/.rvm/rubies/jruby-1.6.5/bin/gem

boisvert@honeybrown:~$ gem install buildr --pre -platform java
^Cboisvert@honeybrown:~$ gem install buildr --pre --platform java
Building native extensions.  This could take a while...
ERROR:  Error installing buildr:
ERROR: Failed to build gem native extension.

WTF?  It's trying to install rjb so it's not picking up the java platform
distribution.

I don't think that's a buildr issue; just pointing out that we may have to
deal with install hurdles.  (BTW, I also tried with jruby-1.6.3 with same
result).

alex


On Thu, Nov 17, 2011 at 1:14 PM, Antoine Toulme anto...@lunar-ocean.comwrote:

 Done, and pushing pre2 for both MRI and Java.

 Please try it out, I'll work on the CI meanwhile.

 Thanks!

 Antoine


 On Thu, Nov 17, 2011 at 12:44, Antoine Toulme anto...@toulme.name wrote:

 I think I did the wrong thing and tried to yank the prerelease, after
 Dominic's reply, to push a new attempt. And it didn't work.

 I thought I could push prerelease gems.

 On second thought, maybe I could push pre2 ? I'll get to that and will
 try with 2 different machines again.

 Sorry for the confusion. Doing the RJB change now.

 Thanks,

 Antoine

 On Thu, Nov 17, 2011 at 12:35, Alex Boisvert alex.boisv...@gmail.comwrote:

 Fine with me.

 Separately, using rvm and jruby 1.6.5, when I gem install buildr --pre
 it seems to pick up the c-ruby platform distribution not the java platform
 distribution.   I tried explicitly passing --platform java but that
 didn't work either.   Anybody else seen this?

 (The package installs fine when I download and gem install
 buildr-1.4.7.pre.gem directly)

 alex


 On Thu, Nov 17, 2011 at 12:21 PM, Antoine Toulme anto...@toulme.namewrote:

 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

Re: Moving to RJB 1.3.7 ?

[Alex Boisvert]

Right, downloading + installing the local gem works fine.

alex

On Thu, Nov 17, 2011 at 1:40 PM, Antoine Toulme anto...@lunar-ocean.comwrote:

 Very odd. I had issues too, but not the same error.

 Please try this out:
 Download the gem directly:
 Downloadhttp://rubygems.org/downloads/buildr-1.4.7.pre2-java.gem

 Then gem install the gem.

 It worked for me then.

 Antoine

 On Thu, Nov 17, 2011 at 13:25, Alex Boisvert alex.boisv...@gmail.com
 wrote:

  Still doesn't install directly on JRuby...  This is a clean rvm install
  jruby-1.6.5 install:
 
  boisvert@honeybrown:~$ rvm use jruby-1.6.5
  Using /home/boisvert/.rvm/gems/jruby-1.6.5
 
  boisvert@honeybrown:~$ which gem
  /home/boisvert/.rvm/rubies/jruby-1.6.5/bin/gem
 
  boisvert@honeybrown:~$ gem install buildr --pre -platform java
  ^Cboisvert@honeybrown:~$ gem install buildr --pre --platform java
  Building native extensions.  This could take a while...
  ERROR:  Error installing buildr:
  ERROR: Failed to build gem native extension.
 
  WTF?  It's trying to install rjb so it's not picking up the java platform
  distribution.
 
  I don't think that's a buildr issue; just pointing out that we may have
 to
  deal with install hurdles.  (BTW, I also tried with jruby-1.6.3 with same
  result).
 
  alex
 
 
  On Thu, Nov 17, 2011 at 1:14 PM, Antoine Toulme anto...@lunar-ocean.com
 wrote:
 
  Done, and pushing pre2 for both MRI and Java.
 
  Please try it out, I'll work on the CI meanwhile.
 
  Thanks!
 
  Antoine
 
 
  On Thu, Nov 17, 2011 at 12:44, Antoine Toulme anto...@toulme.name
 wrote:
 
  I think I did the wrong thing and tried to yank the prerelease, after
  Dominic's reply, to push a new attempt. And it didn't work.
 
  I thought I could push prerelease gems.
 
  On second thought, maybe I could push pre2 ? I'll get to that and will
  try with 2 different machines again.
 
  Sorry for the confusion. Doing the RJB change now.
 
  Thanks,
 
  Antoine
 
  On Thu, Nov 17, 2011 at 12:35, Alex Boisvert alex.boisv...@gmail.com
 wrote:
 
  Fine with me.
 
  Separately, using rvm and jruby 1.6.5, when I gem install buildr
  --pre it seems to pick up the c-ruby platform distribution not the
 java
  platform distribution.   I tried explicitly passing --platform java
 but
  that didn't work either.   Anybody else seen this?
 
  (The package installs fine when I download and gem install
  buildr-1.4.7.pre.gem directly)
 
  alex
 
 
  On Thu, Nov 17, 2011 at 12:21 PM, Antoine Toulme anto...@toulme.name
 wrote:
 
  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
 
 
 
 
 
 

November 2011 Board Report

[Alex Boisvert]

I wrote a quick board report,
https://cwiki.apache.org/confluence/display/BUILDR/November+2011+Board+Report

Will be sending tomorrow.  As always feel free to edit/comment if I forgot
something.

alex

Re: New release ?

[Alex Boisvert]

Quick update:  I have pending changes for,

1) upgrading to Scala 2.9.1 as default
2) basic support for scala Specs2 testing framework
3) better change detection for Scala sources (still naive, but better)
4) new :scopes and :optional dependencies options on transitive()

Need to add/update tests for all of this.

alex

On Sunday, October 23, 2011, Alex Boisvert alex.boisv...@gmail.com wrote:
 Hi Antoine,
 I'm good for doing a release in the near future.
 There's a couple of library upgrades I want to do (mostly relative to
Scala 2.9.1) beforehand but that's about it.
 alex

 On Sat, Oct 22, 2011 at 5:38 PM, Antoine Toulme anto...@lunar-ocean.com
wrote:

 Hi folks,

 thanks for the hard work and keeping this up. I apologize I can't take as
 much time as I'd like on Buildr.

 I looked up the changelog and it looks to me that we are ripe for a new
 release - and I'm willing to help push it out.

 WDYT ?

 Antoine

Re: Experiences with transitive dependencies in buildr

[Alex Boisvert]

+1

My personal view is that,

1) Buildr shouldn't force any dependency resolution framework on anybody.
 It should always be possible to use explicit dependency lists (aka
whitelisting) -- either local files (non-Maven artifacts) or Maven
artifacts -- or use 3rd-party plugins.

2) We should keep supporting and improving Maven artifact resolution in
Buildr (core) because it's the most widely used distribution scheme in the
Java world.  If that means eventually reusing Aether to get real good
interoperability, so be it.

I'll say in passing that a great feature of any dependency resolution
framework is to allow/support caching the results locally to avoid both
recomputing and network usage every time.

Ivy4r supports this (though it's not the default) and saves the result in
YAML files (one per ivy conf).  This has the advantage that you can easily
peek into what dependencies are used at any time and if you check it into
version control then you can also easily monitor dependency changes and
keep dependencies consistent across multiple checkouts.

alex


On Wed, Nov 2, 2011 at 8:36 AM, Michael Guymon michael.guy...@gmail.comwrote:


 I could not agree more, Buildr should stay lean and mean. Enabling a big
 dependency resolution framework should be optional.

 Right now Aether suffers from the same needy networking that Maven has. It
 wants to check artifacts frequently for changes. While this can be a good
 thing, it is not always an operation a project should have to do.

 --M


 On 11/02/2011 09:26 AM, Chiaming Hsu wrote:


 If this becomes part of the core of buildr as Peter suggested, would
 there be performance impact when not using transitive dependencies?

 I have large projects using buildr (migrated from Maven), and I did
 strictly white listing without any use of transitive dependencies.  Buildr
 runs at least twice faster then Maven to build the same large project after
 migration and generates WAR artifacts about half of the size of Maven.  I
 believe using white listing of dependencies without transitive plays a key
 role in the performance / compactness I saw.  I don't want to lose this key
 benefit of using buildr.

 In a sense, I would like to see transitive dependencies being optional
 (as it is in buildr now) and avoid any performance impact for projects not
 using transitive dependencies, if we brought in more Maven stuff into
 core buildr library.

 Cheers,
 Chiaming Hsu



 __**__
 From: Peter Donaldpe...@realityforge.org
 To: dev@buildr.apache.org
 Sent: Tuesday, November 1, 2011 8:40 PM
 Subject: Re: Experiences with transitive dependencies in buildr

 Hi,

 On Sat, Oct 29, 2011 at 5:43 AM, Michael Guymon
 michael.guy...@gmail.com  wrote:

 The integration with buildr is crude and for some reason the rdoc is no
 longer formated correct. I will update it to make it legible again.

 https://github.com/mguymon/**buildr-resolverhttps://github.com/mguymon/buildr-resolver

 nice.

  This is the ruby wrapper for the Aether java libs, which buildr-resolver
 depends on

 https://github.com/mguymon/**naetherhttps://github.com/mguymon/naether

 That is quite neat. I wonder if the core of buildr could move across
 to using (n)Aether and if there is much benefit from that? Last time I
 looked the project was still relatively volatile. What did you think
 of working with the library?

 The one advantage I see is that it would be using the same core as
 maven and thus guaranteed to be compatible (where as now we know there
 is scenarios where we are not quite right).

Re: Rake Setup?

[Alex Boisvert]

On Fri, Oct 7, 2011 at 8:50 AM, Daniel Spiewak djspie...@gmail.com wrote:

 It's been a while since I ran Buildr from trunk.  I tried today and I'm
 discovering that the setup task for Buildr's Rakefile appears to be
 missingt
 (note: this also affects the stage task, which depends on setup).  Has
 setup
 been replaced with something or is it just gone?


Welcome back :)

We're using bundler now to manage dependencies so you'll want to run bundle
install and either set up your environment to automatically pick up the
bundled gems (e.g. http://effectif.com/ruby/automating-bundle-exec though
there are many other ways) or run everything prefixed with bundle exec.

Hadn't noticed state task is broken, I'll take a look.

alex

Re: Rake Setup?

[Alex Boisvert]

On Fri, Oct 7, 2011 at 10:55 AM, Alex Boisvert alex.boisv...@gmail.comwrote:

 On Fri, Oct 7, 2011 at 8:50 AM, Daniel Spiewak djspie...@gmail.comwrote:

 It's been a while since I ran Buildr from trunk.  I tried today and I'm
 discovering that the setup task for Buildr's Rakefile appears to be
 missingt

 (note: this also affects the stage task, which depends on setup).  Has
 setup
 been replaced with something or is it just gone?


 Welcome back :)

 We're using bundler now to manage dependencies so you'll want to run
 bundle install and either set up your environment to automatically pick up
 the bundled gems (e.g. http://effectif.com/ruby/automating-bundle-exec though
 there are many other ways) or run everything prefixed with bundle exec.

 Hadn't noticed state task is broken, I'll take a look.


s/state/stage.

fixed.

Re: Using RSpec to test buildr plugins

[Alex Boisvert]

Any chance you could commit your specs so I can try them?

alex


On Thu, Sep 22, 2011 at 8:18 AM, Dominic Graefen
dominic.grae...@gmail.comwrote:

 I am trying to write RSpec tests for my buildr plugin 'buildr-as3' (
 https://github.com/devboy/buildr_as3)
 but am facing a problem with missing Buildr::RSpec::Matchers as soon as I
 require buildr from any of my specs.

 I am having a hard time to find out where this problem comes from and
 therefore couldn't come up with a solution yet,
 If anyone here has a clue what could cause this I would appreciate any kind
 of pointer into the right direction.

 For completeness the RSpec output:

 ( ~/Development/Source/Ruby/buildr_as3 )
 devboy  bundle exec rake spec
 (in /Users/devboy/Development/Source/Ruby/buildr_as3)
 rm -rf /Users/devboy/Development/Source/Ruby/buildr_as3/test/report
 /Users/devboy/.rvm/rubies/ruby-1.9.2-p180/bin/ruby -S bundle exec rspec
 spec/as3/mxml_spec.rb
 /Users/devboy/.rvm/gems/ruby-1.9.2-p180/gems/rake-0.8.7/lib/rake.rb:2503:in
 `const_missing': uninitialized constant Buildr::RSpec::Matchers (NameError)
 from
 /Users/devboy/.rvm/gems/ruby-1.9.2-p180/gems/rspec-core-2.1.0/lib/rspec/core/backward_compatibility.rb:20:in
 `const_missing'
 from
 /Users/devboy/.rvm/gems/ruby-1.9.2-p180/gems/rspec-expectations-2.1.0/lib/rspec/matchers/dsl.rb:21:in
 `top (required)'
 from
 /Users/devboy/.rvm/gems/ruby-1.9.2-p180/gems/rspec-expectations-2.1.0/lib/rspec/matchers/be.rb:1:in
 `require'
 from
 /Users/devboy/.rvm/gems/ruby-1.9.2-p180/gems/rspec-expectations-2.1.0/lib/rspec/matchers/be.rb:1:in
 `top (required)'
 from
 /Users/devboy/.rvm/gems/ruby-1.9.2-p180/gems/rspec-expectations-2.1.0/lib/rspec/matchers.rb:172:in
 `require'
 from
 /Users/devboy/.rvm/gems/ruby-1.9.2-p180/gems/rspec-expectations-2.1.0/lib/rspec/matchers.rb:172:in
 `top (required)'
 from
 /Users/devboy/.rvm/gems/ruby-1.9.2-p180/gems/rspec-expectations-2.1.0/lib/rspec/expectations.rb:2:in
 `require'
 from
 /Users/devboy/.rvm/gems/ruby-1.9.2-p180/gems/rspec-expectations-2.1.0/lib/rspec/expectations.rb:2:in
 `top (required)'
 from
 /Users/devboy/.rvm/gems/ruby-1.9.2-p180/gems/rspec-core-2.1.0/lib/rspec/core/expecting/with_rspec.rb:1:in
 `require'
 from
 /Users/devboy/.rvm/gems/ruby-1.9.2-p180/gems/rspec-core-2.1.0/lib/rspec/core/expecting/with_rspec.rb:1:in
 `top (required)'
 from
 /Users/devboy/.rvm/gems/ruby-1.9.2-p180/gems/rspec-core-2.1.0/lib/rspec/core/configuration.rb:144:in
 `require'
 from
 /Users/devboy/.rvm/gems/ruby-1.9.2-p180/gems/rspec-core-2.1.0/lib/rspec/core/configuration.rb:144:in
 `require_expectation_framework_adapter'
 from
 /Users/devboy/.rvm/gems/ruby-1.9.2-p180/gems/rspec-core-2.1.0/lib/rspec/core/configuration.rb:329:in
 `configure_expectation_framework'
 from
 /Users/devboy/.rvm/gems/ruby-1.9.2-p180/gems/rspec-core-2.1.0/lib/rspec/core/command_line.rb:20:in
 `run'
 from
 /Users/devboy/.rvm/gems/ruby-1.9.2-p180/gems/rspec-core-2.1.0/lib/rspec/core/runner.rb:55:in
 `run_in_process'
 from
 /Users/devboy/.rvm/gems/ruby-1.9.2-p180/gems/rspec-core-2.1.0/lib/rspec/core/runner.rb:46:in
 `run'
 from
 /Users/devboy/.rvm/gems/ruby-1.9.2-p180/gems/rspec-core-2.1.0/lib/rspec/core/runner.rb:10:in
 `block in autorun'
 rake aborted!
 ruby -S bundle exec rspec spec/as3/mxml_spec.rb failed

 (See full trace by running task with --trace)

 Thank you!

 --
 Dominic Graefen
 Freelance: Interactive Developer / Creative Technologist
 devboy.org

Re: Using RSpec to test buildr plugins

[Alex Boisvert]

Cool, working over here too.

alex

On Thu, Sep 22, 2011 at 1:50 PM, Dominic Graefen
dominic.grae...@gmail.comwrote:

 Hi Alex,

 i solved it, or at least so it seems. Was a problem with autoload.

 I am now using a trimmed down version of the buildr spec_helpers and
 sandbox and they seem todo the job.

 https://github.com/devboy/buildr_as3/tree/feature/rspec/spec

 --
 Dominic Graefen
 Freelance: Interactive Developer / Creative Technologist
 devboy.org (http://devboy.org)


 On Thursday, September 22, 2011 at 10:29 PM, Alex Boisvert wrote:

  Any chance you could commit your specs so I can try them?
 
  alex
 
 
  On Thu, Sep 22, 2011 at 8:18 AM, Dominic Graefen
  dominic.grae...@gmail.com (mailto:dominic.grae...@gmail.com)wrote:
 
   I am trying to write RSpec tests for my buildr plugin 'buildr-as3' (
   https://github.com/devboy/buildr_as3)
   but am facing a problem with missing Buildr::RSpec::Matchers as soon as
 I
   require buildr from any of my specs.
  
   I am having a hard time to find out where this problem comes from and
   therefore couldn't come up with a solution yet,
   If anyone here has a clue what could cause this I would appreciate any
 kind
   of pointer into the right direction.
  
   For completeness the RSpec output:
  
   ( ~/Development/Source/Ruby/buildr_as3 )
   devboy  bundle exec rake spec
   (in /Users/devboy/Development/Source/Ruby/buildr_as3)
   rm -rf /Users/devboy/Development/Source/Ruby/buildr_as3/test/report
   /Users/devboy/.rvm/rubies/ruby-1.9.2-p180/bin/ruby -S bundle exec rspec
   spec/as3/mxml_spec.rb
  
 /Users/devboy/.rvm/gems/ruby-1.9.2-p180/gems/rake-0.8.7/lib/rake.rb:2503:in
   `const_missing': uninitialized constant Buildr::RSpec::Matchers
 (NameError)
   from
  
 /Users/devboy/.rvm/gems/ruby-1.9.2-p180/gems/rspec-core-2.1.0/lib/rspec/core/backward_compatibility.rb:20:in
   `const_missing'
   from
  
 /Users/devboy/.rvm/gems/ruby-1.9.2-p180/gems/rspec-expectations-2.1.0/lib/rspec/matchers/dsl.rb:21:in
   `top (required)'
   from
  
 /Users/devboy/.rvm/gems/ruby-1.9.2-p180/gems/rspec-expectations-2.1.0/lib/rspec/matchers/be.rb:1:in
   `require'
   from
  
 /Users/devboy/.rvm/gems/ruby-1.9.2-p180/gems/rspec-expectations-2.1.0/lib/rspec/matchers/be.rb:1:in
   `top (required)'
   from
  
 /Users/devboy/.rvm/gems/ruby-1.9.2-p180/gems/rspec-expectations-2.1.0/lib/rspec/matchers.rb:172:in
   `require'
   from
  
 /Users/devboy/.rvm/gems/ruby-1.9.2-p180/gems/rspec-expectations-2.1.0/lib/rspec/matchers.rb:172:in
   `top (required)'
   from
  
 /Users/devboy/.rvm/gems/ruby-1.9.2-p180/gems/rspec-expectations-2.1.0/lib/rspec/expectations.rb:2:in
   `require'
   from
  
 /Users/devboy/.rvm/gems/ruby-1.9.2-p180/gems/rspec-expectations-2.1.0/lib/rspec/expectations.rb:2:in
   `top (required)'
   from
  
 /Users/devboy/.rvm/gems/ruby-1.9.2-p180/gems/rspec-core-2.1.0/lib/rspec/core/expecting/with_rspec.rb:1:in
   `require'
   from
  
 /Users/devboy/.rvm/gems/ruby-1.9.2-p180/gems/rspec-core-2.1.0/lib/rspec/core/expecting/with_rspec.rb:1:in
   `top (required)'
   from
  
 /Users/devboy/.rvm/gems/ruby-1.9.2-p180/gems/rspec-core-2.1.0/lib/rspec/core/configuration.rb:144:in
   `require'
   from
  
 /Users/devboy/.rvm/gems/ruby-1.9.2-p180/gems/rspec-core-2.1.0/lib/rspec/core/configuration.rb:144:in
   `require_expectation_framework_adapter'
   from
  
 /Users/devboy/.rvm/gems/ruby-1.9.2-p180/gems/rspec-core-2.1.0/lib/rspec/core/configuration.rb:329:in
   `configure_expectation_framework'
   from
  
 /Users/devboy/.rvm/gems/ruby-1.9.2-p180/gems/rspec-core-2.1.0/lib/rspec/core/command_line.rb:20:in
   `run'
   from
  
 /Users/devboy/.rvm/gems/ruby-1.9.2-p180/gems/rspec-core-2.1.0/lib/rspec/core/runner.rb:55:in
   `run_in_process'
   from
  
 /Users/devboy/.rvm/gems/ruby-1.9.2-p180/gems/rspec-core-2.1.0/lib/rspec/core/runner.rb:46:in
   `run'
   from
  
 /Users/devboy/.rvm/gems/ruby-1.9.2-p180/gems/rspec-core-2.1.0/lib/rspec/core/runner.rb:10:in
   `block in autorun'
   rake aborted!
   ruby -S bundle exec rspec spec/as3/mxml_spec.rb failed
  
   (See full trace by running task with --trace)
  
   Thank you!
  
   --
   Dominic Graefen
   Freelance: Interactive Developer / Creative Technologist
   devboy.org (http://devboy.org)

Re: Updating to rubygems 1.8.6?

[Alex Boisvert]

+1 monkeying with gem versions is largely redundant with bundler now so I
think it's best to take it out (assume read-only, like you said) and leave
it to the more sophisticated tool.

alex

On Tuesday, July 26, 2011, Rhett Sutphin rh...@detailedbalance.net wrote:
 Hi Peter,

 On Jul 26, 2011, at 7:11 AM, Peter Donald wrote:

 Hi,

 I am looking at upgrading buildrs dependency on rubygems to a later
version
 and being more explicit about the version. i.e. Something like

 spec.add_dependency 'rubygems-update',  '= 1.8.6'

 Good idea, though the gemspec line you want is something like this:

 s.required_rubygems_version = = 1.8.6

 Is 1.8.6 specifically required? I would ask that you try to make this as
loose as possible. Many releases in the 1.7 and 1.8 line have been broken or
unreasonably noisy, so I have been conservative about upgrading. (I'm still
mostly using 1.6.2.)


 However as I was going through this I noticed we are using a whole
whackload
 of deprecated features that is planned to be remove from rubygems in the
 next few months, in particular Gem:SourceIndex. We mostly use the
plugin
 to ensure the build has necessary dependencies before it rus (i.e. if you
 have added it to build.yaml) and to install gems as part of :gem
packaging.
 As both of these features were broken up until a few releases ago I would
 guess they are barely used. In some environments some of these features
 continue to be broken (in particular installing of gems).

 Yes, automatically installing gems from build.yml has been broken for a
long time. I've tried patching it a few times, but never come up with a
solution inside buildr that works consistently. Eventually I gave up and
added a script like this

 https://github.com/NUBIC/psc-mirror/blob/trunk/install_gems.rb

 in each of my projects that uses buildr.


 The ruby world seems to be going in a few different directions to manage
 dependencies (i.e. rvm, bundler, ...) but most of them involve the
runtime
 managing them.

 So I propose that we remove all the usage of these features and just
 consider the rubygems library as a read-only interface. We could change
the
 startup scanning of build.yaml and rather than trying to install missing
 dependencies just print an error on the console and exit. For the
:install
 phase of gem package I think it would be best to let people manage it in
a
 way that makes sense in their environment. We could add documentation to
 fill this gap.

 Thoughts?

 This makes sense to me. I've explained my feelings about the gem
installer. I don't use the gem package type nor do I recall anyone ever
asking a question about it on the mailing list.

 Rhett


 --
 Cheers,

 Peter Donald

Buildr @ Oredev 2011

[Alex Boisvert]

Just a heads-up, I'll be presenting Buildr at Øredev 2011 in November:

http://oredev.org/2011
http://oredev.org/2011/sessions/apache-buildr-build-like-you-code

If anyone wants to hook up at the conference, work/review something
together, have me over for an on-site presentation/discussion in the area or
just grab lunch/beer together, it would be a pleasure.

alex

Re: Testing a change for pull request submittal?

[Alex Boisvert]

Hi Christopher,

Thanks for the patch!  I've applied it as-is.

I /may/ rework it a little bit later to extend group include/exclude support
to other test frameworks:  JUnit, ScalaTest, Specs and others all support
the notion of grouping/labeling tests and I'd like to standardize how this
is specified in the Buildfile and on the command-line, e.g.,

buildr test:@group1,-@group2# include group1 and exclude group2

similar to how we do for individual test inclusion/exclusion today.

alex


On Mon, Jul 18, 2011 at 12:42 PM, Christopher Coco cac...@gmail.com wrote:

 Hi Alex,

 I've finally had time to get back to this. I've submitted a JIRA
 (BUILDR-598) along with a code patch attached and updated the pull request
 in GitHub with the changes to support TestNG group inclusion and exclusion
 via the @Test(groups={}) annotation modifier.

 Please let me know if there's anything else I can do to get this included
 in Buildr.

 Thanks!
 -c

 On Wednesday, April 27, 2011 at 8:23 AM, Christopher Coco wrote:

  Hi Alex,
 
  No worries. I'll open up a JIRA as you suggested.
 
  Thanks!
  Christopher
 
  On Wed, Apr 27, 2011 at 6:36 AM, Alex Boisvert 
  alex.boisv...@gmail.com(mailto:
 alex.boisv...@gmail.com) wrote:
   Hi Christopher,
  
Oh, I haven't seen your pull request... regardless... I forgot to say
 the
best way to notify other devs of a patch is to open a Jira, attach a
 copy of
the patch, make sure you click on the ASL license grant and if your
 work is
also on github (or wherever else) then link to it.
  
   https://issues.apache.org/jira/browse/BUILDR
  
   https://issues.apache.org/jira/browse/BUILDRalex
  
  
On Tue, Apr 26, 2011 at 10:00 PM, Christopher Coco 
   cac...@gmail.com(mailto:
 cac...@gmail.com) wrote:
  
Hi Alex,
   
Thanks for the info. I'll look into rspec. I submitted a pull request
 a
couple of weeks ago (maybe rather hastily) for the TestNG changes I
 made.
I'll try to write up a test to accompany them.
   
Thanks again,
Christopher
   
   
On Tue, Apr 26, 2011 at 6:06 PM, Alex Boisvert 
 alex.boisv...@gmail.com (mailto:alex.boisv...@gmail.com)
wrote:
   
 Hi Christopher,

 Pull requests are much appreciated! And your JSP precompiler is a
 very
 nice
 first task.

 For testing, we use rspec.  If you're enhancing TestNG support, you
would
 typically add to the TestNG specification (

 https://github.com/apache/buildr/blob/trunk/lib/buildr/java/tests.rb).

 If you get stuck, ask questions here or you can try to catch some
 of us
on
 the IRC channel (#buildr on irc.freenode.net (
 http://irc.freenode.net))

 alex

 On Tue, Apr 26, 2011 at 2:51 PM, Christopher Coco 
 cac...@gmail.com (mailto:cac...@gmail.com)
 wrote:

  Hey guys,
 
  I'm new to Buildr (and ruby in general) and am working on
 migrating our
  build from Maven to something that is more expressive in terms of
project
  definition which is what drew us to Buildr. A couple of the
 necessary
  pieces
  we need before switching are expanded TestNG support (like
 supporting
  excluding/including by TestNG groups) and JSP pre-compilation
 (via
 tomcat6
  jasper). Simple things, right?
 
  Knowing little ruby when I started, I did managed to write a jsp
  precompiler
  extension (available here: https://gist.github.com/921897). I'm
 sure
 this
  code can be improved.
 
  As for the TestNG functionality, trying to get exclusion via
 TestNG
 groups
  (or any of the other cmd line options that TestNG allows) using
 the
  properties hash didn't work as the param and value are added to
 the
 TestNG
  runner as -D args instead of just as cmd line params. So, I
 forked the
  buildr project on github and made a few small tweaks to the
 tests.rb to
  pass
  along more parameters in the options array to the TestNG class.
 The
 change
  basically shims more cmd line parameters onto the string for
 TestNG
 runner.
 
  So my question is now, ok, I should probably test this -- like I
 mentioned,
  I'm extremely green with ruby -- what's the next step (or steps)
 so I
can
  actually give some confidence (other than that we're actually
 running
the
  fork here) that the change works so that my pull request is
 actually
 looked
  at for potential inclusion into the master branch? I'm a java guy
 and
  slowly
  learning ruby and ruby testing is somewhat alien to me right now.
 But,
I
  think this functionality is useful (maybe I'm off-base, but we
definitely
  need it and TestNG definitely supports it), so I'd like to
 actually
help
  out
  here and contribute. I know the question is seemingly general
 (ruby
  testing), but I'm trying to be targeted in asking, what needs to
 happen
 to
  get the changes

Re: [VOTE] Buildr 1.4.6 release

[Alex Boisvert]

Vote passed with 3 +1's, no 0's and no -1's.

I'm going to push the release in the coming hour.

alex

On Tue, Jun 21, 2011 at 2:40 PM, Alex Boisvert alex.boisv...@gmail.comwrote:

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

 Specifically:
 http://people.apache.org/~boisvert/buildr/1.4.6/dist/buildr-1.4.6.tgz
 http://people.apache.org/~boisvert/buildr/1.4.6/dist/buildr-1.4.6.zip

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

 The official specification against which this release was tested:
 http://people.apache.org/~boisvert/buildr/1.4.6/site/specs.html

 Test coverage report:
 http://people.apache.org/~boisvert/buildr/1.4.6/site/coverage/index.html

 IMPORTANT NOTE:  This release includes JtestR support;  the code is same as
 for previous release except it was not tested during the release process.
  Caveat emptor.  Removal of JtestR support is currently under discussion on
 dev@buildr.apache.org.

 The following changes were made since 1.4.5:

   * Added:  Support for Scala 2.9.0+ (with help of Alexis Midon)
   * Fixed:  BUILDR-583 Update jruby install to use jruby version 1.6.1
 (Alexis Midon)
   * Fixed:  BUILDR-582 Revert the name change for the task to generate
 Intellij
 project files to 'idea'
   * Change: BUILDR-579 Format generated IDEA project files to look more
 like what
 IntelliJ generates (Peter Royal)
   * Change: BUILDR-574 Enhance idea task to generate test resources with
 test scope
 (Jean-Philippe Caruana)
   * Change: BUILDR-576 Upgrade to JUnit 4.8.2
   * Change: Upgrade to JRuby 1.6.2
   * Change: Scala 2.9.0-1 is now default, along with ScalaCheck 1.9,
 ScalaTest 1.6.1
 and Specs 1.6.8.
   * Change: ScalaCheck, ScalaTest and Specs now default to sane versions
 when using
 older Scala versions.
   * Fixed:  BUILDR-571 Generated IDEA projects include resources multiple
 times (Peter Royal)
   * Fixed:  BUILDR-573 HTTP upload PUT request with incorrect Content-Type
 (Mathias Doenitz)
   * Fixed:  BUILDR-578 Tar task does not preserve uid/gid on folders
 (Jean-Philippe Caruana)
   * Fixed:  BUILDR-251 Classifier not handled when downloading snapshot
 artifacts (Ryan Fowler)
   * Fixed:  BUILDR-585 TypeError : can't dup NilClass when merging jars
   * Fixed:  BUILDR-586 ScalaTest uses deprecated ant task (Martin Partel)
   * Fixed:  BUILDR-584 eclipse plugin should use absolute path
   * Fixed:  BUILDR-587 ScalaTest uses deprecated reporter parameters

Re: [VOTE] Buildr 1.4.6 release

[Alex Boisvert]

2011/6/22 Marc-André Laverdière marcandre.laverdi...@gmail.com

 That part worked well. Thanks!

 But I got something that didn't :(

 The auto-versioning after a release messed up:
 1.2-RC-5-SNAPSHOT - 1.2-RC-5 - 1.03-SNAPSHOT


Did this use to work in previous versions?

The release documentation (http://buildr.apache.org/releasing.html) is
pretty clear that it will increment the last digit of the 3-digit version
number if THIS_VERSION ends with -SNAPSHOT.   And you have several
alternatives to specify the next version number.

Unless this used to work, I don't see this bug as a blocker for the release.
 We can address it for the next version.

alex

Re: [VOTE] Buildr 1.4.6 release

[Alex Boisvert]

2011/6/22 Marc-André Laverdière marcandre.laverdi...@gmail.com

 That part worked well. Thanks!

 But I got something that didn't :(

 The auto-versioning after a release messed up:
 1.2-RC-5-SNAPSHOT - 1.2-RC-5 - 1.03-SNAPSHOT

 Huh ??? :(


Please open a ticket so we can help diagnose the issue.  I suspect it's a
bug introduced/regressed in 1.4.6 since there have been no changes in the
area of the code since 1.4.4.

alex

Re: [VOTE] Buildr 1.4.6 release

[Alex Boisvert]

On Wed, Jun 22, 2011 at 7:18 AM, Alex Boisvert alex.boisv...@gmail.comwrote:

 2011/6/22 Marc-André Laverdière marcandre.laverdi...@gmail.com

 That part worked well. Thanks!

 But I got something that didn't :(

 The auto-versioning after a release messed up:
 1.2-RC-5-SNAPSHOT - 1.2-RC-5 - 1.03-SNAPSHOT

 Huh ??? :(


 Please open a ticket so we can help diagnose the issue.  I suspect it's a
 bug introduced/regressed in 1.4.6 since there have been no changes in the
 area of the code since 1.4.4.


Sorry, meant to say I _don't think_ it's a bug introduced...

alex

[VOTE] Buildr 1.4.6 release

[Alex Boisvert]

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

Specifically:
http://people.apache.org/~boisvert/buildr/1.4.6/dist/buildr-1.4.6.tgz
http://people.apache.org/~boisvert/buildr/1.4.6/dist/buildr-1.4.6.zip

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

The official specification against which this release was tested:
http://people.apache.org/~boisvert/buildr/1.4.6/site/specs.html

Test coverage report:
http://people.apache.org/~boisvert/buildr/1.4.6/site/coverage/index.html

IMPORTANT NOTE:  This release includes JtestR support;  the code is same as
for previous release except it was not tested during the release process.
 Caveat emptor.  Removal of JtestR support is currently under discussion on
dev@buildr.apache.org.

The following changes were made since 1.4.5:

  * Added:  Support for Scala 2.9.0+ (with help of Alexis Midon)
  * Fixed:  BUILDR-583 Update jruby install to use jruby version 1.6.1
(Alexis Midon)
  * Fixed:  BUILDR-582 Revert the name change for the task to generate
Intellij
project files to 'idea'
  * Change: BUILDR-579 Format generated IDEA project files to look more like
what
IntelliJ generates (Peter Royal)
  * Change: BUILDR-574 Enhance idea task to generate test resources with
test scope
(Jean-Philippe Caruana)
  * Change: BUILDR-576 Upgrade to JUnit 4.8.2
  * Change: Upgrade to JRuby 1.6.2
  * Change: Scala 2.9.0-1 is now default, along with ScalaCheck 1.9,
ScalaTest 1.6.1
and Specs 1.6.8.
  * Change: ScalaCheck, ScalaTest and Specs now default to sane versions
when using
older Scala versions.
  * Fixed:  BUILDR-571 Generated IDEA projects include resources multiple
times (Peter Royal)
  * Fixed:  BUILDR-573 HTTP upload PUT request with incorrect Content-Type
(Mathias Doenitz)
  * Fixed:  BUILDR-578 Tar task does not preserve uid/gid on folders
(Jean-Philippe Caruana)
  * Fixed:  BUILDR-251 Classifier not handled when downloading snapshot
artifacts (Ryan Fowler)
  * Fixed:  BUILDR-585 TypeError : can't dup NilClass when merging jars
  * Fixed:  BUILDR-586 ScalaTest uses deprecated ant task (Martin Partel)
  * Fixed:  BUILDR-584 eclipse plugin should use absolute path
  * Fixed:  BUILDR-587 ScalaTest uses deprecated reporter parameters

Re: Working on CI build again

[Alex Boisvert]

JtestR is a huge pain to get working correctly due to its sensitivity to
environment/configuration.

I'm trying one more time to get it working for buildr 1.4.6 -- failing that
it will be removed.   No sense maintaining something in Buildr if the
authors of JtestR aren't maintaining it.And I don't want to hold back
Buildr for a feature that only 1-2 people are using.

alex


On Wed, Jun 8, 2011 at 7:21 PM, Antoine Toulme anto...@lunar-ocean.comwrote:

 8 tests not passing:
 https://builds.apache.org/job/Buildr-ci-build/226/testReport/

 It might be a problem with jtestr not being configured or not installed on
 vesta ?

 On Tue, Jun 7, 2011 at 07:57, Peter Donald pe...@realityforge.org wrote:

  Hi,
 
  On Tue, Jun 7, 2011 at 5:10 PM, Antoine Toulme anto...@lunar-ocean.com
  wrote:
   I was able to run successfully the build on the machine - I mean, the
  build
   ran to the end, I'm not sure all specs pass.
 
  great work. It would be good to get some visibility into the build again
 ;)
 
  --
  Cheers,
 
  Peter Donald
 

Re: BUILDR-251

[Alex Boisvert]

On Thu, May 19, 2011 at 7:35 PM, Ryan Fowler rwfow...@gmail.com wrote:

 I attached a spec/fix patch for BUILDR-251. I didn't see a way to reopen
 the issue so I thought I'd send a quick note to this list to make sure
 someone saw it. If the patch needs more work, let me know.

 https://issues.apache.org/jira/browse/BUILDR-251


Hi Ryan,

Thanks for the patch and the notice since I didn't get any notification from
Jira...  I've now applied your patch.

cheers,
alex

May 2011 Board Report

[Alex Boisvert]

FYI, I drafted our quarterly board report at:
https://cwiki.apache.org/confluence/display/BUILDR/May+2011+Board+Report
and will be submitting later today.

Feel free to chime in if you think I've missed anything...

alex

Re: Testing a change for pull request submittal?

[Alex Boisvert]

Hi Christopher,

Oh, I haven't seen your pull request... regardless... I forgot to say the
best way to notify other devs of a patch is to open a Jira, attach a copy of
the patch, make sure you click on the ASL license grant and if your work is
also on github (or wherever else) then link to it.

https://issues.apache.org/jira/browse/BUILDR

https://issues.apache.org/jira/browse/BUILDRalex


On Tue, Apr 26, 2011 at 10:00 PM, Christopher Coco cac...@gmail.com wrote:

 Hi Alex,

 Thanks for the info. I'll look into rspec. I submitted a pull request a
 couple of weeks ago (maybe rather hastily) for the TestNG changes I made.
 I'll try to write up a test to accompany them.

 Thanks again,
 Christopher


 On Tue, Apr 26, 2011 at 6:06 PM, Alex Boisvert alex.boisv...@gmail.com
 wrote:

  Hi Christopher,
 
  Pull requests are much appreciated!  And your JSP precompiler is a very
  nice
  first task.
 
  For testing, we use rspec.   If you're enhancing TestNG support, you
 would
  typically add to the TestNG specification (
  https://github.com/apache/buildr/blob/trunk/lib/buildr/java/tests.rb).
 
  If you get stuck, ask questions here or you can try to catch some of us
 on
  the IRC channel (#buildr on irc.freenode.net)
 
  alex
 
  On Tue, Apr 26, 2011 at 2:51 PM, Christopher Coco cac...@gmail.com
  wrote:
 
   Hey guys,
  
   I'm new to Buildr (and ruby in general) and am working on migrating our
   build from Maven to something that is more expressive in terms of
 project
   definition which is what drew us to Buildr. A couple of the necessary
   pieces
   we need before switching are expanded TestNG support (like supporting
   excluding/including by TestNG groups) and JSP pre-compilation (via
  tomcat6
   jasper). Simple things, right?
  
   Knowing little ruby when I started, I did managed to write a jsp
   precompiler
   extension (available here: https://gist.github.com/921897). I'm sure
  this
   code can be improved.
  
   As for the TestNG functionality, trying to get exclusion via TestNG
  groups
   (or any of the other cmd line options that TestNG allows) using the
   properties hash didn't work as the param and value are added to the
  TestNG
   runner as -D args instead of just as cmd line params. So, I forked the
   buildr project on github and made a few small tweaks to the tests.rb to
   pass
   along more parameters in the options array to the TestNG class. The
  change
   basically shims more cmd line parameters onto the string for TestNG
  runner.
  
   So my question is now, ok, I should probably test this -- like I
  mentioned,
   I'm extremely green with ruby -- what's the next step (or steps) so I
 can
   actually give some confidence (other than that we're actually running
 the
   fork here) that the change works so that my pull request is actually
  looked
   at for potential inclusion into the master branch? I'm a java guy and
   slowly
   learning ruby and ruby testing is somewhat alien to me right now. But,
 I
   think this functionality is useful (maybe I'm off-base, but we
 definitely
   need it and TestNG definitely supports it), so I'd like to actually
 help
   out
   here and contribute. I know the question is seemingly general (ruby
   testing), but I'm trying to be targeted in asking, what needs to happen
  to
   get the changes incorporated in the next version of Buildr? Am I going
   about
   this all wrong and should I submit an issue instead?
  
   Thanks,
   Christopher
   cac...@gmail.com
   https://github.com/cacoco
  
 

Re: bug : tar task does not preserve uid/gid on folders

[Alex Boisvert]

Thanks!  I applied the patch.

alex


On Fri, Mar 25, 2011 at 9:27 AM, Jean-Philippe Caruana 
jeanphilippe1.caru...@orange-ftgroup.com wrote:

 Hi all,

 I filed a bug under BUILDR-578.

 tar task does not preserve uid/gid on folders, but it does on files.
 I wasn't able to write a test to show the defect without being root for
 running tests, but I can submit a working patch.

 --
 Jean-Philippe Caruana
 --
 sorry for the crap that will be appended here:

 
 Ce message et toutes les pieces jointes (ci-apres le message) sont
 confidentiels et etablis a l'attention exclusive de ses destinataires.
 Toute utilisation ou diffusion non autorisee est interdite.
 Tout message electronique est susceptible d'alteration. Multimedia Business
 Services decline
 toute responsabilite au titre de ce message s'il a ete altere, deforme
 ou falsifie.
 Si vous n'etes pas destinataire de ce message, merci de le detruire
 immediatement et d'avertir l'expediteur.
 *
 This message and any attachments (the message) are confidential and
 intended solely for the addressees. Any unauthorised use or
 dissemination is prohibited.
 Messages are susceptible to alteration. Multimedia Business Services shall
 not be liable for the
 message if altered, changed or falsified.
 If you are not the intended addressee of this message, please cancel it
 immediately and inform the sender..
 

Re: junit default version

[Alex Boisvert]

I'll take care of it.  Thanks for the feedback.

alex

On Thu, Mar 17, 2011 at 7:35 AM, Jean-Philippe Caruana 
jeanphilippe1.caru...@orange-ftgroup.com wrote:

 Hi,

 the junit default version in buildr is still 4.7. This version is bogus (it
 plays the @Rules after the @Before methods where you might want to use your
 defined rules). The very last version (4.8.2) works very fine : we've used
 it every day on our project for months now. I would love to delete my
 junit: 4.8.2 line in my build.yaml file.

 Should I open a bug under JIRA for this ?

 ps : no test failed when I changed the default junit version in
 lib/buildr/java/tests.rb

 --
 Jean-Philippe Caruana
 --
 sorry for the crap that will be appended here:
 
 Ce message et toutes les pieces jointes (ci-apres le message) sont
 confidentiels et etablis a l'attention exclusive de ses destinataires.
 Toute utilisation ou diffusion non autorisee est interdite.
 Tout message electronique est susceptible d'alteration. Multimedia Business
 Services decline
 toute responsabilite au titre de ce message s'il a ete altere, deforme
 ou falsifie.
 Si vous n'etes pas destinataire de ce message, merci de le detruire
 immediatement et d'avertir l'expediteur.
 *
 This message and any attachments (the message) are confidential and
 intended solely for the addressees. Any unauthorised use or
 dissemination is prohibited.
 Messages are susceptible to alteration. Multimedia Business Services shall
 not be liable for the
 message if altered, changed or falsified.
 If you are not the intended addressee of this message, please cancel it
 immediately and inform the sender..
 

Maven SNAPSHOT timestamps

[Alex Boisvert]

So we got a nice
contributionhttps://issues.apache.org/jira/browse/BUILDR-572from
Brice Figureau to add timestamps when uploading Maven SNAPSHOT
artifacts.

As it stands, the feature is only enabled with --unique-version is passed on
the command-line or when Buildr.application.options.unique_version is set to
true.

I'm tempted to turn the feature on by default since I believe it's the right
thing to do (compatibility-wise) on Maven repos.  However, it could be a
breaking change if people currently depend on SNAPSHOTs being updated
in-place instead of uploading a new artifact with a timestamp.

Anybody has a strong opinion about this?

alex

Re: Auth for Buildr repositories.remote

[Alex Boisvert]

Hi Michael,

I think it's a good idea and I don't think it would be that much work.  Use
of repositories.remote for actual downloading seems to be fairly localized
in buildr/packaging/artifact.rb.

alex


On Thu, Mar 10, 2011 at 8:56 AM, Michael Guymon michael.guy...@gmail.comwrote:


 So I am interested in getting repositories.remote to support auth. The goal
 is to have buildr deploy to private maven repo's I have a work. What I would
 like to do is have the following be valid:

repositories.remote  'https://a.secure.repo/maven2'
repositories.remote  { :url = 'https://a.secure.repo/maven2' }
repositories.remote  { :url = 'https://a.secure.repo/maven2',
 :username = 'blah', :password = 'blah' }

 and possibly

repositories.remote  { :url = 'https://a.secure.repo/maven2',
 :priv_key = 'file' }


 I have sourced dived a little to see how repositories.remote is used, but I
 am not sure if this change would be a colossal PITA. If someone has a
 better/easier solution I would love to hear it.

 thanks,
 Michael

Buildr 1.4.5 released

[Alex Boisvert]

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.

http://buildr.apache.org

The following changes were made since 1.4.4:

  * Added:  BUILDR-555 Add support for the jaxb binding compiler (Mark
Petrovic)
  * Added:  BUILDR-554 Add support for OSGi bundle packages by importing the
buildr_bnd plugin
  * Added:  BUILDR-125 Add support for security-role in application.xml of
EAR packaging (Mikael Amborn)
  * Added:  BUILDR-550 Add support for groovydoc
  * Added:  BUILDR-521: System tray notifications for Linux systems
(via libnotify/notify-send)
  * Added:  BUILDR-537 Shell tasks should use JAVA_OPTS by default
  * Added:  BUILDR-538 Shell tasks should support passing :java_args
  * Added:  BUILDR-544 Support ${groupId} in pom files (Chris Dean)
  * Added:  BUILDR-552 Projects may now be defined using project(:name) and
a block
  * Added:  BUILDR-564 Add package(:scaladoc)
  * Added:  Automatically add require buildr/{groovy,scala}  when
generating
project if Groovy/Scala files are detected.
  * Change: BUILDR-540 Upgrade to rspec 2.1.0
  * Change: BUILDR-546 Upgrade to Rubyzip 0.9.4 (Michael Guymon)
  * Change: BUILDR-556 Merge buildr-iidea extension back into buildr.
  * Change: Upgrade default Scala compiler version to 2.8.1-final
  * Change: Upgrade to ScalaCheck 1.8
  * Change: Upgrade to ScalaTest 1.3
  * Change: Upgrade to Specs 1.6.6
  * Chagne: Upgrade to JRuby 1.5.6
  * Fixed:  BUILDR-542 Release task:  SVN tagging fails if parent tag
directory
does not exist yet (Gerolf Seitz)
  * Fixed:  BUILDR-543 POMs are installed and uploaded twice when using
artifacts
with classifier
  * Fixed:  BUILDR-522 Send notifications when continuous compilation
succeeds/fails.
  * Fixed:  BUILDR-551 Continuous compilation not working for project trees
  * Fixed:  BUILDR-557 MD5 + SHA1 checksums are not Maven compliant (Tammo
van Lessen)
  * Change: Upgrade to Groovy 1.7.5
  * Change: BUILDR-545 Add the ability to specify the description element in
in
application.xml contained within an ear.
  * Fixed:  BUILDR-547 - Ensure ECJ compiler works when there is a space in
the
path of dependencies.
  * Fixed:  BUILDR-558 Artifact uploads should show a progress bar (Tammo
van Lessen)
  * Fixed:  BUILDR-560 show a meaning full error message when POM cannot be
parsed
(Tammo van Lessen)
  * Fixed:  BUILDR-562 WAR package isn't updated if files under
src/main/webapp
are updated
  * Fixed:  BUILDR-569 Buildr fails under JRuby 1.6.0.RC1 due to read-only
$? variable
  * Fixed:  BUILDR-570 Buildr does not work with Rubygems 1.5.x
  * Fixed:  Scaladoc task would cause build to exit prematurely

Re: Dependency resolution with Maven's Aether

[Alex Boisvert]

On Fri, Feb 25, 2011 at 9:58 PM, Michael Guymon michael.guy...@gmail.comwrote:


 So I jumped straight into the fire and have created a basic dependency
 resolver using Aether for Buildr.
 https://github.com/mguymon/buildr-resolver


Nice work!


 It will take an array of dependencies and find their dependencies,
 returning the total of all dependencies. For example, if you pass it
 [org.apache.activemq:activemq-spring:jar:5.4.2] it returns an array of
 org.apache.activemq:activemq-spring:jar:5.4.2 and its 32 dependencies.

 Not surprising, it still needs work. It requires JRuby but I should be able
 to get it to work with RJB for vanilla Ruby support. Aether is downloading
 dependencies on its own, which needs to be disabled, so buildr can handle
 that part.

 buildr-resolver may cause conflicts due to the jars required to bootstrap
 Aether. Needs a way to load Aether without polluting the project runtime.
 Bootstrap deps -
 https://github.com/mguymon/naether/blob/master/src/main/java/com/slackworks/Bootstrap.java


Just an idea... you may want to load these in a separate ClassLoader
(assuming Aether doesn't require jars to be in the bootstrap classloader).

alex

[VOTE] Buildr 1.4.5 release

[Alex Boisvert]

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

Specifically:
http://people.apache.org/~boisvert/buildr/1.4.5/dist/buildr-1.4.5.tgz
http://people.apache.org/~boisvert/buildr/1.4.5/dist/buildr-1.4.5.zip

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

The official specification against which this release was tested:
http://people.apache.org/~boisvert/buildr/1.4.5/site/specs.html

Test coverage report:
http://people.apache.org/~boisvert/buildr/1.4.5/site/coverage/index.html


The following changes were made since 1.4.4:

  * Added:  BUILDR-555 Add support for the jaxb binding compiler (Mark
Petrovic)
  * Added:  BUILDR-554 Add support for OSGi bundle packages by importing the
buildr_bnd plugin
  * Added:  BUILDR-125 Add support for security-role in application.xml of
EAR packaging (Mikael Amborn)
  * Added:  BUILDR-550 Add support for groovydoc
  * Added:  BUILDR-521: System tray notifications for Linux systems
(via libnotify/notify-send)
  * Added:  BUILDR-537 Shell tasks should use JAVA_OPTS by default
  * Added:  BUILDR-538 Shell tasks should support passing :java_args
  * Added:  BUILDR-544 Support ${groupId} in pom files (Chris Dean)
  * Added:  BUILDR-552 Projects may now be defined using project(:name) and
a block
  * Added:  BUILDR-564 Add package(:scaladoc)
  * Added:  Automatically add require buildr/{groovy,scala}  when
generating
project if Groovy/Scala files are detected.
  * Change: BUILDR-540 Upgrade to rspec 2.1.0
  * Change: BUILDR-546 Upgrade to Rubyzip 0.9.4 (Michael Guymon)
  * Change: BUILDR-556 Merge buildr-iidea extension back into buildr.
  * Change: Upgrade default Scala compiler version to 2.8.1-final
  * Change: Upgrade to ScalaCheck 1.8
  * Change: Upgrade to ScalaTest 1.3
  * Change: Upgrade to Specs 1.6.6
  * Chagne: Upgrade to JRuby 1.5.6
  * Fixed:  BUILDR-542 Release task:  SVN tagging fails if parent tag
directory
does not exist yet (Gerolf Seitz)
  * Fixed:  BUILDR-543 POMs are installed and uploaded twice when using
artifacts
with classifier
  * Fixed:  BUILDR-522 Send notifications when continuous compilation
succeeds/fails.
  * Fixed:  BUILDR-551 Continuous compilation not working for project trees
  * Fixed:  BUILDR-557 MD5 + SHA1 checksums are not Maven compliant (Tammo
van Lessen)
  * Change: Upgrade to Groovy 1.7.5
  * Change: BUILDR-545 Add the ability to specify the description element in
in
application.xml contained within an ear.
  * Fixed:  BUILDR-547 - Ensure ECJ compiler works when there is a space in
the
path of dependencies.
  * Fixed:  BUILDR-558 Artifact uploads should show a progress bar (Tammo
van Lessen)
  * Fixed:  BUILDR-560 show a meaning full error message when POM cannot be
parsed
(Tammo van Lessen)
  * Fixed:  BUILDR-562 WAR package isn't updated if files under
src/main/webapp
are updated
  * Fixed:  BUILDR-569 Buildr fails under JRuby 1.6.0.RC1 due to read-only
$? variable
  * Fixed:  BUILDR-570 Buildr does not work with Rubygems 1.5.x
  * Fixed:  Scaladoc task would cause build to exit prematurely

IntelliJ IDEA specs failing

[Alex Boisvert]

Hi Peter,

Running the IDEA specs today, I'm getting:

  1) Buildr::IntellijIdea Buildr::IntellijIdea::IdeaModule with
local_repository_env_override = nil base_directory on different drive on
windows generates relative paths correctly
 Failure/Error: @foo.iml.send(:resolve_path, E:/foo).should
eql('E:/foo')

 expected E:/foo
  got $MODULE_DIR$/../../E:/foo

 (compared using eql?)
 # ./spec/ide/idea_spec.rb:1030

Is this something you can reproduce?

alex


On Sun, Jan 30, 2011 at 4:40 PM, Peter Donald pe...@realityforge.orgwrote:

 Hi,

 I tested it out on all our builds and only found one issue. JIRA is
 down for system maintenance right nowso I have attached a patch to
 address this but am away from the computer with the key to access svn
 atm. So if you could make sure this change gets in before release I am
 +1 for a release. The message for the commit should be something like

 
 Ensure that the IDEA module is generated correctly when the module
 contains no java files.

 Without this change the output directory would be the project root
 which would end up being excluded as a result. This problem was caused
 by the refactor of the plugin prior to migrating it into buildr core.
 

 On Fri, Jan 28, 2011 at 4:54 PM, Alex Boisvert alex.boisv...@gmail.com
 wrote:
  I'm thinking about releasing Buildr 1.4.5 towards end of next week.  I
 want
  to keep pushing regular releases out and I think we have a fair number of
  issues/changes that would benefit our users.
 
  If you want to get anything else in this release or feel the timing isn't
  right, please shout.

 --
 Cheers,

 Peter Donald

Re: Buildr idea / idea7x failed on ruby 1.9.x -- String no long has method sort

[Alex Boisvert]

Hi Chiaming,

Thanks for reporting this.  I think it's better open a separate issue.

alex

On Tue, Jan 11, 2011 at 11:43 AM, Chiaming Hsu camy...@yahoo.com wrote:

 I ran into an issue today where idea / idea7x project generations uses
 method
 sort on String.  This won't work for ruby 1.9.x:

 $ buildr idea7x
 (in /home/camyhsu/code/bug-submit/buildr/ruby1.9-idea, development)
 Writing
 /home/camyhsu/code/bug-submit/buildr/ruby1.9-idea/ruby1.9-idea-test-7x.ipr
 Writing

 /home/camyhsu/code/bug-submit/buildr/ruby1.9-idea/subproject/ruby1.9-idea-test-subproject-7x.iml

 Buildr aborted!
 NoMethodError : undefined method `sort' for src/test/java:String

 (See full trace by running task with --trace)
 $


 Is this a known issue?  I saw a ticket for ruby 1.9 compatibility.  Should
 I add
 a comment to that ticket or open a new bug under IDE integration?

 Cheers,
 Chiaming Hsu

Re: Continuous Testing

[Alex Boisvert]

I think the idea was brought up but nobody's started working on it.

Be our guest! :)

alex

On Mon, Jan 3, 2011 at 10:45 AM, pablo fernandez fernandezpabl...@gmail.com
 wrote:

 Hey Buildr Crew!

 Just wondering if you were planning to support a Continuous Testing task.
 It will be something like cc but that also runs your test suite (like
 autotest).

 I think this would rock. I'm even volunteering for the job if it's not
 planned and you guys want the feature in.

 Pablo

 PS: Thanks for creating buildr.