gt; Could you please confirm is Apache Commons Lang (Commons Lang3) version
> 3.1 is compatible with Open Java 11 & 17, if not which version is
> compatible with Open Java 11 & 17?
>
> Regards,
> Pranav Kumar
>
Hi Team,
Could you please confirm is Apache Commons Lang (Commons Lang3) version 3.1 is
compatible with Open Java 11 & 17, if not which version is compatible with Open
Java 11 & 17?
Regards,
Pranav Kumar
yes it is really a bug.
I created a fix pr (with test codes) at
https://github.com/apache/commons-lang/pull/529
check in it when you guys have time.
Xeno Amess 于2020年4月29日周三 上午5:04写道：
> well when I look at StringUtil I found something like this.
>
> final char c1 = cs.charAt(index1++);
> final
well when I look at StringUtil I found something like this.
final char c1 = cs.charAt(index1++);
final char c2 = substring.charAt(index2++);
if (c1 == c2) {
continue;
}
if (!ignoreCase) {
return false;
}
// The same check as in String.regionMatches():
if (Character.toUpperCase(c1) !=
Hi,
I have question about StopWatch.
I want to do interleaved timing with a single StopWatch instance.
Something like this:
{
code-to-time-group-1
}
{
code-to-time-group-2
}
{
code-to-time-group-1
}
this could be done with 2 instances of StopWatch at higher performance
impact.
Hi,
I was just wondering whether StringUtils should be handling Unicode
supplementary characters correctly?
For example org.apache.commons.lang3.StringUtils#isAlphanumeric will return
false for code point 65536 which is actually a letter. This is because it
uses java.lang.CharSequence#charAt
t the error message:
ClassNotFoundException: com..
, this says com.. is not available in the class path of JVM
(which
your Spark is running on). I would verify that you can instantiate
com.. in Spark/Scala *without* SerializationUtils.
Regards,
Tomo
On Wed, Jun 26, 2
com.. is not available in the class path of JVM
>
>
> (which
>
>
> your Spark is running on). I would verify that you can instantiate
> com.. in Spark/Scala *without* SerializationUtils.
>
> Regards,
> Tomo
>
>
>
> On Wed, Jun 26, 2019 at
your Spark is running on). I would verify that you can instantiate
com.. in Spark/Scala *without* SerializationUtils.
Regards,
Tomo
On Wed, Jun 26, 2019 at 4:12 AM big data
<mailto:bigdatab...@outlook.com><mailto:bigdatab...@outlook.com>
wrote:
I use Apache Commo
;
> 在 2019/6/26 下午10:23, Tomo Suzuki 写道:
>
>
> Hi Big data,
>
> I don't use SerializationUtils, but if I interpret the error message:
>
>ClassNotFoundException: com..
>
> , this says com.. is not available in the class path of JVM
>
>
>
ch
your Spark is running on). I would verify that you can instantiate
com.. in Spark/Scala *without* SerializationUtils.
Regards,
Tomo
On Wed, Jun 26, 2019 at 4:12 AM big data
<mailto:bigdatab...@outlook.com>
wrote:
I use Apache Commons Lang3's SerializationUtils in the code.
Ser
com.. in Spark/Scala *without* SerializationUtils.
> >
> > Regards,
> > Tomo
> >
> >
> >
> > On Wed, Jun 26, 2019 at 4:12 AM big data
> wrote:
> >
> >> I use Apache Commons Lang3's SerializationUtils in the code.
>
alizationUtils.
>
> Regards,
> Tomo
>
>
>
> On Wed, Jun 26, 2019 at 4:12 AM big data wrote:
>
>> I use Apache Commons Lang3's SerializationUtils in the code.
>>
>> SerializationUtils.serialize()
>>
>> to store a customized class as files into
*without* SerializationUtils.
Regards,
Tomo
On Wed, Jun 26, 2019 at 4:12 AM big data wrote:
> I use Apache Commons Lang3's SerializationUtils in the code.
>
> SerializationUtils.serialize()
>
> to store a customized class as files into disk and
>
> SerializationU
I use Apache Commons Lang3's SerializationUtils in the code.
SerializationUtils.serialize()
to store a customized class as files into disk and
SerializationUtils.deserialize(byte[])
to restore them again.
In the local environment (Mac OS), all serialized files can be deserialized
normally
> On Apr 15, 2019, at 6:55 PM, Rob Tompkins wrote:
>
>
>
>> On Apr 15, 2019, at 3:08 PM, Gary Gregory wrote:
>>
>> On Mon, Apr 15, 2019 at 6:06 PM Bruno P. Kinoshita
>> wrote:
>>
>>> I think that should be fine. I think something similar already happened
>>> in the past, but can't recall
t;>
>> Since we approved the sources tagged and we are not changing those, I'd say
>> we are OK to push out the javadoc files.
>
> This should be fixed now. It may take a little while for maven central to
> pick up the changes. @Scott - many thanks for the catch there!
&g
ot changing those, I'd say
> we are OK to push out the javadoc files.
This should be fixed now. It may take a little while for maven central to pick
up the changes. @Scott - many thanks for the catch there!
Cheers,
-Rob
>
> Gary
>
>
>>
>> -Rob
>>
>>>
; Since we approved the sources tagged and we are not changing those, I'd say
> we are OK to push out the javadoc files.
This should be fixed now. It may take a little while for maven central to pick
up the changes. @Scott - many thanks for the catch there!
Cheers,
-Rob
>
&g
changing those, I'd say
> we are OK to push out the javadoc files.
Cool. I’ll sort that out in the next hour.
>
> Gary
>
>
>>
>> -Rob
>>
>>> CheersBruno
>>>
>>> On Tuesday, 16 April 20
[LAZY][VOTE] on the staged
> artifacts in nexus. Thoughts?
>
Since we approved the sources tagged and we are not changing those, I'd say
we are OK to push out the javadoc files.
Gary
>
> -Rob
>
> > CheersBruno
> >
> >On Tuesday, 16 April 2019, 9
pload just the jar to an existing release?
Yes. My plan was to do just that. With a [LAZY][VOTE] on the staged artifacts
in nexus. Thoughts?
-Rob
> CheersBruno
>
> On Tuesday, 16 April 2019, 9:44:07 am NZST, Scott Palmer
> wrote:
>
> I noticed there are
April 2019, 9:44:07 am NZST, Scott Palmer
> wrote:
>
> I noticed there are no javadocs on Maven Central for commons-lang3 3.9.
> Is that intentional or a mistake?
>
> Scott
> (please copy me on responses as I am not subscribed to the list)
>
> -
the jar to an existing release?
CheersBruno
On Tuesday, 16 April 2019, 9:44:07 am NZST, Scott Palmer
wrote:
I noticed there are no javadocs on Maven Central for commons-lang3 3.9.
Is that intentional or a mistake?
Scott
(please copy me on responses as I am not subscribed to the list
Hm. Curious. Let me look at that.
-Rob
> On Apr 15, 2019, at 12:58 PM, Scott Palmer wrote:
>
> I noticed there are no javadocs on Maven Central for commons-lang3 3.9.
> Is that intentional or a mistake?
>
> Scott
> (please copy me on responses as I am not s
I noticed there are no javadocs on Maven Central for commons-lang3 3.9.
Is that intentional or a mistake?
Scott
(please copy me on responses as I am not subscribed to the list)
-
To unsubscribe, e-mail: user-unsubscr
lowing stack trace:
>
> ava.lang.ArrayIndexOutOfBoundsException: 4
>[junit4] 2> at
> org.apache.commons.lang3.time.FastDatePrinter$TextField.appendTo(FastDatePrinter.java:901)
> ~[commons-lang3-3.7.jar:3.7]
>[junit4] 2> at
> org.apache.commons.lang3.time.FastDatePrinter.applyRules(FastDatePr
the following stack trace:
ava.lang.ArrayIndexOutOfBoundsException: 4
[junit4] 2> at
org.apache.commons.lang3.time.FastDatePrinter$TextField.appendTo(FastDatePrinter.java:901)
~[commons-lang3-3.7.jar:3.7]
[junit4] 2> at
org.apache.commons.lang3.time.FastDatePrinter.appl
Hi,
thanks for quick response ...
Am 06.09.2018 um 21:24 schrieb Oliver Heger:
> So opening a ticket in Jira would be the correct action to take.
https://issues.apache.org/jira/browse/LANG-1419
Done :-) Hopefully I didn't miss any important stuff in Jira.
Cheers,
Phil
I've just stumbled upon a problem that prevents me from updating from
> 3.7 to 3.8 in an OSGi context.
>
> Although the release has just been a patch one, the bundle's symbolic
> name changed
> from "Bundle-SymbolicName org.apache.commons.lang3" in 3.7.0
> to "Bundle-Sym
le-SymbolicName org.apache.commons.commons-lang3" in 3.8.0.
That makes it impossible to do a drop-in update, as it is a breaking change.
Is that change an error in 3.8.0 or a wanted one that could be
communicated more directly to downstream users?
May I file a bugticket in the LANG-Jira for it? I assume there ha
t;
> > Regards,
> > Amey
> >
> > On Sun, Sep 3, 2017 at 6:26 PM, Philippe Mouawad <pmoua...@apache.org>
> > wrote:
> >
> > > Hello,
> > > Since version 3.6 of commons-lang3, RandomStringUtils has been
> deprecated
> > > following
plan, I
> think it will be good for your expectations.
>
> http://markmail.org/message/azxw4nai7fs2laas
>
> Regards,
> Amey
>
> On Sun, Sep 3, 2017 at 6:26 PM, Philippe Mouawad <pmoua...@apache.org>
> wrote:
>
> > Hello,
> > Since version 3.6 of commons-lang3, R
message/azxw4nai7fs2laas
>
> Regards,
> Amey
>
> On Sun, Sep 3, 2017 at 6:26 PM, Philippe Mouawad <pmoua...@apache.org
> <javascript:;>>
> wrote:
>
> > Hello,
> > Since version 3.6 of commons-lang3, RandomStringUtils has been deprecated
> > following
,
> Since version 3.6 of commons-lang3, RandomStringUtils has been deprecated
> following introduction of commons-text.
>
> Looking at current 1.1 version (and even snapshot 1.2) I wonder if it's not
> too early for deprecation.
>
> RandomStringUtils was very simple and intuit
Hello,
Since version 3.6 of commons-lang3, RandomStringUtils has been deprecated
following introduction of commons-text.
Looking at current 1.1 version (and even snapshot 1.2) I wonder if it's not
too early for deprecation.
RandomStringUtils was very simple and intuitive to use. I don't remember
= Validate.notNull(bar) from commons-lang3? ;)
Matt
IMO it's time to reimplement the JDK and throw away backward compatibility
than introduce patch after patch. At least a second clean API of the JDK
should be provided.
I wonder what others are thinking about this.
Karsten
-Ursprüngliche Nachricht
Hello,
I can see NullArgumentException has been removed from the lang3 API, but I
don't understand why. There have been long discussions in the past why a
NullArgumentException is better than using an IllegalArgumentException. Most
people are using commons-lang anyway, so what's the point
The official standard in the JDK is to throw NPE for null arguments. Since
JDK 7, they have made API available for this in
java.util.Objects#requireNonNull(). Commons is following the official
direction.
On Dec 21, 2011 10:16 AM, kwut...@web.de wrote:
Hi,
I am using the 3.0-SNAPSHOT of commons-lang3 and it seems like something
changed in the repository yesterday.
See the dates at
https://repository.apache.org/content/repositories/snapshots/org/apache/commons/commons-lang3/3.0-SNAPSHOT/
However the version has not changed, it is the same
On 2010-11-04 11:18, JammyZ wrote:
Hi,
I am using the 3.0-SNAPSHOT of commons-lang3 and it seems like something
changed in the repository yesterday.
See the dates at
https://repository.apache.org/content/repositories/snapshots/org/apache/commons/commons-lang3/3.0-SNAPSHOT/
However
41 matches
Mail list logo
