To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-vfs2-test has an issue affecting its community integration.
This i
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-id has an issue affecting its community integration.
This issue af
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-proxy-test has an issue affecting its community integration.
This
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-digester3 has an issue affecting its community integration.
This i
sebb wrote:
> Trying again - I hope I've fixed all the problems found previously.
>
> This is a vote to release Apache Commons NET 3.1 based on RC2.
>
> [ ] +1 release it
> [ ] +0 go ahead I don't care
> [ ] -1 no, do not release it because...
>
> tag:
> https://svn.apache.org/repos/asf/commons
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=18998&projectId=83
Build statistics:
State: Failed
Previous State: Ok
Started at: Fri 17 Feb 2012 23:23:32 +
Finished at: Fri 17 Feb 2012 23:25:29 +
Total time: 1m 56s
Build Trigger: Schedule
Buil
On Feb 17, 2012, at 2:16 PM, Gary Gregory wrote:
> On Fri, Feb 17, 2012 at 5:03 PM, Ralph Goers
> wrote:
>
>>
>> What new features and did they really break the API? I'd really hate to go
>> to 3.0 after just getting 2.0 out.
>>
>
> "They" would really be me :)
By "they" I didn't mean who b
On Feb 17, 2012, at 2:18 PM, Gary Gregory wrote:
> On Fri, Feb 17, 2012 at 5:05 PM, Ralph Goers
> wrote:
>
>>
>> On Feb 17, 2012, at 1:17 PM, Gary Gregory wrote:
>>
>>> On Fri, Feb 17, 2012 at 4:12 PM, Ralph Goers >> wrote:
>>>
Really? I've gotten so used to putting the '{' at the end
On Fri, Feb 17, 2012 at 5:05 PM, Ralph Goers wrote:
>
> On Feb 17, 2012, at 1:17 PM, Gary Gregory wrote:
>
> > On Fri, Feb 17, 2012 at 4:12 PM, Ralph Goers >wrote:
> >
> >> Really? I've gotten so used to putting the '{' at the end of the line
> >> that I assumed VFS was that way.
> >>
> >
> > I'
On Fri, Feb 17, 2012 at 5:03 PM, Ralph Goers wrote:
>
> On Feb 17, 2012, at 1:09 PM, Gary Gregory wrote:
>
> > This is off topic on for this thread but I'll take all the help I can get
> > to move VFS to a new release :)
> >
> > I am happy with the fact that the build is now self sufficient WRT
>
On Feb 17, 2012, at 1:17 PM, Gary Gregory wrote:
> On Fri, Feb 17, 2012 at 4:12 PM, Ralph Goers
> wrote:
>
>> Really? I've gotten so used to putting the '{' at the end of the line
>> that I assumed VFS was that way.
>>
>
> I'm happy to change the style to what we both seem to consider normal
On Feb 17, 2012, at 1:09 PM, Gary Gregory wrote:
> This is off topic on for this thread but I'll take all the help I can get
> to move VFS to a new release :)
>
> I am happy with the fact that the build is now self sufficient WRT testing,
> embedded servers are used to test HTTP and so on.
>
>
Hello.
> just some status/feedback on some still open issues:
>
> - MATH-449: I have implemented (almost) all suggestions from
>Phil, and the code is documented and tested, so imho the issue
>can be resolved unless somebody has still reservations
You probably know best.
> - MATH-431:
On Fri, Feb 17, 2012 at 4:12 PM, Ralph Goers wrote:
> Really? I've gotten so used to putting the '{' at the end of the line
> that I assumed VFS was that way.
>
I'm happy to change the style to what we both seem to consider normal but I
am not sure what the rest of the community feels like...
G
So... are we ready to move some bits?
;)
Gary
On Sun, Feb 12, 2012 at 8:03 PM, Konstantin Kolinko
wrote:
> 2012/2/13 Mark Thomas :
> >
> > General
> > - Logging in pool, if any, should be minimal
> >
>
> Two general questions:
> When there are several pools,
> - is it possible to discern log mess
Really? I've gotten so used to putting the '{' at the end of the line that I
assumed VFS was that way.
Ralph
On Feb 17, 2012, at 1:05 PM, Gary Gregory wrote:
> On Fri, Feb 17, 2012 at 11:33 AM, Ralph Goers
> wrote:
>
>> I'm confused as to why you are having to fix so many checkstyle issues
This is off topic on for this thread but I'll take all the help I can get
to move VFS to a new release :)
I am happy with the fact that the build is now self sufficient WRT testing,
embedded servers are used to test HTTP and so on.
There are a lot of Clirr "errors" due to new features which makes
On Fri, Feb 17, 2012 at 11:33 AM, Ralph Goers wrote:
> I'm confused as to why you are having to fix so many checkstyle issues. I
> had thought I had them down to just a couple of classes. In fact, putting
> the curly brace on the next line should cause a checkstyle error. Are you
> using the chec
2012/2/17 Thomas Neidhart :
> Hi @all,
>
> just some status/feedback on some still open issues:
>
> - MATH-449: I have implemented (almost) all suggestions from
> Phil, and the code is documented and tested, so imho the issue
> can be resolved unless somebody has still reservations
>
> - MATH
Hi @all,
just some status/feedback on some still open issues:
- MATH-449: I have implemented (almost) all suggestions from
Phil, and the code is documented and tested, so imho the issue
can be resolved unless somebody has still reservations
- MATH-431: the two tests were contributed by M
Hi,
FYI: I submitted a patch to already closed ticket
https://issues.apache.org/jira/browse/LANG-462
The previously merged patch caused the build to broke. Is uses Java 6
features, which are not Java 5 compatible. Also one test was broken.
Regards,
Felix
I'm confused as to why you are having to fix so many checkstyle issues. I had
thought I had them down to just a couple of classes. In fact, putting the
curly brace on the next line should cause a checkstyle error. Are you using the
checktyle configuration that is in the project which is used to
On Feb 17, 2012, at 2:29, Ralph Goers wrote:
> Did you notice these messages?
Yes and it just worked for some reason. Now gump is failing for the
previous reason: the wrong version of slf4j is used.
Gary
> Project ID: org.apache.maven.plugins:maven-checkstyle-plugin
>
> Reason: POM 'org.apache
23 matches
Mail list logo
