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

[Alex Boisvert]

Sorry for the delay... +1 from me.

(Tested only on Linux)

On Tue, Dec 5, 2017 at 2:50 PM, Antoine Toulme  wrote:

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

Re: [VOTE] Buildr 1.5.4 release

[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.2 release

[Alex Boisvert]

+1

On Sun, Apr 2, 2017 at 4:41 PM, Peter Donald  wrote:

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

Re: [VOTE] Buildr 1.5.1 release

[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  wrote:

> My login is “toulmean”. Sorry for the confusion.
>
> > On Nov 2, 2016, at 5:56 PM, Alex Boisvert 
> 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 
> 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 
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 
> 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: [VOTE] Buildr 1.5.0 release

[Alex Boisvert]

Agreed - you're on a roll.  Thanks!

On Tue, Oct 4, 2016 at 1:29 PM, Peter Donald  wrote:

> Great work - thanks!
>
> On Tue, Oct 4, 2016 at 11:39 PM, Antoine Toulme 
> wrote:
>
> > Thank you all! The release vote passes with 3 +1 binding votes.
> >
> > > On Sep 27, 2016, at 12:16 PM, Alex Boisvert 
> > wrote:
> > >
> > > Have not done any testing but here's my +1 for the release.
> > >
> > > On Sep 25, 2016 4:26 PM, "Peter Donald" 
> wrote:
> > >
> > >> Hi,
> > >>
> > >> All my tests pass so here is my +1 :)
> > >>
> > >> On Sat, Sep 24, 2016 at 3:27 PM, Antoine Toulme 
> > >> wrote:
> > >>
> > >>> OK, sorry it took me a while to circle back and cut RC2.
> > >>>
> > >>> Here is my +1.
> > >>>
> > >>>> On Sep 23, 2016, at 10:18 PM, Antoine Toulme 
> > >>> wrote:
> > >>>>
> > >>>> We're voting on the source distributions available here:
> > >>>> https://dist.apache.org/repos/dist/dev/buildr/1.5.0.RC2/dist/
> > >>>>
> > >>>> Specifically:
> > >>>> https://dist.apache.org/repos/dist/dev/buildr/1.5.0.RC2/
> > >>> dist/buildr-1.5.0.tgz
> > >>>> https://dist.apache.org/repos/dist/dev/buildr/1.5.0.RC2/
> > >>> dist/buildr-1.5.0.zip
> > >>>>
> > >>>> The documentation generated for this release is available here:
> > >>>> https://dist.apache.org/repos/dist/dev/buildr/1.5.0.RC2/site/
> > >>>> https://dist.apache.org/repos/dist/dev/buildr/1.5.0.RC2/
> > >> site/buildr.pdf
> > >>>>
> > >>>> The following changes were made since 1.4.25:
> > >>>>
> > >>>> * Change: Update RJB to 1.5.4
> > >>>> * Change: Update rubyzip to 1.2.0
> > >>>> * Change: Update hoe to 3.15.0
> > >>>> * Change: Update net-ssh to 3.1.1
> > >>>> * Change: Update json_pure to 1.8.3
> > >>>> * Change: Update diff-lcs to 1.2.5
> > >>>> * Change: Update xml-simple to 1.1.5
> > >>>> * Change: Update jekyll to 3.1.3
> > >>>> * Change: Update rdoc to 4.2.2
> > >>>> * Change: Update ecj to 4.5.1
> > >>>> * Change: Added jekyll-textile-converter 0.1.0 to generate the site.
> > >>>> * Change: Move to default on Scala 2.11.
> > >>>> * Change: Remove Buildr::Project#on_define, deprecated in 1.3
> > >>>> * Change: Remove JavaWrapper, deprecated in 1.3
> > >>>> * Change: Remove JUnit::REQUIRES, deprecated in 1.3.3
> > >>>> * Change: Remove TestNG::REQUIRES, deprecated in 1.3.3
> > >>>> * Change: Remove Buildr::Ant::REQUIRES, deprecated in version 1.3.3
> > >>>> * Change: Remove Buildr::CompileTask#classpath, deprecated in
> version
> > >>> 1.3
> > >>>> * Change: Remove Buildr::TestTask responding to :using with
> > >>> .using('foo','bar'), deprecated in version 1.3
> > >>>> * Change: Remove addon/buildr/cobertura.rb, deprecated since 1.3.4
> > >>>> * Change: Remove addon/buildr/emma.rb, deprecated since 1.3.4
> > >>>> * Change: Remove support for Rakefile/rakefile, deprecated.
> > >>>> * Change: Remove project#target, project#reports, deprecated.
> > >>>> * Change: Remove JBehave::REQUIRES, deprecated.
> > >>>> * Change: Remove JMock::REQUIRES, deprecated.
> > >>>> * Change: Remove ScalaCheck::REQUIRES, deprecated.
> > >>>> * Change: Change Eclipse Scala project natures from
> > >>> ch.epfl.lamp.sdt.core.scalanature to org.scala-ide.sdt.core.
> > scalanature
> > >>>> * Change: Fix the custom Google search widget on the website.
> > >>>> * Change: BUILDR-722 Remove links and image of the buildr book from
> > >> the
> > >>> website.
> > >>>> * Added:  Travis badge to README.rdoc
> > >>>> * Added:  Added Rubygems badges to README.rdoc
> > >>>> * Added:  BUILDR-577 Allow remote repo to be added with http basic
> > >> auth
> > >>> support. Submitted by Michael Guymon.
> > >>>> * Added:  BUILDR-523 Issue a warning when Java.classpath is modified
> > >>> after Java.lo

Re: [VOTE] Buildr 1.5.0 release

[Alex Boisvert]

Have not done any testing but here's my +1 for the release.

On Sep 25, 2016 4:26 PM, "Peter Donald"  wrote:

> Hi,
>
> All my tests pass so here is my +1 :)
>
> On Sat, Sep 24, 2016 at 3:27 PM, Antoine Toulme 
> wrote:
>
> > OK, sorry it took me a while to circle back and cut RC2.
> >
> > Here is my +1.
> >
> > > On Sep 23, 2016, at 10:18 PM, Antoine Toulme 
> > wrote:
> > >
> > > We're voting on the source distributions available here:
> > > https://dist.apache.org/repos/dist/dev/buildr/1.5.0.RC2/dist/
> > >
> > > Specifically:
> > > https://dist.apache.org/repos/dist/dev/buildr/1.5.0.RC2/
> > dist/buildr-1.5.0.tgz
> > > https://dist.apache.org/repos/dist/dev/buildr/1.5.0.RC2/
> > dist/buildr-1.5.0.zip
> > >
> > > The documentation generated for this release is available here:
> > > https://dist.apache.org/repos/dist/dev/buildr/1.5.0.RC2/site/
> > > https://dist.apache.org/repos/dist/dev/buildr/1.5.0.RC2/
> site/buildr.pdf
> > >
> > > The following changes were made since 1.4.25:
> > >
> > >  * Change: Update RJB to 1.5.4
> > >  * Change: Update rubyzip to 1.2.0
> > >  * Change: Update hoe to 3.15.0
> > >  * Change: Update net-ssh to 3.1.1
> > >  * Change: Update json_pure to 1.8.3
> > >  * Change: Update diff-lcs to 1.2.5
> > >  * Change: Update xml-simple to 1.1.5
> > >  * Change: Update jekyll to 3.1.3
> > >  * Change: Update rdoc to 4.2.2
> > >  * Change: Update ecj to 4.5.1
> > >  * Change: Added jekyll-textile-converter 0.1.0 to generate the site.
> > >  * Change: Move to default on Scala 2.11.
> > >  * Change: Remove Buildr::Project#on_define, deprecated in 1.3
> > >  * Change: Remove JavaWrapper, deprecated in 1.3
> > >  * Change: Remove JUnit::REQUIRES, deprecated in 1.3.3
> > >  * Change: Remove TestNG::REQUIRES, deprecated in 1.3.3
> > >  * Change: Remove Buildr::Ant::REQUIRES, deprecated in version 1.3.3
> > >  * Change: Remove Buildr::CompileTask#classpath, deprecated in version
> > 1.3
> > >  * Change: Remove Buildr::TestTask responding to :using with
> > .using('foo','bar'), deprecated in version 1.3
> > >  * Change: Remove addon/buildr/cobertura.rb, deprecated since 1.3.4
> > >  * Change: Remove addon/buildr/emma.rb, deprecated since 1.3.4
> > >  * Change: Remove support for Rakefile/rakefile, deprecated.
> > >  * Change: Remove project#target, project#reports, deprecated.
> > >  * Change: Remove JBehave::REQUIRES, deprecated.
> > >  * Change: Remove JMock::REQUIRES, deprecated.
> > >  * Change: Remove ScalaCheck::REQUIRES, deprecated.
> > >  * Change: Change Eclipse Scala project natures from
> > ch.epfl.lamp.sdt.core.scalanature to org.scala-ide.sdt.core.scalanature
> > >  * Change: Fix the custom Google search widget on the website.
> > >  * Change: BUILDR-722 Remove links and image of the buildr book from
> the
> > website.
> > >  * Added:  Travis badge to README.rdoc
> > >  * Added:  Added Rubygems badges to README.rdoc
> > >  * Added:  BUILDR-577 Allow remote repo to be added with http basic
> auth
> > support. Submitted by Michael Guymon.
> > >  * Added:  BUILDR-523 Issue a warning when Java.classpath is modified
> > after Java.load has happened
> > >  * Added:  BUILDR-594 Added support for changing the verification mode
> > of SSL certificates
> > >  * Added:  BUILDR-595 Added support to providing custom SSL
> certificates
> > >  * Added:  BUILDR-572 Allow to upload unique version (timestamp based)
> > snapshot artifacts to a repository. Submitted by Brice Figureau.
> > >  * Fixed:  BUILDR-207 remove 'Skipping tests' messages
> > >  * Added:  BUILDR-703 release: allow THIS_VERSION to be defined in
> > another file
> > >  * Fixed:  BUILDR-674 Artifacts with bundle extension cannot be
> > downloaded by Buildr
> > >  * Fixed:  BUILDR-565 resources are not included in the war if defined
> > after package call
> > >  * Fixed:  BUILDR-621 ZipTask creates zip file with entries not sorted
> > by path causing very slow unzipping.
> > >  * Fixed:  BUILDR-695 transitive doesn't support
> > ${project.parent.version} in POM.
> > >  * Fixed:  BUILDR-653 Using Eclipse compiler (ECJ)
> > >  * Fixed:  BUILDR-476 Buildr doesn't respect company repository manager
> > >  * Fixed:  BUILDR-454 Definition-level parent-child references-by-name
> > fail in 1.4.0 but not in 1.3.5. Submitted by Rhett Sutphin.
> > >  * Fixed:  BUILDR-620 resources.filter should not run on non-text files
> > >  * Fixed:  BUILDR-489 Java + Scala joint compiler fails if default
> > encoding and source file encoding are not same and special characters
> have
> > been used in source code
> > >  * Fixed:  BUILDR-486 Buildr-generated poms should include dependencies
> > >  * Fixed:  BUILDR-723 JavaTestFilter is unable to parse paths
> containing
> > %2F
> > >  * Change: Update the custom_pom addon to generate poms with exclusions
> > section that excludes
> > >all transitive dependencies. This is required as buildr
> > dependencies are not
> > >transitive while Maven's dependencies are transitive by
> > defa

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: Creating 1.5.1 and jira access rights

[Alex Boisvert]

Antoine - I made you admin of the BUILDR project in Jira.

On Tue, Aug 23, 2016 at 5:43 PM, Peter Donald 
wrote:

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

Re: require 'buildr/scala'

[Alex Boisvert]

Also curious how that would work but if it's just a simple check for,
e.g.,src/main/scala/**.scala. then all is well.

On Sun, Aug 21, 2016 at 6:33 PM, Peter Donald 
wrote:

> What is the impact if the project does not use scala?
>
> On Mon, Aug 22, 2016 at 11:32 AM, Antoine Toulme
>  wrote:
> > Hello all,
> >
> > would it make sense to remove the need to explicitly require
> ‘buildr/scala’? I’d like to have my Scala sources detected by default.
> >
> > Please let me know what you think?
> >
> > Antoine
>
>
>
> --
> Cheers,
>
> Peter Donald
>

Re: 1.5.pre

[Alex Boisvert]

I think that's a good idea.

On Wed, Aug 17, 2016 at 12:43 AM, Antoine Toulme 
wrote:

> We have 6 issues left total for 1.5. Two of them (the 2 major ones) are
> documentation/installation stories.
>
> I propose we cut a -pre gem version and have the community test it for a
> little while.
>
> Please let me know if you feel like a different course makes sense.
>
> Cheers,
>
> Antoine

Re: Update on development for 1.5

[Alex Boisvert]

Ha ha.  You can't win the Java game in "hard mode" without dealing with the
classloader bosses. ;)

On Aug 16, 2016 7:43 AM, "Antoine Toulme"  wrote:

> It took a while to get it right.
>
> -I needed a Java wrapper class to call out to the Main object on the
> compiler. I took after Specs2Runner.
> -Even then, zinc kept failing missing scala.reflect packages. This was
> very weird since the classpath definitely contained those classes.
> I eventually found out that zinc plays with the classloader and takes
> several arguments: -scala-library, -scala-compiler, and a new one,
> -scala-extra. (https://github.com/typesafehub/zinc <https://github.com/
> typesafehub/zinc> gave it away).
> Adding -scala-extra, pointing at the scala-reflect jar fixed the issue.
>
> Cheers,
>
> Antoine
>
> > On Aug 16, 2016, at 7:20 AM, Alex Boisvert 
> wrote:
> >
> > Nice, thanks for bringing zinc back.
> >
> > On Mon, Aug 15, 2016 at 11:38 PM, Antoine Toulme 
> > 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 
> wrote:
> >>>
> >>> On Aug 15, 2016, at 3:47 PM, Alex Boisvert 
> >> wrote:
> >>>>
> >>>> On Mon, Aug 15, 2016 at 3:24 PM, Antoine Toulme 
> >> wrote:
> >>>>
> >>>>> Two things had to go to make it happen:
> >>>>> -the Zinc compiler’s last release was 6 years ago, and it doesn’t
> seem
> >> to
> >>>>> play well with the latest. I have removed it.
> >>>>>
> >>>>
> >>>> Zinc's last release was about a month ago (July 3rd);  I think you
> might
> >>>> have been looking at older artifacts / older organization in maven2
> >> repo?
> >>>>
> >>>> https://github.com/typesafehub/zinc
> >>>>
> >>>> No biggie, just mentioning it.
> >>>
> >>> OK, I missed it:
> >>> http://central.maven.org/maven2/com/typesafe/zinc/zinc/0.3.12/ <
> >> http://central.maven.org/maven2/com/typesafe/zinc/zinc/0.3.12/>
> >>>
> >>> OK, let me try to bring this back in.
> >>>
> >>> I looked at this new Zinc incarnation from SBT and found that it has a
> >> first 1.0.0-X1 build out there:
> >>> http://mvnrepository.com/artifact/org.scala-sbt/zinc_2.11 <
> >> http://mvnrepository.com/artifact/org.scala-sbt/zinc_2.11>
> >>>
> >>> Here is the code:
> >>> https://github.com/sbt/zinc <https://github.com/sbt/zinc>
> >>>
> >>> I tried to use it but could not find the main class like the old one.
> >>
> >>
>
>

Re: Update on development for 1.5

[Alex Boisvert]

Nice, thanks for bringing zinc back.

On Mon, Aug 15, 2016 at 11:38 PM, Antoine Toulme 
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  wrote:
> >
> > On Aug 15, 2016, at 3:47 PM, Alex Boisvert 
> wrote:
> >>
> >> On Mon, Aug 15, 2016 at 3:24 PM, Antoine Toulme 
> wrote:
> >>
> >>> Two things had to go to make it happen:
> >>> -the Zinc compiler’s last release was 6 years ago, and it doesn’t seem
> to
> >>> play well with the latest. I have removed it.
> >>>
> >>
> >> Zinc's last release was about a month ago (July 3rd);  I think you might
> >> have been looking at older artifacts / older organization in maven2
> repo?
> >>
> >> https://github.com/typesafehub/zinc
> >>
> >> No biggie, just mentioning it.
> >
> > OK, I missed it:
> > http://central.maven.org/maven2/com/typesafe/zinc/zinc/0.3.12/ <
> http://central.maven.org/maven2/com/typesafe/zinc/zinc/0.3.12/>
> >
> > OK, let me try to bring this back in.
> >
> > I looked at this new Zinc incarnation from SBT and found that it has a
> first 1.0.0-X1 build out there:
> > http://mvnrepository.com/artifact/org.scala-sbt/zinc_2.11 <
> http://mvnrepository.com/artifact/org.scala-sbt/zinc_2.11>
> >
> > Here is the code:
> > https://github.com/sbt/zinc <https://github.com/sbt/zinc>
> >
> > I tried to use it but could not find the main class like the old one.
>
>

Re: Update on development for 1.5

[Alex Boisvert]

BTW, this is great!  Looking forward to 1.5.

Has anybody looked at deprecations?  We could remove anything that's been
marked as deprecated in 1.3.x and before.

https://cwiki.apache.org/confluence/display/BUILDR/Backward+Compatibility


On Mon, Aug 15, 2016 at 3:24 PM, Antoine Toulme  wrote:

> OK,
>
> we now have support for Scala 2.11.
>
> Two things had to go to make it happen:
> -the Zinc compiler’s last release was 6 years ago, and it doesn’t seem to
> play well with the latest. I have removed it.
> -specs vs specs2. specs would not work with 2.11. I have removed it.
>
> Also, as a bonus we now run our test suite on JDK8. Happy to report all
> tests pass and we have a great streak of green builds:
> https://travis-ci.org/apache/buildr/builds  buildr/builds>
>
> We’re down to 8 issues for 1.5, 4 of them major ones.
>
> Cheers,
>
> Antoine
>
> > On Aug 14, 2016, at 12:41 AM, Antoine Toulme 
> wrote:
> >
> > Cool, thanks!
> >
> > Further updates on development.
> >
> > We have 6 major issues remaining on the 1.5 roadmap.
> > Still no progress on the Scala 2.11 upgrade, because I’m lazy.
> >
> > Cheers,
> >
> > Antoine
> >
> >> On May 22, 2016, at 3:47 AM, Peter Donald 
> wrote:
> >>
> >> Actually went and updated custom_pom to do this as this shouuld be done
> anyway.
> >>
> >> On Sun, May 22, 2016 at 8:02 PM, Peter Donald 
> wrote:
> >>> We may also need to change the way we output dependencies from
> >>>
> >>> 
> >>>   com.biz
> >>>   app
> >>>   1.0
> >>> 
> >>>
> >>> to
> >>>
> >>> 
> >>>   com.biz
> >>>   app
> >>>   1.0
> >>>   
> >>>   
> >>>   *
> >>>   *
> >>>   
> >>>   
> >>> 
> >>>
> >>> As Maven assumes transitive dependencies and buildr assumes no
> >>> transitive dependencies.
> >>
> >>
> >> --
> >> Cheers,
> >>
> >> Peter Donald
> >
>
>

Re: Update on development for 1.5

[Alex Boisvert]

On Mon, Aug 15, 2016 at 3:24 PM, Antoine Toulme  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.

Buildr Status Report

[Alex Boisvert]

-
Attachment K: 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 previously, I (Alex Boisvert) have decided to step down as
PMC Chair for the Buildr project.  Following the recent vote
(
https://lists.apache.org/thread.html/5b3b645bd4bda001c4b9f749efea7e18aa41efa4342e0bfad45416fc@%3Cprivate.buildr.apache.org%3E),

Antoine Toulme should become our next PMC Chair.  I will send a resolution
for the Board to approve/reject.

Otherwise, we have no issues that require board attention

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

[Alex Boisvert]

+1

On Thu, Apr 21, 2016 at 5:28 PM, Peter Donald 
wrote:

> Hi,
>
> +1
>
> Thanks for taking the lead.  I ran a set of test builds and all seems a-ok.
>
> On Tue, Apr 19, 2016 at 4:07 PM, Antoine Toulme 
> wrote:
> > We're voting on the source distributions available here:
> > http://home.apache.org/~toulmean/buildr/1.4.25/dist/
> >
> > Specifically:
> > http://home.apache.org/~toulmean/buildr/1.4.25/dist/buildr-1.4.25.tgz
> > http://home.apache.org/~toulmean/buildr/1.4.25/dist/buildr-1.4.25.zip
> >
> > The documentation generated for this release is available here:
> > http://home.apache.org/~toulmean/buildr/1.4.25/site/
> > http://home.apache.org/~toulmean/buildr/1.4.25/site/buildr.pdf
> >
> > The following changes were made since 1.4.24:
> >
> >   * Change: BUILDR-712 Update jruby-openssl dependency version or
> support a range of versions
> >   * Change: Update gwt addon to add the GWT artifacts to project
> dependencies as specs rather
> > than files.
> >   * Change: Support the project.root_project utility method to retrieve
> the top level project.
>
>
>
> --
> 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: New release

[Alex Boisvert]

Same here.  Go for it.
On Mar 14, 2016 12:11 PM, "Peter Donald"  wrote:

> Sounds good to me.
>
> On Tue, Mar 15, 2016 at 4:22 AM, Antoine Toulme 
> wrote:
> > Hey folks,
> >
> > it’s been a while since the last release. There’s about a dozen changes
> in the CHANGELOG:
> > https://github.com/apache/buildr/blob/master/CHANGELOG <
> https://github.com/apache/buildr/blob/master/CHANGELOG>
> >
> > I believe it would be a good time to run a release. With your
> permission, I’ll get started on rolling out a RC.
> >
> > Cheers,
> >
> > Antoine
>
>
>
> --
> Cheers,
>
> Peter Donald
>

Buildr board report

[Alex Boisvert]

-
Attachment F: 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.23) happened on June 12th, 2015.

Development and community activity (mailing lists, bug reports, etc.)
remains
relatively low. Our last committer/PMC change happened in October 2013.

We have no issues that require board attention.

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

Status report for the 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.

We made one minor release (v1.4.22 on March 5th) since our last board
report.

Development and community activity (mailing lists, bug reports, etc.)
remains relatively low. Our last committer/PMC change happened in October
2013.

We have no issues that require board attention.

Re: [VOTE] Buildr 1.4.22 release

[Alex Boisvert]

+1 (did quick sanity checks on OSX)


On Sat, Feb 28, 2015 at 2:43 AM, Peter Donald 
wrote:

> We're voting on the source distributions available here:
> http://people.apache.org/~donaldp/buildr/1.4.22/dist/
>
> Specifically:
> http://people.apache.org/~donaldp/buildr/1.4.22/dist/buildr-1.4.22.tgz
> http://people.apache.org/~donaldp/buildr/1.4.22/dist/buildr-1.4.22.zip
>
> The documentation generated for this release is available here:
> http://people.apache.org/~donaldp/buildr/1.4.22/site/
> http://people.apache.org/~donaldp/buildr/1.4.22/site/buildr.pdf
>
> The following changes were made since 1.4.21:
>
>   * Change: BUILDR-704 - Updated the Sonar addon to support the latest
> version of SonarQube Runner. Submitted by Ross Mahony.
>   * Added:  Add support for ipr.add_glassfish_remote_configuration
> method that generates a remote glassfish configuration in IntelliJ
> IDEA project files.
>   * Added:  Add support for iml.prefix and ipr.prefix settings that
> prefix the generated IntelliJ IDEA project and module files.
>   * Change: Update the buildr gemspec so that rspec is no longer a
> required dependency. This enables end-users to use a different version
> of rspec and buildr in the same project. The rspec version MUST be be
> compatible with the version used by Buildr if rspec features are used
> from within Buildr. Buildr also issues a warning if the `check` method
> is called and rspec has not been loaded. The warning includes
> directions on how to resolve the issue. Submitted by r6p.
>   * Fixed:  A long standing bug existed such that if tests failed to
> compile, and the option Buildr.options.test is set to :all then the
> compilation error would not result in a failed build. As many people
> set the Buildr.options.test to :all in their continuous
> delivery/integration tools, this has caused some problems. This has
> been fixed by ensuring all the problems associated with the resolving
> the prerequisites are not caught when Buildr.options.test is set to
> :all.
>   * Change: Update checkstyle to 6.1.1. Submitted by neher.
>   * Fixed:  Avoid empty dependency issue in gwt addon if the
> attempting to gwt compile a project that has no src/main/java.
>   * Fixed:  Support dependencies in the gwt addon that are other local
> projects rather that artifacts, without forcing a compilation of
> dependency when parsing buildfile.
>   * Added:  Support configuration of sql dialect mapping in IDEA
> generated project files through methods on the ipr extension
> ipr.mssql_dialect_mapping, ipr.postgres_dialect_mapping and
> ipr.sql_dialect_mappings
>   * Added:  Support specification of the target project to which the
> gwt compilation artifacts are added as an asset, by using
> :target_project option.
>
> --
> Cheers,
>
> Peter Donald
>

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

> +1
>
>
> On Sun, Jul 6, 2014 at 10:23 PM, Antoine Toulme 
> wrote:
>
> > +1
> >
> >
> > On Sat, Jul 5, 2014 at 6:12 PM, Peter Donald 
> > 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 wrote:

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

> +1,
>   Tammo
>
>
> On Sat, May 3, 2014 at 7:23 AM, Peter Donald 
> 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: Moving Buildr to use Git as the primary source control system

[Alex Boisvert]

awesome!  thanks for pushing on this Peter.


On Tue, Feb 18, 2014 at 12:50 PM, Peter Donald wrote:

> Hi,
>
> Okay, the nice Apache infrastructure people have flipped the switch
> and our primary source control is now git. To get write access you
> need to use https://git-wip-us.apache.org/repos/asf/buildr.git
>
> Over the next little bit I will try to go through and update the
> documentation to reflect the move.
>
>
> On Thu, Feb 13, 2014 at 8:27 AM, Peter Donald 
> wrote:
> > Hi,
> >
> > Apache now seems to have relatively mature support for using git as
> > the primary source control system. From what I recall most people
> > seemed to prefer Git - does anyone object to moving our primary
> > mechanism to git?
> >
> > --
> > Cheers,
> >
> > Peter Donald
>
>
>
> --
> Cheers,
>
> Peter Donald
>

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

> git != Gitub. ie: moving to git is not the same as
> using Github.
> On Feb 13, 2014, at 12:34 PM, Antoine Toulme 
> 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  >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

New PMC member: Peter Donald

[Alex Boisvert]

It's my pleasure to announce that Peter Donald has joined the Project
Management Committee of the Apache Buildr project.

As most of you already know, Peter has been very active in the project over
the past 3 years, contributing numerous features, fixing things, handling
the past few releases all by himself and improving the process while at it.

This new responsibility is a recognition of his continued dedication to the
project.

Thanks Peter!

Re: [VOTE] Buildr 1.4.15 release

[Alex Boisvert]

+1 for the release with the caveat that I can't do any testing since I'm in
the woods with no computer access.
On Oct 26, 2013 1:02 AM, "Peter Donald"  wrote:

> We're voting on the source distributions available here:
> http://people.apache.org/~donaldp/buildr/1.4.15/dist/
>
> Specifically:
> http://people.apache.org/~donaldp/buildr/1.4.15/dist/buildr-1.4.15.tgz
> http://people.apache.org/~donaldp/buildr/1.4.15/dist/buildr-1.4.15.zip
>
> The documentation generated for this release is available here:
> http://people.apache.org/~donaldp/buildr/1.4.15/site/
> http://people.apache.org/~donaldp/buildr/1.4.15/site/buildr.pdf
>
> The following changes were made since 1.4.14:
>
>   * Change: Updated the 'test_jar' package type to have a
> classifier of 'tests' and thus match maven
> conventions. Reported by Chris Bozic.
>   * Fixed:  BUILDR-689 - Ensure that war file includes generated
> assets rather than the "source" assets that may have
> been filtered.
>   * Fixed:  BUILDR-689 - Define assets task before the project is
> defined to avoid "undefined method `project='" if the
> project attempts to generate into the same directory.
>   * Added:  BUILDR-679 - Support uploading to a snapshot repository
> defined by repositories.snapshot_to if the artifact is
> a snapshot. Submitted by Tammo van Lessen.
>   * Change: Update the jaxb_xjc addon to add output directory to
> generated IDEA project files.
>   * Change: Update the default output directory used in the jaxb_xjc
> addon to use Maven conventions.
>   * Fixed:  Bug in IdeaProject.partition_dependencies resulted in
> projects being rebuilt if artifacts were added to the
> project with dependencies on the current project.
>   * Fixed:  BUILDR-605 - Ensure package task invokes included paths.
>   * Fixed:  BUILDR-609 - compile.from should accept Task argument.
>

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

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

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

> +1, of course.
>
>
> On Sat, May 4, 2013 at 12:09 AM, Peter Donald  >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 wrote:

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

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

> 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: [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 wrote:

> Hi,
>
> On Thu, Feb 21, 2013 at 9:49 AM, Peter Donald 
> wrote:
> > On Wed, Feb 20, 2013 at 3:47 PM, Antoine Toulme 
> 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: Migration to Apache CMS & svnpubsub

[Alex Boisvert]

Sweet.  Thanks for pushing on that!

On Wed, Mar 13, 2013 at 4:08 PM, Peter Donald wrote:

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

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

> Hi,
>
> On Tue, Feb 12, 2013 at 6:17 AM, Antoine Toulme 
> 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]

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

> Hi,
>
> On Thu, Jan 24, 2013 at 8:53 AM, Alex Boisvert  >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
>

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

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

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: Add tasks to attach generation tasks to?

[Alex Boisvert]

On Fri, Nov 9, 2012 at 7:32 PM, Peter Donald  wrote:

> Hi,
>
> Another thing I noticed across a whole bunch of projects is that they
> usually create a per project task off which they can hang all the code
> generation tasks off. i.e. They add a task like "myproject:generate"
> that does all the source generation required for the project. Mostly
> this is so they can generate code and then do most of their
> development out of an IDE. However I notice that when I look at mavens
> lifecycle at [1] they actually include phases by the names
>
> * generate-sources: (Generate the main source code)
> * generate-resources: (Generate the main resources)
> * generate-test-sources: (Generate the test source code)
> * generate-test-resources: (Generate the test resources)
>
> I was thinking about trying to incorporate something similar into
> buildr. What do you think would be the best approach?
> * Add one "generate" task
> * Add the maven generate tasks
> * Add both tasks and have the generate task have all the maven
> generate taks as dependencies
>
> There would then be a process of updating all the addons to use this
> new approach.
>
> Thoughts?
>

I think it's a good idea to standardize on the task(s) names.  I would go
with defining separate task names and associating them with their most
relevant tasks e.g. "resources" depends on "generate-resources", "compile"
depends on "generate-sources", etc.   I'm not sure about the utility of the
overall "generate" task but I guess we could add it as a dependency of
"build".

Whatever we opt for, we should update our basic dependency graph at
https://cwiki.apache.org/confluence/display/BUILDR/12+Things+to+Know+About+Buildr
.

alex

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

[Alex Boisvert]

On Fri, Nov 9, 2012 at 7:20 PM, Peter Donald  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 wrote:

> Hi,
>
> I actually found it quite hard to reproduce. It seems to depend on the
> order in which the gems are installed and I seemed to be able to
> reproduce it by random touch commands in gem directory.
>
> However, a symptom is present on non windows boxes if you do something like
>
> $ cat > buildfile
> task "X" do
>   rm_rf ""
> end
> ^D
> $ buildr X
>
> and you see a line like "rm -rf XX" then there may be an issue.
>
> I also observed that some times there was also problems with "buildr
> install" on windows boxes. (You would receive a ArgumentError for
> calling the install method).
>
> On Fri, Nov 9, 2012 at 3:03 AM, Alex Boisvert 
> 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,  wrote:

> Author: donaldp
> Date: Wed Nov  7 08:17:22 2012
> New Revision: 1406490
>
> URL: http://svn.apache.org/viewvc?rev=1406490&view=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=1406490&r1=1406489&r2=1406490&view=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: [ANNOUNCE] Apache Buildr 1.4.8 released

[Alex Boisvert]

Well done Peter and thanks for the release!

On Tue, Nov 6, 2012 at 1:38 PM, Peter Donald  wrote:

> Apache Buildr is a build system for Java-based applications, including
> support
> for Scala, Groovy and a growing number of JVM languages and tools.  We
> wanted
> something that's simple and intuitive to use, so we only need to tell it
> what
> to do, and it takes care of the rest.  But also something we can easily
> extend
> for those one-off tasks, with a language that's a joy to use.
>
>
> New in this release:
>
>   * 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)
> - 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.
>
>
> To learn more about Buildr and get started:
> http://buildr.apache.org/
>
> Thanks!
> The Apache Buildr Team
>

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

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

Re: 1.4.8 Release?

[Alex Boisvert]

+1 for release.

The process is documented here:
https://cwiki.apache.org/confluence/display/BUILDR/Release+process

And thanks much for getting the CI builds back on track and testing passing
across all platforms!

Let me know if you need help during the release.

On Sat, Oct 20, 2012 at 11:10 PM, Peter Donald wrote:

> Hi,
>
> So I think we are ready to do a release. The CI is building on both Linux
> hosts and win32 with 100% success rate and I just ran the tests through OSX
> locally and there seems to be no problems there either. I vaguely recall
> there being a document for the process somewhere? Anyone have any reason
> for us not to kick off the process?
>
> --
> Cheers,
>
> Peter Donald
>

Status report for the Apache Buildr project

[Alex Boisvert]

-
Attachment C: 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.

After almost a year without release, we finally got our release act
together and
published Buildr 1.4.7 (incl. 70+ fixes/changes/enhancements) on May 29th.

Outside of a surge surrounding the release, the mailing lists have been
relatively quiet in past 3 months. We continue to receive contributions at a
rate of about one per month on average.

We have no issues that require board attention.

Apache Buildr 1.4.7 released

[Alex Boisvert]

Apache Buildr is a Ruby/JRuby-based 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.

Special thanks to contributors to this release: Christopher Coco, Peter
Donald,
Kafka Liu, Dani Perez, Russell Teabeault, Antoine Toulme, Tammo Van Lessen.

New in Buildr 1.4.7:
* Added: BUILDR-618 pom properties feature does not support hierarchy
(kafka liu)
* 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 JTestR as it is no longer
maintained (Antoine Toulme)
* Change: BUILDR-614 Buildr development - Using rvm, bundler and OSX
installs the wrong rjb (Russell Teabeault)
* Change: Upgrade to RJB 1.4.0
* Fixed: ArtifactNamespace fails when using artifacts with classfier.
* Fixed: Buildr.artifacts() should handle any object with :to_spec method
(i.e., any object that ActsAsArtifact)
*

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

> 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 _(:ta

Re: [VOTE] Buildr 1.4.7 release

[Alex Boisvert]

Actually the credit for getting to a release goes to Peter Donald.  He did
all the grunt work of getting our tests passing on all supported
configurations and putting our rvm-bundler house back in order.I just
pushed the rocket launch button.

Thanks Peter!

On Wed, May 30, 2012 at 10:47 AM, lacton wrote:

> +1
>
> Great job, Alex!
>
> lacton
>
> On Tue, May 29, 2012 at 10:11 PM, Victor Hugo Borja 
> wrote:
> > awesome +1
> >
> > --
> > Quaerendo invenietis.
> >
> > vic.
> >
> >
> >
> > On Monday, May 28, 2012 at 1:53 PM, Alex Boisvert wrote:
> >
> >> 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 (
> http://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 JD

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

> 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 wrote:
>
>> I can reproduce the failure ... will look into it.
>>
>>
>> On Mon, May 28, 2012 at 3:30 PM, Peter Donald wrote:
>>
>>> 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 >> (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,   wrote:
>>> > Author: boisvert
>>> > Date: Mon May 28 21:15:38 2012
>>> > New Revision: 1343392
>>> >
>>> > URL: http://svn.apache.org/viewvc?rev=1343392&view=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=1343392&r1=1343391&r2=1343392&view=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=1343392&r1=1343391&r2=1343392&view=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
>>>
>>
>>
>

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

> I can reproduce the failure ... will look into it.
>
>
> On Mon, May 28, 2012 at 3:30 PM, Peter Donald wrote:
>
>> 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 > (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,   wrote:
>> > Author: boisvert
>> > Date: Mon May 28 21:15:38 2012
>> > New Revision: 1343392
>> >
>> > URL: http://svn.apache.org/viewvc?rev=1343392&view=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=1343392&r1=1343391&r2=1343392&view=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=1343392&r1=1343391&r2=1343392&view=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
>>
>
>

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

[Alex Boisvert]

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

On Mon, May 28, 2012 at 3:30 PM, Peter Donald wrote:

> 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 '
>
> 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,   wrote:
> > Author: boisvert
> > Date: Mon May 28 21:15:38 2012
> > New Revision: 1343392
> >
> > URL: http://svn.apache.org/viewvc?rev=1343392&view=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=1343392&r1=1343391&r2=1343392&view=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=1343392&r1=1343391&r2=1343392&view=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 supp

Re: Buildr 1.4.7 release candidate #1

[Alex Boisvert]

I've tested on Linux (Ubuntu 12.04) both CRuby 1.8.7 and JRuby 1.6.7 and
Windows 7.   The only problem I've faced is compiling RJB on Windows due to
https://github.com/arton/rjb/issues/7 so I'm tempted to upgrade to RJB
1.4.0 for the release.   Any objections?

On Sun, May 27, 2012 at 6:08 PM, Peter Donald wrote:

> Hi,
>
> Tested this and didn't hit any problems with the combinations;
>
> * Windows/JRuby
> * OSX/*
> * Linux/*
>
> On Sat, May 26, 2012 at 2:28 AM, Alex Boisvert 
> wrote:
> > I noticed a few errors in the PDF and generated site ("Liquid: "
> > errors).  Will fix before release.
> >
> > On Fri, May 25, 2012 at 8:49 AM, Alex Boisvert  >wrote:
> >
> >> 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 &qu

Re: Buildr 1.4.7 release candidate #1

[Alex Boisvert]

I noticed a few errors in the PDF and generated site ("Liquid: "
errors).  Will fix before release.

On Fri, May 25, 2012 at 8:49 AM, Alex Boisvert wrote:

> 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 _(:targ

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 t

Re: Time between releases

[Alex Boisvert]

On Tue, May 15, 2012 at 10:08 AM, Russ Teabeault wrote:

> I read the release process wiki page and at the risk of being flamed this
> seems a bit heavyweight, especially when releasing patch releases.  I am
> not sure if I understand the need for voting and getting all the issues
> down to zero.  Would it be possible to have different release requirements
> depending on the type of release (patch versus major)?
>

The vote is an Apache requirement.  Any official release for any Apache
project requires a vote, even patch releases.  In practical terms, the vote
gives everybody a period of 24-48 hours for testing releases which is
probably a good idea regardless.

Getting all the issues down to zero is based on what's been agreed to be
fixed in a given release.  If we're doing a patch release to fix something
small, the list of issues could a single issue.

In that respect, I wouldn't read the process too literally.   It's meant as
a guideline -- things to think about -- when doing a release.


A committer fixes a couple of bugs and then:
>
>  rake release - "Run specs, build gem, push to rubygems.com, done."
>
> It should be that simple.
>

Agreed in the sense that the process should be as automated as possible and
involve the least amount of administrative overhead (while still abiding to
Apache rules -- which again is just agreeing on what goes into a release
and voting on the release packages when they're ready).


> I am a big fan of buildr and I really want to see it thrive.  I am willing
> to volunteer my time to help do whatever is needed to get buildr to that
> level of simplicity when releasing.
>

Great!  Please try the rake scripts for staging/releasing and send back any
suggestions/improvements you have.  I would be thrilled to get back to a
simpler/fully-automated release process.   (I've done most of the recent
releases and they have been too time-consuming).

alex

Re: Time between releases

[Alex Boisvert]

On Mon, May 14, 2012 at 5:52 PM, Peter Donald wrote:

> 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: Time between releases

[Alex Boisvert]

On Mon, May 14, 2012 at 4:38 PM, Peter Donald wrote:

> Hi,
>
> On Tue, May 15, 2012 at 6:53 AM, Russ Teabeault 
> 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

Status report for the Apache Buildr project

[Alex Boisvert]

-
Attachment D: 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.

Our latest release happened in June -- we were hoping for a release in
November
but follow-up efforts stalled due to time constraints and difficulty in
getting
tests working on all supported platforms. Our changelog currently shows
about
70+ fixes/changes/enhancements since our last release. Subversion log show
about
120 commits since June with commits from 4 different committers and patches
accepted from 5 external contributors.

Mailing lists activity has been relatively low in past 3 months, with a
small
surge in past few weeks.

We have no issues that require board attention.

Re: Test task dependency will always be invoked

[Alex Boisvert]

Is generate_files a FileTask?  If so, it shouldn't execute if none of its
dependencies have changed.

(Also, reminder that in Rake tasks are only executed if needed? returns
true)

alex


On Mon, Apr 30, 2012 at 11:48 PM, Dominic Graefen  wrote:

> Hey guys,
>
> I am currently implementing a custom test-framework for one of my
> buildr-plugins.
> I enhance the test-task with a task that automatically generates
> test-suites prior to running them.
>
> Something like this:
>
> def initialize(test_task, options)
>  super
>  @task.compile.enhance [generate_files]
>  @task.project.clean.enhance [clean_files]
> end
>
>
>
> But somehow these tasks are executed all the time,
> for example when I run "buildr clean" it will still run generate_files.
>
> How would one go on to make these tasks adhere the buildr style of
> execution,
> so for example when I call "buildr build test=no" that the dependencies
> I've added to the tesk task won't be invoked and so on.
>
> Cheers,
>
> --
> Dominic Graefen
>
>

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

[Alex Boisvert]

Yes, sounds good.   My "availability window" closed shortly after I
volunteered and I didn't get past getting a proper environment to get 100%
specs passing on my machine on both Ruby + JRuby.

alex


On Tue, Mar 13, 2012 at 5:53 PM, Antoine Toulme wrote:

> I'm willing to give an other shot at a release, but I certainly don't want
> to interrupt if you are on it Alex.
>
> Ideally, if I engage myself to do the next release, I'll push a RC in the
> next 3 days, and if that doesn't happen, the release task is up for grabs
> again.
>
> Does that sound good ?
>
> Antoine
>
> On Thu, Feb 9, 2012 at 10:09, Alex Boisvert 
> wrote:
>
> > On Thu, Feb 9, 2012 at 3:10 AM, Peter Donald 
> > wrote:
> >
> > > On Thu, Feb 9, 2012 at 3:07 AM, Alex Boisvert  >
> > > 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: 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  wrote:

> On Thu, Feb 9, 2012 at 3:07 AM, Alex Boisvert 
> 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

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: 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 Toulme> >wrote:
>>
>>  OK, will do.
>>>
>>>
>>> On Fri, Nov 25, 2011 at 12:51, Alex 
>>> Boisvert
>>> >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 
>>>>> Boisvert
>>>>>
>>>>>> wrote:
>>>>>> On Tue, Nov 22, 2011 at 6:05 PM, Peter Donald>>>>>
>>>>>>> wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> I attempted to get the packages at
>>>>>>> http:/people.apache.org/~**toulmean/buildr/1.4.7/dist/<http://people.apache.org/~toulmean/buildr/1.4.7/dist/>working
>>>>>>>  but ran
>>>>>>> into some issues. I then did a blank rvm install and attempted again
>>>>>>> with no success. Here is what happened...
>>>>>>>
>>>>>>> $ wget
>>>>>>>
>>>>>>>  http://people.apache.org/~**toulmean/buildr/1.4.7/dist/**
>>>>> buildr-1.4.7.gem<http://people.apache.org/~toulmean/buildr/1.4.7/dist/buildr-1.4.7.gem>
>>>>>
>>>>>> $ rvm use ruby-1.8.7-p352
>>>>>>> $ gem install buildr-1.4.7.gem
>>>>>>> ERROR:  While executing gem ... (ArgumentError)
>>>>>>>Illformed requirement ["#>>>>>> 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 ["#>>>>> 0x7fdfa1c9c448>
>>>>>> 2.0.23"]
>>>>>> $ gem update --system
>>>>>> Fetching: rubygems-update-1.8.11.gem (100%)
>>>>>> Installing RubyGems 1.8.11
>>>>>> RubyGems 1.8.11 installed
>>>>>> [...]
>>>>>> $ gem install buildr-1.4.7.gem
>>>>>> [...]
>>>>>> Successfully installed buildr-1.4.7
>>>>>> 19 gems installed
>>>>>>
>>>>>>
>>>>>>  $ wget
>>>>>>>
>>>>>>>  http://people.apache.org/~**toulmean/buildr/1.4.7/dist/**
>>>>> buildr-1.4.7-java.gem<http://people.apache.org/~toulmean/buildr/1.4.7/dist/buildr-1.4.7-java.gem>
>>>>>
>>>>>> $ rvm use jruby-1.6.3
>>>>>>> $ gem install buildr-1.4.7-java.gemERROR:  While executing gem ...
>>>>>>> (NoMethodError)undefined method `call' for nil:NilClass
>>>>>>>
>>>>>>> Any ideas?
>>>>>>>
>>>>>>>  Also a rubygems issue... although upgrading to 1.8.11 led to a
>>>>>>
>>>>> different
>>>>>
>>>>>> issue:
>>>>>> https://github.com/carlhuda/**bundler/issues/1235<https://github.com/carlhuda/bundler/issues/1235>
>>>>>>
>>>>>> Not sure how to resolve this yet.
>>>>>>
>>>>>> alex
>>>>>>
>>>>>>
>>>>
>

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

>
> 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 
>
> A Jarfile is used to specify the repos and dependencies, an example:
>
> repository '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-**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 Guymon
>> >
>> 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 Hsu
>>> wrote:
>>>
 If this becomes part of the core of buildr as Peter suggested, would
 there be performance impact when not using transitive dependencies

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

> I am in favor of giving this vote one more week to conclude - with
> Thanksgiving, I didn't have time to run all tests yet.
>
> Please let me know if you favor a different solution.
>
> Antoine
>
> On Wed, Nov 23, 2011 at 13:35, Alex Boisvert  >wrote:
>
> > On Tue, Nov 22, 2011 at 6:05 PM, Peter Donald  > >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 ["#
> > > 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 ["#
> > 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
> >
>