[jira] [Commented] (SCXML-231) Create Git / GitHub Mirror

2015-05-06 Thread Adam Bien (JIRA) 

[ 
https://issues.apache.org/jira/browse/SCXML-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14530054#comment-14530054
 ] 

Adam Bien commented on SCXML-231:
-

Git would be even better…

cheers,

adam



 Create Git / GitHub Mirror
 --

 Key: SCXML-231
 URL: https://issues.apache.org/jira/browse/SCXML-231
 Project: Commons SCXML
  Issue Type: Improvement
Reporter: Adam Bien

 The sources are currently maintained in SVN, what makes the contributions 
 harder. 
 Please introduce a github mirror (would be the best) or expose the sources to 
 git repo.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SCXML-228) Push current snapshot to maven central

2015-05-06 Thread Adam Bien (JIRA) 

[ 
https://issues.apache.org/jira/browse/SCXML-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14530047#comment-14530047
 ] 

Adam Bien commented on SCXML-228:
-

Hi Bedikt,

works perfectly, thanks!,

cheers,

adam

 workshops.adam-bien.com
 blog.adam-bien.com
 airhacksnews.com

 Author of: 
 Real World Java EE Night Hacks”,  
 Real World Java EE Patterns— Rethinking Best Practices
   
 


















 Push current snapshot to maven central
 --

 Key: SCXML-228
 URL: https://issues.apache.org/jira/browse/SCXML-228
 Project: Commons SCXML
  Issue Type: Improvement
Reporter: Adam Bien

 I'm using SCXML v2 in https://github.com/AdamBien/stateful and it works well. 
 However, there are no snapshot builds in maven, so I had to build it from 
 sources.
 Please push frequently snapshots to maven central.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CONFIGURATION-600) Loading xml configuration file as a stream does not work with multi configurations

2015-05-06 Thread John Henriksson (JIRA) 
John Henriksson created CONFIGURATION-600:
-

 Summary: Loading xml configuration file as a stream does not work 
with multi configurations
 Key: CONFIGURATION-600
 URL: https://issues.apache.org/jira/browse/CONFIGURATION-600
 Project: Commons Configuration
  Issue Type: Bug
Affects Versions: 1.8
Reporter: John Henriksson


When using the commons configuration inside a WAR loading a XML file works fine 
when done like this:

InputStream is = 
this.getClass().getClassLoader().getResourceAsStream(/conf/main.xml);
builder.load(is);

The problem is when the main.xml reference other xml files:
configuration
xml fileName=child1.xml/
/configuration

If the structure of the war is:
/
/classes
/conf/child1.xml
/conf/main.xml

There seems to be no way to pick up child1.xml from main.xml when loading 
main.xml as a stream.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (LANG-1134) New methods for lang3.Validate

2015-05-06 Thread Stardust (JIRA) 
Stardust created LANG-1134:
--

 Summary: New methods for lang3.Validate
 Key: LANG-1134
 URL: https://issues.apache.org/jira/browse/LANG-1134
 Project: Commons Lang
  Issue Type: Improvement
  Components: lang.*
Affects Versions: 3.4
Reporter: Stardust
Priority: Minor


These are suggestions for new methods for the Validate class.

h1. Floating point values

h2. notNaN(value)
Throws an exception if value != value .

{code}double value;

value = Double.NaN;
Validate.notNaN(value);// Throws exception

value = 1.0;
Validate.notNaN(value);// Validates

value = Double.POSITIVE_INFINITY;
Validate.notNaN(value);// Validates{code}

h2. finite(value)
Validates that the argument contains a numeric value (not NaN or infinite).

{code}double value;

value = Double.NaN;
Validate.notNaN(value);// Throws exception

value = Double.POSITIVE_INFINITY;
Validate.notNaN(value);// Throws exception

value = 1.0;
Validate.notNaN(value);// Validates{code}

h1. Integers and floats
The following methods are overloaded to accept both integers and floating point 
values.

h2. greater(reference, value), greaterOrEqual(reference, value)
Ensures the argument is greater than (or equal to) a given value.

{code}double value;

value = 0.0;
Validate.greater(0.0, value);// Throws exception
Validate.greaterOrEqual(0.0, value); // Validates

value = Double.POSITIVE_INFINITY;
Validate.greater(0.0, value);// Validates

value = Double.NaN;
Validate.greater(0.0, value);// Throws exception{code}

h2. smaller(reference, value), smallerOrEqual(reference, value)
Ensures the argument is smaller than (or equal to) a given value. Does the 
opposite of greater(), see example above.

h2. different(reference, value)
Ensures the argument is not equal to a given value. A typical use case would be 
to accept only non-zero values.

{code}double value;

value = 0.0;
different(0.0, value);// Throws exception
different(1.0, value);// Validates

value = Double.NaN;
different(0.0, value);// Validates{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (LANG-1134) New methods for lang3.Validate

2015-05-06 Thread Stardust (JIRA) 

 [ 
https://issues.apache.org/jira/browse/LANG-1134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stardust updated LANG-1134:
---
Description: 
These are suggestions for new methods for the Validate class.

h1. Floating point values

h2. notNaN(value)
Throws an exception if value != value .

{code}double value;

value = Double.NaN;
Validate.notNaN(value);// Throws exception

value = 1.0;
Validate.notNaN(value);// Validates

value = Double.POSITIVE_INFINITY;
Validate.notNaN(value);// Validates{code}

h2. finite(value)
Validates that the argument contains a numeric value (not NaN or infinite).

{code}double value;

value = Double.NaN;
Validate.finite(value);// Throws exception

value = Double.POSITIVE_INFINITY;
Validate.finite(value);// Throws exception

value = 1.0;
Validate.finite(value);// Validates{code}

h1. Integers and floats
The following methods are overloaded to accept both integers and floating point 
values.

h2. greater(reference, value), greaterOrEqual(reference, value)
Ensures the argument is greater than (or equal to) a given value.

{code}double value;

value = 0.0;
Validate.greater(0.0, value);// Throws exception
Validate.greaterOrEqual(0.0, value); // Validates

value = Double.POSITIVE_INFINITY;
Validate.greater(0.0, value);// Validates

value = Double.NaN;
Validate.greater(0.0, value);// Throws exception{code}

h2. smaller(reference, value), smallerOrEqual(reference, value)
Ensures the argument is smaller than (or equal to) a given value. Does the 
opposite of greater(), see example above.

h2. different(reference, value)
Ensures the argument is not equal to a given value. A typical use case would be 
to accept only non-zero values.

{code}double value;

value = 0.0;
different(0.0, value);// Throws exception
different(1.0, value);// Validates

value = Double.NaN;
different(0.0, value);// Validates{code}

  was:
These are suggestions for new methods for the Validate class.

h1. Floating point values

h2. notNaN(value)
Throws an exception if value != value .

{code}double value;

value = Double.NaN;
Validate.notNaN(value);// Throws exception

value = 1.0;
Validate.notNaN(value);// Validates

value = Double.POSITIVE_INFINITY;
Validate.notNaN(value);// Validates{code}

h2. finite(value)
Validates that the argument contains a numeric value (not NaN or infinite).

{code}double value;

value = Double.NaN;
Validate.notNaN(value);// Throws exception

value = Double.POSITIVE_INFINITY;
Validate.notNaN(value);// Throws exception

value = 1.0;
Validate.notNaN(value);// Validates{code}

h1. Integers and floats
The following methods are overloaded to accept both integers and floating point 
values.

h2. greater(reference, value), greaterOrEqual(reference, value)
Ensures the argument is greater than (or equal to) a given value.

{code}double value;

value = 0.0;
Validate.greater(0.0, value);// Throws exception
Validate.greaterOrEqual(0.0, value); // Validates

value = Double.POSITIVE_INFINITY;
Validate.greater(0.0, value);// Validates

value = Double.NaN;
Validate.greater(0.0, value);// Throws exception{code}

h2. smaller(reference, value), smallerOrEqual(reference, value)
Ensures the argument is smaller than (or equal to) a given value. Does the 
opposite of greater(), see example above.

h2. different(reference, value)
Ensures the argument is not equal to a given value. A typical use case would be 
to accept only non-zero values.

{code}double value;

value = 0.0;
different(0.0, value);// Throws exception
different(1.0, value);// Validates

value = Double.NaN;
different(0.0, value);// Validates{code}


 New methods for lang3.Validate
 --

 Key: LANG-1134
 URL: https://issues.apache.org/jira/browse/LANG-1134
 Project: Commons Lang
  Issue Type: Improvement
  Components: lang.*
Affects Versions: 3.4
Reporter: Stardust
Priority: Minor

 These are suggestions for new methods for the Validate class.
 h1. Floating point values
 h2. notNaN(value)
 Throws an exception if value != value .
 {code}double value;
 value = Double.NaN;
 Validate.notNaN(value);// Throws exception
 value = 1.0;
 Validate.notNaN(value);// Validates
 value = Double.POSITIVE_INFINITY;
 Validate.notNaN(value);// Validates{code}
 h2. finite(value)
 Validates that the argument contains a numeric value (not NaN or infinite).
 {code}double value;
 value = Double.NaN;
 Validate.finite(value);// Throws exception
 value = Double.POSITIVE_INFINITY;
 Validate.finite(value);// Throws exception
 value = 1.0;
 Validate.finite(value);// Validates{code}
 h1. Integers and floats
 The following methods are overloaded to accept both integers and floating 
 point values.
 h2. greater(reference, value), greaterOrEqual(reference, value)
 Ensures the argument is greater

[jira] [Updated] (LANG-1134) New methods for lang3.Validate

2015-05-06 Thread Stardust (JIRA) 

 [ 
https://issues.apache.org/jira/browse/LANG-1134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stardust updated LANG-1134:
---
Description: 
These are suggestions for new methods for the Validate class.

h1. Floating point values

h2. notNaN(value)
Throws an exception if value != value .

{code}double value;

value = Double.NaN;
Validate.notNaN(value);// Throws exception

value = 1.0;
Validate.notNaN(value);// Validates

value = Double.POSITIVE_INFINITY;
Validate.notNaN(value);// Validates{code}

h2. finite(value)
Validates that the argument contains a numeric value (not NaN or infinite).

{code}double value;

value = Double.NaN;
Validate.finite(value);// Throws exception

value = Double.POSITIVE_INFINITY;
Validate.finite(value);// Throws exception

value = 1.0;
Validate.finite(value);// Validates{code}

h1. Integers and floats
The following methods are overloaded to accept both integers and floating point 
values.

h2. greater(reference, value), greaterOrEqual(reference, value)
Ensures the argument is greater than (or equal to) a given value.

{code}double value;

value = 0.0;
Validate.greater(0.0, value);// Throws exception
Validate.greaterOrEqual(0.0, value); // Validates

value = Double.POSITIVE_INFINITY;
Validate.greater(0.0, value);// Validates

value = Double.NaN;
Validate.greater(0.0, value);// Throws exception{code}

h2. smaller(reference, value), smallerOrEqual(reference, value)
Ensures the argument is smaller than (or equal to) a given value. Does the 
opposite of greater(), see example above.

h2. different(reference, value)
Ensures the argument is not equal to a given value. A typical use case would be 
to accept only non-zero values.

{code}double value;

value = 0.0;
Validate.different(0.0, value);// Throws exception
Validate.different(1.0, value);// Validates

value = Double.NaN;
Validate.different(0.0, value);// Validates{code}

  was:
These are suggestions for new methods for the Validate class.

h1. Floating point values

h2. notNaN(value)
Throws an exception if value != value .

{code}double value;

value = Double.NaN;
Validate.notNaN(value);// Throws exception

value = 1.0;
Validate.notNaN(value);// Validates

value = Double.POSITIVE_INFINITY;
Validate.notNaN(value);// Validates{code}

h2. finite(value)
Validates that the argument contains a numeric value (not NaN or infinite).

{code}double value;

value = Double.NaN;
Validate.finite(value);// Throws exception

value = Double.POSITIVE_INFINITY;
Validate.finite(value);// Throws exception

value = 1.0;
Validate.finite(value);// Validates{code}

h1. Integers and floats
The following methods are overloaded to accept both integers and floating point 
values.

h2. greater(reference, value), greaterOrEqual(reference, value)
Ensures the argument is greater than (or equal to) a given value.

{code}double value;

value = 0.0;
Validate.greater(0.0, value);// Throws exception
Validate.greaterOrEqual(0.0, value); // Validates

value = Double.POSITIVE_INFINITY;
Validate.greater(0.0, value);// Validates

value = Double.NaN;
Validate.greater(0.0, value);// Throws exception{code}

h2. smaller(reference, value), smallerOrEqual(reference, value)
Ensures the argument is smaller than (or equal to) a given value. Does the 
opposite of greater(), see example above.

h2. different(reference, value)
Ensures the argument is not equal to a given value. A typical use case would be 
to accept only non-zero values.

{code}double value;

value = 0.0;
different(0.0, value);// Throws exception
different(1.0, value);// Validates

value = Double.NaN;
different(0.0, value);// Validates{code}


 New methods for lang3.Validate
 --

 Key: LANG-1134
 URL: https://issues.apache.org/jira/browse/LANG-1134
 Project: Commons Lang
  Issue Type: Improvement
  Components: lang.*
Affects Versions: 3.4
Reporter: Stardust
Priority: Minor

 These are suggestions for new methods for the Validate class.
 h1. Floating point values
 h2. notNaN(value)
 Throws an exception if value != value .
 {code}double value;
 value = Double.NaN;
 Validate.notNaN(value);// Throws exception
 value = 1.0;
 Validate.notNaN(value);// Validates
 value = Double.POSITIVE_INFINITY;
 Validate.notNaN(value);// Validates{code}
 h2. finite(value)
 Validates that the argument contains a numeric value (not NaN or infinite).
 {code}double value;
 value = Double.NaN;
 Validate.finite(value);// Throws exception
 value = Double.POSITIVE_INFINITY;
 Validate.finite(value);// Throws exception
 value = 1.0;
 Validate.finite(value);// Validates{code}
 h1. Integers and floats
 The following methods are overloaded to accept both integers and floating 
 point values.
 h2. greater(reference, value), greaterOrEqual(reference, value)

[jira] [Created] (LANG-1133) FastDateParser_TimeZoneStrategyTest#testTimeZoneStrategyPattern() fails on Windows with German Locale

2015-05-06 Thread Pascal Schumacher (JIRA) 
Pascal Schumacher created LANG-1133:
---

 Summary: 
FastDateParser_TimeZoneStrategyTest#testTimeZoneStrategyPattern() fails on 
Windows with German Locale
 Key: LANG-1133
 URL: https://issues.apache.org/jira/browse/LANG-1133
 Project: Commons Lang
  Issue Type: Bug
  Components: lang.time.*
Affects Versions: 3.5
 Environment: Windows 7, German Locale, Java7
Reporter: Pascal Schumacher
Priority: Minor


FastDateParser_TimeZoneStrategyTest#testTimeZoneStrategyPattern() on current 
master fails:

{quote}java.lang.AssertionError: Französisch:Heure d'Europe de l'Est UTC+3
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.assertTrue(Assert.java:41)
at 
org.apache.commons.lang3.time.FastDateParser_TimeZoneStrategyTest.testTimeZoneStrategyPattern(FastDateParser_TimeZoneStrategyTest.java:39){quote}

I'm unsure why. I guess it has something to do with my German Locale and maybe 
Windows too.





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] commons-lang pull request: @SuppressWarnings(deprecation) to joi...

2015-05-06 Thread coveralls 
Github user coveralls commented on the pull request:

https://github.com/apache/commons-lang/pull/84#issuecomment-99601310
  

[![Coverage 
Status](https://coveralls.io/builds/2502757/badge)](https://coveralls.io/builds/2502757)

Coverage increased (+0.01%) to 93.36% when pulling 
**82152f41ac8a727c2f0042bd555452dc2dda11b1 on 
PascalSchumacher:supress_compiler_warning** into 
**d6dd2b4cd4a337c5517952680c3714e5d08e9cb8 on apache:master**.



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] commons-lang pull request: @SuppressWarnings(deprecation) to joi...

2015-05-06 Thread coveralls 
Github user coveralls commented on the pull request:

https://github.com/apache/commons-lang/pull/84#issuecomment-99589501
  

[![Coverage 
Status](https://coveralls.io/builds/2502815/badge)](https://coveralls.io/builds/2502815)

Coverage decreased (-0.0%) to 93.35% when pulling 
**82152f41ac8a727c2f0042bd555452dc2dda11b1 on 
PascalSchumacher:supress_compiler_warning** into 
**d6dd2b4cd4a337c5517952680c3714e5d08e9cb8 on apache:master**.



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Updated] (LANG-1133) FastDateParser_TimeZoneStrategyTest#testTimeZoneStrategyPattern fails on Windows with German Locale

2015-05-06 Thread Pascal Schumacher (JIRA) 

 [ 
https://issues.apache.org/jira/browse/LANG-1133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pascal Schumacher updated LANG-1133:

Summary: FastDateParser_TimeZoneStrategyTest#testTimeZoneStrategyPattern 
fails on Windows with German Locale  (was: 
FastDateParser_TimeZoneStrategyTest#testTimeZoneStrategyPattern() fails on 
Windows with German Locale)

 FastDateParser_TimeZoneStrategyTest#testTimeZoneStrategyPattern fails on 
 Windows with German Locale
 ---

 Key: LANG-1133
 URL: https://issues.apache.org/jira/browse/LANG-1133
 Project: Commons Lang
  Issue Type: Bug
  Components: lang.time.*
Affects Versions: 3.5
 Environment: Windows 7, German Locale, Java7
Reporter: Pascal Schumacher
Priority: Minor

 FastDateParser_TimeZoneStrategyTest#testTimeZoneStrategyPattern() on current 
 master fails:
 {quote}java.lang.AssertionError: Französisch:Heure d'Europe de l'Est UTC+3
   at org.junit.Assert.fail(Assert.java:88)
   at org.junit.Assert.assertTrue(Assert.java:41)
   at 
 org.apache.commons.lang3.time.FastDateParser_TimeZoneStrategyTest.testTimeZoneStrategyPattern(FastDateParser_TimeZoneStrategyTest.java:39){quote}
 I'm unsure why. I guess it has something to do with my German Locale and 
 maybe Windows too.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] commons-lang pull request: @SuppressWarnings(deprecation) to joi...

2015-05-06 Thread PascalSchumacher 
Github user PascalSchumacher commented on a diff in the pull request:

https://github.com/apache/commons-lang/pull/84#discussion_r29793834
  
--- Diff: src/main/java/org/apache/commons/lang3/StringUtils.java ---
@@ -4196,7 +4196,8 @@ public static String join(final Iterable? iterable, 
final String separator) {
  * @return the joined String.
  * @throws java.lang.IllegalArgumentException if a null varargs is 
provided
  */
-public static String joinWith(final String separator, final Object... 
objects) {
+@SuppressWarnings(deprecation)
--- End diff --

good point


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (CONFIGURATION-600) Loading xml configuration file as a stream does not work with multi configurations

2015-05-06 Thread Oliver Heger (JIRA) 

[ 
https://issues.apache.org/jira/browse/CONFIGURATION-600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14531228#comment-14531228
 ] 

Oliver Heger commented on CONFIGURATION-600:


I assume you are using {{DefaultConfigurationBuilder}} for loading the file, do 
you? This class has a method for setting a base path. The base path is taken 
into account when resolving child configuration files.

You can set the base path to a URL (in string form) obtained via 
this.getClass().getClassLoader().getResource(). I am not sure whether this 
works with URLs pointing to elements in a jar file though, but you should give 
it a try.

 Loading xml configuration file as a stream does not work with multi 
 configurations
 --

 Key: CONFIGURATION-600
 URL: https://issues.apache.org/jira/browse/CONFIGURATION-600
 Project: Commons Configuration
  Issue Type: Bug
Affects Versions: 1.8
Reporter: John Henriksson

 When using the commons configuration inside a WAR loading a XML file works 
 fine when done like this:
 InputStream is = 
 this.getClass().getClassLoader().getResourceAsStream(/conf/main.xml);
 builder.load(is);
 The problem is when the main.xml reference other xml files:
 configuration
 xml fileName=child1.xml/
 /configuration
 If the structure of the war is:
 /
 /classes
 /conf/child1.xml
 /conf/main.xml
 There seems to be no way to pick up child1.xml from main.xml when loading 
 main.xml as a stream.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LANG-1121) FastDateFormat.parse() does not handle wrong length string

2015-05-06 Thread Henry Kang (JIRA) 

[ 
https://issues.apache.org/jira/browse/LANG-1121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14532030#comment-14532030
 ] 

Henry Kang commented on LANG-1121:
--

Thanks for commit tests.
I agree that is same behavior as SimpleDateFormat.
However, It is incorrect operation, I think.

format : MMdd
input : 20150429113100

It matches pattern (\p{Nd{4}}+)(\p{Nd{2}+)(\p{Nd}++).
It works , MM, and the others are dd (don't care how long digits)

Is there any plan for patches, or not?

 FastDateFormat.parse() does not handle wrong length string
 --

 Key: LANG-1121
 URL: https://issues.apache.org/jira/browse/LANG-1121
 Project: Commons Lang
  Issue Type: Bug
  Components: lang.time.*
Affects Versions: 3.3.2
Reporter: Henry Kang
Assignee: Charles Honton
Priority: Minor
 Fix For: Patch Needed


 FDFP does not handled wrong length string.
 for example,
 {code}
 // Wed Apr 29 00:00:00 KST 2015
 FastDateFormat.getInstance(MMdd).parse(20150429);
 // throws ParseException
 FastDateFormat.getInstance(MMdd).parse(2015);
 // Thu Mar 16 00:00:00 KST 81724
 FastDateFormat.getInstance(MMdd).parse(20150429113100);
 {code}
 I think result of third throws ParseException,
 but FastDateFormat.parse() returns wrong year, ex, 81724 instead of 2015.
 As I tested,
 regex.matcher.group = (2015)(04)(29113100) = setCalendar = March 16, 81724



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (LANG-1121) FastDateFormat.parse() does not handle wrong length string

2015-05-06 Thread Henry Kang (JIRA) 

[ 
https://issues.apache.org/jira/browse/LANG-1121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14532030#comment-14532030
 ] 

Henry Kang edited comment on LANG-1121 at 5/7/15 5:26 AM:
--

Thanks for commit tests.
I agree that is same behavior as SimpleDateFormat.
However, It is incorrect operation, I think.

format : MMdd
input : 20150429113100

It matches pattern below
{code}(\p{Nd{4}}+)(\p{Nd{2}+)(\p{Nd}++){code}
It works , MM, and the others are dd (don't care how long digits)

Is there any plan for patches, or not?


was (Author: freeism):
Thanks for commit tests.
I agree that is same behavior as SimpleDateFormat.
However, It is incorrect operation, I think.

format : MMdd
input : 20150429113100

It matches pattern (\p{Nd{4}}+)(\p{Nd{2}+)(\p{Nd}++).
It works , MM, and the others are dd (don't care how long digits)

Is there any plan for patches, or not?

 FastDateFormat.parse() does not handle wrong length string
 --

 Key: LANG-1121
 URL: https://issues.apache.org/jira/browse/LANG-1121
 Project: Commons Lang
  Issue Type: Bug
  Components: lang.time.*
Affects Versions: 3.3.2
Reporter: Henry Kang
Assignee: Charles Honton
Priority: Minor
 Fix For: Patch Needed


 FDFP does not handled wrong length string.
 for example,
 {code}
 // Wed Apr 29 00:00:00 KST 2015
 FastDateFormat.getInstance(MMdd).parse(20150429);
 // throws ParseException
 FastDateFormat.getInstance(MMdd).parse(2015);
 // Thu Mar 16 00:00:00 KST 81724
 FastDateFormat.getInstance(MMdd).parse(20150429113100);
 {code}
 I think result of third throws ParseException,
 but FastDateFormat.parse() returns wrong year, ex, 81724 instead of 2015.
 As I tested,
 regex.matcher.group = (2015)(04)(29113100) = setCalendar = March 16, 81724



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)