That's certainly the solution of least impact and works for me. Sucks that
we would have to keep a whole dependency for one deprecated method in one
deprecated class, but life is hard sometimes.
On 10/22/07, Niall Pemberton <[EMAIL PROTECTED]> wrote:
>
> On 10/23/07, Ben Speakmon <[EMAIL PROTECTED
On 10/23/07, Ben Speakmon <[EMAIL PROTECTED]> wrote:
> After refactoring EmailValidator to use InetAddressValidator, I went to get
> rid of (or at least deprecate) isValidIpAddress. However, it takes a
> parameter of type Perl5Util from oro. Since it's a protected method, we
> can't eliminate it in
After refactoring EmailValidator to use InetAddressValidator, I went to get
rid of (or at least deprecate) isValidIpAddress. However, it takes a
parameter of type Perl5Util from oro. Since it's a protected method, we
can't eliminate it in a point release, but we also want to get rid of oro
for 1.4,
On 21.10.2007, at 12:37, Oliver Heger wrote:
(this may be a stupid question, but I did not follow the setup of
Continuum too closely)
Not stupid at all. I would imagine the artifacts go into the local
maven repo of vmbuild.apache.org Would be nice to expose that
properly ...or run the dep
Hi Dennis,
Dennis Lundberg wrote:
> What is your conclusion? Should we leave things the way they are and
> maybe add JRockit as a "known issue" on the wiki?
I suppose so. I debugged the code with different JDKs/JREs and so I can
report the the security test cases work on all my JDKs (including 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 [EMAIL PROTECTED]
Project commons-jelly-tags-jaxme 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 [EMAIL PROTECTED]
Project commons-jelly-tags-jsl-test has an issue affecting its community
integration.
Th
On 22/10/2007, Simon Kitching <[EMAIL PROTECTED]> wrote:
[on the commons-user list]
> Hi Morten,
>
[...]
> Keeping the site relevant for people who are using the current release, while
> still publishing site updates is unfortunately an unsolved problem at commons
> :-(.
There was an e-mail thr
Hi Dennis,
Dennis Lundberg wrote on Sunday, October 21, 2007 12:40 AM:
> What is your conclusion? Should we leave things the way they are and
> maybe add JRockit as a "known issue" on the wiki?
well, just from my short look, I did not grok all the code in the
MockingSecurityManager in detail at
