[
https://issues.apache.org/jira/browse/MCOMPILER-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17542842#comment-17542842
]
Markus Bader commented on MCOMPILER-394:
----------------------------------------
It's not easy. I tried it with a blank project with only one test class and
could not reproduce the issue. I tried it with 400 attributes in one class.
Then I tried to add this class to an existing, more complex project and I still
was not able to get the error. But after increasing the number of attributes to
1000, the error occured.
So try following: Take my class with 1000 attributes, add it to an own, complex
maven project and try to compile it. If not reproducable, increase the number
of attributes (incl. getter, setter, toString()).
[^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 "xxxxx".
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
