[jira] [Updated] (MCOMPILER-394) Stackoverflow while compiling Java Sources, but works after renaming project directory
[
https://issues.apache.org/jira/browse/MCOMPILER-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Markus Bader updated MCOMPILER-394:
---
Attachment: MCompiler394.java
> Stackoverflow while compiling Java Sources, but works after renaming project
> directory
> --
>
> Key: MCOMPILER-394
> URL: https://issues.apache.org/jira/browse/MCOMPILER-394
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.1
> Environment: The problem occurs with Windows 10, Windows 7 and also
> with Ubuntu.
>Reporter: Markus Bader
>Priority: Major
> Attachments: MCompiler394.java, build.log
>
>
> Me and one of my colleagues have following problem (others do not): We want
> to build a maven project, but "mvn clean install" ends up in a stackoverflow
> error. But after renaming the project directory, it works. Also after
> renaming the name of the parent directory and leaving the name of the project
> directory by its original value, compilation is possible.
> I also tried changing the artifactId so that it doesn't match the folder
> name. Result: stackoverflow.
> To make it more strange: I tried to reduce the used Java classes for possibly
> identifying a class to be responsible for this phenomenon. Therefor I deleted
> a class named "MathParser" and after that compilation was possible. So I
> analysed the content of the class and found out, that the stackoverflow error
> occurs even if the class ist nearly empty. With following content I can
> reproduce the error:
>
> {code:java}
> package some.anonymised.package;
> public class MathParser {
> private void doSomething(String func) throws Exception {
> throw new Exception ("function '" + func + "' is not defined");
> }
> } {code}
> With an empty method body, the build works fine.
> I attached the log created with debug option activated (with reduced number
> of classes and reduced content of MathParser). For anonymisation purposes I
> replaced the name of some directories, packages etc. by "x".
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (MCOMPILER-394) Stackoverflow while compiling Java Sources, but works after renaming project directory
[
https://issues.apache.org/jira/browse/MCOMPILER-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Markus Bader updated MCOMPILER-394:
---
Environment: The problem occurs with Windows 10, Windows 7 and also with
Ubuntu. (was: The problem occurs with Windows 10 and also with Windows 7.)
> Stackoverflow while compiling Java Sources, but works after renaming project
> directory
> --
>
> Key: MCOMPILER-394
> URL: https://issues.apache.org/jira/browse/MCOMPILER-394
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.1
> Environment: The problem occurs with Windows 10, Windows 7 and also
> with Ubuntu.
>Reporter: Markus Bader
>Priority: Major
> Attachments: build.log
>
>
> Me and one of my colleagues have following problem (others do not): We want
> to build a maven project, but "mvn clean install" ends up in a stackoverflow
> error. But after renaming the project directory, it works. Also after
> renaming the name of the parent directory and leaving the name of the project
> directory by its original value, compilation is possible.
> I also tried changing the artifactId so that it doesn't match the folder
> name. Result: stackoverflow.
> To make it more strange: I tried to reduce the used Java classes for possibly
> identifying a class to be responsible for this phenomenon. Therefor I deleted
> a class named "MathParser" and after that compilation was possible. So I
> analysed the content of the class and found out, that the stackoverflow error
> occurs even if the class ist nearly empty. With following content I can
> reproduce the error:
>
> {code:java}
> package some.anonymised.package;
> public class MathParser {
> private void doSomething(String func) throws Exception {
> throw new Exception ("function '" + func + "' is not defined");
> }
> } {code}
> With an empty method body, the build works fine.
> I attached the log created with debug option activated (with reduced number
> of classes and reduced content of MathParser). For anonymisation purposes I
> replaced the name of some directories, packages etc. by "x".
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
