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

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

thijsrijpert opened a new pull request, #244:
URL: https://github.com/apache/maven-compiler-plugin/pull/244

   …Timestamp is empty
   
   Following this checklist to help us incorporate your 
   contribution quickly and easily:
   
    - [ ] Make sure there is a [JIRA 
issue](https://issues.apache.org/jira/browse/MCOMPILER) filed 
          for the change (usually before you start working on it).  Trivial 
changes like typos do not 
          require a JIRA issue.  Your pull request should address just this 
issue, without 
          pulling in other changes.
    - [ ] Each commit in the pull request should have a meaningful subject line 
and body.
    - [ ] Format the pull request title like `[MCOMPILER-XXX] - Fixes bug in 
ApproximateQuantiles`,
          where you replace `MCOMPILER-XXX` with the appropriate JIRA issue. 
Best practice
          is to use the JIRA issue title in the pull request title and in the 
first line of the 
          commit message.
    - [ ] Write a pull request description that is detailed enough to 
understand what the pull request does, how, and why.
    - [ ] Run `mvn clean verify` to make sure basic checks pass. A more 
thorough check will 
          be performed on your pull request automatically.
    - [ ] You have run the integration tests successfully (`mvn -Prun-its clean 
verify`).
   
   If your pull request is about ~20 lines of code you don't need to sign an
   [Individual Contributor License 
Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure
   please ask on the developers list.
   
   To make clear that you license your contribution under 
   the [Apache License Version 2.0, January 
2004](http://www.apache.org/licenses/LICENSE-2.0)
   you have to acknowledge this by using the following check-box.
   
    - [x] I hereby declare this contribution to be licenced under the [Apache 
License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
   
    - [ ] In any other case, please file an [Apache Individual Contributor 
License Agreement](https://www.apache.org/licenses/icla.pdf).
   
   




> 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