On Fri, Jun 3, 2016 at 2:09 PM, Gary Gregory wrote:
> On Fri, Jun 3, 2016 at 11:08 AM, Bernd Eckenfels
> wrote:
>
>> Hello,
>>
>> There was no objection to switching VFS project to Git as the primary
>> source control. Here are the people
Am 03.06.2016 um 22:16 schrieb Gary Gregory:
> On Jun 3, 2016 12:53 PM, "Oliver Heger"
> wrote:
>>
>> Build works fine with Java 1.6 on Windows 10. Artifacts and site look
> good.
>>
>> The site cannot be built with Java 8, and the release notes are missing
>>
On Jun 3, 2016 12:53 PM, "Oliver Heger"
wrote:
>
> Build works fine with Java 1.6 on Windows 10. Artifacts and site look
good.
>
> The site cannot be built with Java 8, and the release notes are missing
> BEANUTILS-477, but this is not blocking.
>
> I ran the tests
Build works fine with Java 1.6 on Windows 10. Artifacts and site look good.
The site cannot be built with Java 8, and the release notes are missing
BEANUTILS-477, but this is not blocking.
I ran the tests for [configuration] with the new jar and got a single
test failure which seems to be caused
On Fri, Jun 3, 2016 at 11:08 AM, Bernd Eckenfels
wrote:
> Hello,
>
> There was no objection to switching VFS project to Git as the primary
> source control. Here are the people participated (I also vote +1):
>
> Bernd Eckenfels
> Gary Gregory
> Dave Brosius
> Woonsan Ko
>
Hello,
There was no objection to switching VFS project to Git as the primary
source control. Here are the people participated (I also vote +1):
Bernd Eckenfels
Gary Gregory
Dave Brosius
Woonsan Ko
Josh Elser
Ralph Goers
Jochen Wiedmann
Christopher
How to proceed? Open an Infra ticket?
Gruss
Yeah, that rings a bell.
Gary
On Fri, Jun 3, 2016 at 6:43 AM, Matt Sicker wrote:
> Isn't it the clirr plugin that's failing with bcel?
>
> On 2 June 2016 at 17:07, Benedikt Ritter wrote:
>
> > Gary Gregory schrieb am Fr., 3. Juni
On Thu, Jun 2, 2016 at 11:36 PM, Benson Margulies wrote:
> I don't understand what's wrong with semantic versioning and keeping
> the same maven coordinates. No sane person should be using RELEASE or
> LATEST.
The real problem is, IMO, not the versioning scheme, but the
On Thu, 02 Jun 2016 21:35:45 +, Benedikt Ritter wrote:
Emmanuel Bourg schrieb am Do., 2. Juni 2016 um
23:26 Uhr:
Le 2/06/2016 à 22:42, Benedikt Ritter a écrit :
> - since our components are depended upon by a lot of projects, we
need to
> take special care regarding
Isn't it the clirr plugin that's failing with bcel?
On 2 June 2016 at 17:07, Benedikt Ritter wrote:
> Gary Gregory schrieb am Fr., 3. Juni 2016 um
> 00:06 Uhr:
>
> > On Thu, Jun 2, 2016 at 2:15 PM, Jörg Schaible
> > wrote:
> >
Le 3/06/2016 à 11:13, sebb a écrit :
> I found the Clirr report I did on BCEL:
>
> http://home.apache.org/~sebb/BCEL/clirr-report.html
>
> This compares BCEL trunk with 5.2.
> [The 5.2 code was shaded to align the package names.]
>
> As can be seen, the main changes are additions to the Visitor
I found the Clirr report I did on BCEL:
http://home.apache.org/~sebb/BCEL/clirr-report.html
This compares BCEL trunk with 5.2.
[The 5.2 code was shaded to align the package names.]
As can be seen, the main changes are additions to the Visitor interface.
There are several approaches to fix
ping?
Gary
On Sun, May 29, 2016 at 3:46 PM, James Carman
wrote:
> +1
>
> On Wed, May 25, 2016 at 4:43 PM Bernd Eckenfels
> wrote:
>
> > Hello,
> >
> > I would like to be able to use Git with the Apache Commons VFS repo. As
> > we agreed upon
On 2 June 2016 at 23:15, Gary Gregory wrote:
> On Thu, Jun 2, 2016 at 2:57 PM, Benedikt Ritter wrote:
>
>> Emmanuel Bourg schrieb am Do., 2. Juni 2016 um
>> 23:39 Uhr:
>>
>> > Hi all,
>> >
>> > A part of the release process is to
On 2 June 2016 at 21:42, Benedikt Ritter wrote:
> Hi,
>
> we do seem to have different opinions when it comes to binary compatibility
> and how it should be handled. Usually we would say "this should be decided
> on a component basis". However this discussion is coming up
Hi Benson,
Benson Margulies wrote:
> Just to cite a fact:
>
> If you write:
>
>
>
>
> ...
> x
> ...
>
> You will get x. Even if transitive dependencies ask for x+10. I only
> learned this recently.
Yes, but you dropped the significant part here:
> > A part of the release process is to update the web site. I wonder if
> > this could be simplified with a Jenkins job watching for the release
> > tags and building/uploading the new site automatically. That would
> > make one less thing to think about when releasing new versions. I
> > suspect
Thanks Stian, Dapeng and folks!
For Commons Crypto, do we still have to wait for other process to finish or we
now can go forward with the first release process?
Regards,
Haifeng
-Original Message-
From: Stian Soiland-Reyes [mailto:st...@apache.org]
Sent: Thursday, June 2, 2016 10:36
18 matches
Mail list logo