I'm working on a fix now. Have a look when it is committed to see if
it can be improved.
On 6 September 2011 15:48, Paul Benedict wrote:
> Make the sun class be loaded dynamically -- not statically -- and if
> it is not present, just throw an UnsupportedOperationException? I
> think that would so
Make the sun class be loaded dynamically -- not statically -- and if
it is not present, just throw an UnsupportedOperationException? I
think that would solve Android's problem.
On Tue, Sep 6, 2011 at 8:36 AM, sebb wrote:
> On 6 September 2011 05:44, David Karlsen wrote:
>> I think tying to sun c
On 6 September 2011 05:44, David Karlsen wrote:
> I think tying to sun classes is a bad idea.
Yes, which is why the code checks to see if the class is present.
If the Java 6 method is available, then it uses that, otherwise it
checks for the Sun method.
If neither is available, then the code thr
On Sep 5, 2011, at 23:34, Henri Yandell wrote:
> On Sat, Sep 3, 2011 at 8:10 AM, sebb wrote:
>> On 3 September 2011 05:37, Henri Yandell wrote:
>>> I'm less concerned with the 115 errors, unless they're all as grievous
>>> as the StringUtils one - ie) the method causing trouble is not the
>>> o
I think tying to sun classes is a bad idea.
Den 6. sep. 2011 05:54 skrev "sebb" følgende:
> On 6 September 2011 04:33, Henri Yandell wrote:
>> On Sat, Sep 3, 2011 at 8:10 AM, sebb wrote:
>>> On 3 September 2011 05:37, Henri Yandell wrote:
I'm less concerned with the 115 errors, unless they
On 6 September 2011 04:33, Henri Yandell wrote:
> On Sat, Sep 3, 2011 at 8:10 AM, sebb wrote:
>> On 3 September 2011 05:37, Henri Yandell wrote:
>>> I'm less concerned with the 115 errors, unless they're all as grievous
>>> as the StringUtils one - ie) the method causing trouble is not the
>>> o
On Sat, Sep 3, 2011 at 8:10 AM, sebb wrote:
> On 3 September 2011 05:37, Henri Yandell wrote:
>> I'm less concerned with the 115 errors, unless they're all as grievous
>> as the StringUtils one - ie) the method causing trouble is not the
>> only one broken.
>>
>> If the error happened when callin
can also be done via the maven-invoker-plugin.
>
> LieGrue,
> strub
>
>
> - Original Message -
>> From: sebb
>> To: Commons Developers List
>> Cc:
>> Sent: Saturday, September 3, 2011 5:10 PM
>> Subject: Re: [lang] Running lang under a secu
s List
> Cc:
> Sent: Saturday, September 3, 2011 5:10 PM
> Subject: Re: [lang] Running lang under a security manager and LANG-744
>
> On 3 September 2011 05:37, Henri Yandell wrote:
>> I'm less concerned with the 115 errors, unless they're all as
> grievous
>
On 3 September 2011 05:37, Henri Yandell wrote:
> I'm less concerned with the 115 errors, unless they're all as grievous
> as the StringUtils one - ie) the method causing trouble is not the
> only one broken.
>
> If the error happened when calling stripAccents, that would be
> workable; but having
To see the security manager in action you just need to comment out one
line of code in the POM.
Ideally I would like to be able to run the tests twice, once with a d
without the sec man. Good luck to me trying to figure out how to do
this in maven :( ant would be easy ;)
Ideas?
Gary
On Sep 3, 2
nt: Saturday, September 3, 2011 7:19 AM
> Subject: Re: [lang] Running lang under a security manager and LANG-744
>
> On 9/2/11 4:06 AM, Gary Gregory wrote:
>> On Sep 2, 2011, at 1:21, Stephen Colebourne
> wrote:
>>
>>> On 2 September 2011 01:20, Gary Gregory
> w
On 9/2/11 4:06 AM, Gary Gregory wrote:
> On Sep 2, 2011, at 1:21, Stephen Colebourne wrote:
>
>> On 2 September 2011 01:20, Gary Gregory wrote:
>>> Specifically for StringUtils, should we have a SunStringUtils? This would
>>> let you know that you are depending on com.sun code.
>> I really don't
Bad first paragraph.
ie) the method causing trouble is not the one the user wants to use.
For example - they want to use StringUtils.chomp, and the
implementation of stripAccents is blocking them.
Sorry for the double post,
Hen
On Fri, Sep 2, 2011 at 9:37 PM, Henri Yandell wrote:
> I'm less co
I'm less concerned with the 115 errors, unless they're all as grievous
as the StringUtils one - ie) the method causing trouble is not the
only one broken.
If the error happened when calling stripAccents, that would be
workable; but having all of StringUtils unavailable is very painful.
One option
On 2 September 2011 12:06, Gary Gregory wrote:
> On Sep 2, 2011, at 1:21, Stephen Colebourne wrote:
>
>> On 2 September 2011 01:20, Gary Gregory wrote:
>>> Specifically for StringUtils, should we have a SunStringUtils? This would
>>> let you know that you are depending on com.sun code.
>>
>> I r
On Sep 2, 2011, at 1:21, Stephen Colebourne wrote:
> On 2 September 2011 01:20, Gary Gregory wrote:
>> Specifically for StringUtils, should we have a SunStringUtils? This would
>> let you know that you are depending on com.sun code.
>
> I really don't like that idea!
>
> Generally, it is non-Sun
On 2 September 2011 01:20, Gary Gregory wrote:
> Specifically for StringUtils, should we have a SunStringUtils? This would
> let you know that you are depending on com.sun code.
I really don't like that idea!
Generally, it is non-Sun JVMs including Android that are the problem.
Lets just do the
WRT LANG-744 "StringUtils throws java.security.AccessControlException on
Google App Engine"
Well, I've ruminated, pondered and experimented.
Running all unit tests with a security managers results in:
Tests run: 2046, Failures: 2, Errors: 115, Skipped: 0
Clearly, we need a good overall solution
19 matches
Mail list logo
