[ 
https://issues.apache.org/jira/browse/MCOMPILER-592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17850995#comment-17850995
 ] 

ASF GitHub Bot commented on MCOMPILER-592:
------------------------------------------

thijsrijpert commented on PR #244:
URL: 
https://github.com/apache/maven-compiler-plugin/pull/244#issuecomment-2141522932

   From JIRA issue:
   
   Due to a combination of plugins, it is possible for the 
project.build.outputTimestamp property to have an empty string as a value. This 
causes an IndexOutOfBoundsException on line 1242 when it tries to access the 
first character in the string.
   
   This can be fixed by doing an isEmpty check before doing the charAt check. I 
will create an PR for this.
   
   While this bug is caused by another plugin, I think this should be fixed in 
the compiler because the error returned (IndexOutOfBoundsException), is vague 
and hard to debug.
   
   The workaround for this issue is setting the project.build.outputTimestamp 
property with an arbitrary value.




> IndexOutOfBoundsException when project.build.outputTimestamp is empty
> ---------------------------------------------------------------------
>
>                 Key: MCOMPILER-592
>                 URL: https://issues.apache.org/jira/browse/MCOMPILER-592
>             Project: Maven Compiler Plugin
>          Issue Type: Bug
>    Affects Versions: 3.12.0, 3.12.1, 3.13.0
>            Reporter: Thijs Rijpert
>            Priority: Minor
>
> Due to a combination of plugins, it is possible for the 
> project.build.outputTimestamp property to have an empty string as a value. 
> This causes an IndexOutOfBoundsException on line 1242 when it tries to access 
> the first character in the string. 
> This can be fixed by doing an isEmpty check before doing the charAt check. I 
> will create an PR for this.
> While this bug is caused by another plugin, I think this should be fixed in 
> the compiler because the error returned (IndexOutOfBoundsException), is vague 
> and hard to debug.
> The workaround for this issue is setting the project.build.outputTimestamp 
> property with an arbitrary value.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to