[
https://issues.apache.org/jira/browse/MCOMPILER-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16893723#comment-16893723
]
Markus Bader commented on MCOMPILER-394:
----------------------------------------
Yes, that's the problem. It's even for me not reproducable in another
environment. As I said, it suffices to copy the whole project into another
directory or just rename the directory and the error ist not reproducable.
I've tried to minimize the number of Java classes for providing a sample
project (my project has 150 classes). While minimizing the number of classes
the error disappeared when I removed the class MathParser I mentioned above. I
don't really think that this class is the cause. I always ask me: "Why does the
error disappear when I rename the directory?". I think, the error would also
disappear when I remove other classes. I will try this.
I also tried to increase the memory size with "-J -Xss4096M -Xms:4096m" but
this didn't change anything.
> 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 and also with Windows
> 7.
> 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 "xxxxx".
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
