Re: [compress] release?

On 2016-12-09, Gary Gregory wrote: > What is the outlook on a release? I'd like to make use of > in LZMACompressorOutputStream. There are two unresolved issues assigned to 1.13. No idea who assigned them but it would be good if who ever did it could look into them: https://issues.apache.org/jira

[compress] release?

Hi devs, What is the outlook on a release? I'd like to make use of in LZMACompressorOutputStream. Gary -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition

Re: [VOTE][RC6] Release Commons RNG 1.0

On Thu, 8 Dec 2016 21:45:29 +0100, Oliver Heger wrote: Build works with Java 1.6 and 1.8, site builds fine with 1.8. Artifacts and site look good. On the site I still miss an aggregated Javadocs Link. I removed it on purpose, assuming that it was less confusing if each generated apidocs link

Re: [VOTE][RC6] Release Commons RNG 1.0

+1 > On Dec 8, 2016, at 3:45 PM, Oliver Heger wrote: > > Build works with Java 1.6 and 1.8, site builds fine with 1.8. Artifacts > and site look good. > > On the site I still miss an aggregated Javadocs Link. > > +1 > Oliver > >> Am 07.12.2016 um 00:22 schrieb Gilles: >> Hi. >> >> This is a

Re: [VOTE][RC6] Release Commons RNG 1.0

Build works with Java 1.6 and 1.8, site builds fine with 1.8. Artifacts and site look good. On the site I still miss an aggregated Javadocs Link. +1 Oliver Am 07.12.2016 um 00:22 schrieb Gilles: > Hi. > > This is a [VOTE] for releasing Apache Commons RNG 1.0 (from RC6). > > > Tag name: > RN

Re: [VOTE][RC6] Release Commons RNG 1.0

Am 08.12.2016 um 12:24 schrieb sebb: > Works OK for me, hashes and sigs > > How did you download the files? > > I have noticed that some browsers automatically unpack archives and > it's not unknown for some to silently truncate the download. > Check the file sizes. Your theory seems to be corr

Re: [ALL] Why is the component's web site part of the release vote?

> On Dec 8, 2016, at 9:18 AM, Gilles wrote: > > On Thu, 8 Dec 2016 06:56:06 -0700, Apache wrote: >> Typically the site is voted on during the release when it is built by >> Maven. This is because it will put the version on the site and if it >> isn’t the release it will have SNAPSHOT in the vers

Re: [ALL] Why is the component's web site part of the release vote?

On Thu, 8 Dec 2016 12:33:43 +0100, Jochen Wiedmann wrote: On Thu, Dec 8, 2016 at 9:33 AM, Gilles wrote: I've just noticed a small problem in the (staged) web site submitted for the release of Commons RNG v1.0: http://home.apache.org/~erans/commons-rng-1.0-RC6-site/rat-report.html Since t

Re: [ALL] Why is the component's web site part of the release vote?

On Thu, 8 Dec 2016 06:56:06 -0700, Apache wrote: Typically the site is voted on during the release when it is built by Maven. This is because it will put the version on the site and if it isn’t the release it will have SNAPSHOT in the version, which means you are documenting stuff publicly that i

Re: [vfs] dependency on Jackrabbit WebDAV and obsolete HTTP client

On Thu, Dec 8, 2016 at 10:17 AM, Julian Reschke wrote: > On 2016-12-08 15:49, sebb wrote: >> >> Please note that Commons HttpClient moved to the HttpComponents PMC >> some years ago: >> >> http://hc.apache.org/httpclient-3.x/ >> >> It is no longer being developed (see the above link for details).

Re: [vfs] dependency on Jackrabbit WebDAV and obsolete HTTP client

On 2016-12-08 15:49, sebb wrote: Please note that Commons HttpClient moved to the HttpComponents PMC some years ago: http://hc.apache.org/httpclient-3.x/ It is no longer being developed (see the above link for details). Yes, that's why Jackrabbit is moving away from it. But commons-vfs still

Re: [vfs] dependency on Jackrabbit WebDAV and obsolete HTTP client

Please note that Commons HttpClient moved to the HttpComponents PMC some years ago: http://hc.apache.org/httpclient-3.x/ It is no longer being developed (see the above link for details). On 8 December 2016 at 13:05, Julian Reschke wrote: > Hi there, > > please note that Jackrabbit is moving aw

Re: [ALL] Why is the component's web site part of the release vote?

Typically the site is voted on during the release when it is built by Maven. This is because it will put the version on the site and if it isn’t the release it will have SNAPSHOT in the version, which means you are documenting stuff publicly that isn’t really available yet. There are ways aroun

[vfs] dependency on Jackrabbit WebDAV and obsolete HTTP client

Hi there, please note that Jackrabbit is moving away from http client 3, and the next major version (2.14) is going to remove the APIs based on http client 3. See JCR-2406 for details (and progress information). Best regards, Julian ---

Re: [ALL] Why is the component's web site part of the release vote?

On Thu, Dec 8, 2016 at 9:33 AM, Gilles wrote: > I've just noticed a small problem in the (staged) web site > submitted for the release of Commons RNG v1.0: > http://home.apache.org/~erans/commons-rng-1.0-RC6-site/rat-report.html > > Since this must be fixed in the regenerated site will > not re

Re: [ALL] Why is the component's web site part of the release vote?

On 8 December 2016 at 09:33, Stefan Bodewig wrote: > On 2016-12-08, Gilles wrote: > >> Hi. > >> I've just noticed a small problem in the (staged) web site >> submitted for the release of Commons RNG v1.0: >> http://home.apache.org/~erans/commons-rng-1.0-RC6-site/rat-report.html > >> Since this m

Re: [VOTE][RC6] Release Commons RNG 1.0

Works OK for me, hashes and sigs How did you download the files? I have noticed that some browsers automatically unpack archives and it's not unknown for some to silently truncate the download. Check the file sizes. On 8 December 2016 at 07:58, Gilles wrote: > On Wed, 7 Dec 2016 21:39:02 +0100

Re: [ALL] Why is the component's web site part of the release vote?

On 2016-12-08, Gilles wrote: > Hi. > I've just noticed a small problem in the (staged) web site > submitted for the release of Commons RNG v1.0: > http://home.apache.org/~erans/commons-rng-1.0-RC6-site/rat-report.html > Since this must be fixed in the regenerated site will > not reflect the re

[ALL] Why is the component's web site part of the release vote?

Hi. I've just noticed a small problem in the (staged) web site submitted for the release of Commons RNG v1.0: http://home.apache.org/~erans/commons-rng-1.0-RC6-site/rat-report.html Since this must be fixed in the regenerated site will not reflect the released version number, why do we actual