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

[Antoine Toulme]

+1 from me as well. Good job!

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

Re: [VOTE] Buildr 1.5.8 release

[Peter Donald]

+1 from me

On Sun, Jul 14, 2019 at 9:18 PM Peter Donald  wrote:

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

-- 
Cheers,

Peter Donald

[VOTE] Buildr 1.5.8 release

[Peter Donald]

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

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

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

The following changes were made since 1.5.7:

  * Fixed:  Changed references to `https://repo1.maven.org/maven2` to use
https where possible.
  * Change: Use the `zapwhite` gem to manage file whitespace within
repository.
  * Fixed:  Replace references to long removed `
http://www.ibiblio.org/maven2/` repository with
`https://repo1.maven.org/maven2`.
  * Fixed:  Ensure pom files used in tests use https when referring to
maven repositories.
  * Added:  Add support for downloading external annotations and attaching
them to IntelliJ IDEA module dependencies.
  * Added:  Detect external annotations in the local project and add them
to the generated IntelliJ IDEA
module when generating. The default location is
`src/main/annotations` but other locations
can be specified by modifying the
`project.iml.annotation_paths` property.
  * Fixed:  Explicitly specify the `:sourcepath` parameter for javadoc
tool. This enables additional parameters
such as `-packagenames` and `-subpackages` to be passed to the
underling tool.
  * Fixed:  Stop generating poms with the parent POM
`org.sonatype.oss:oss-parent:8`. The las update was a long time
ago (i.e. 2012) and it is no longer maintained. It was also
deprecated several years ago and is not
guaranteed to work in modern Maven deployments.