[
https://issues.apache.org/jira/browse/MNG-6710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16885932#comment-16885932
]
Markus Bader commented on MNG-6710:
-----------------------------------
I don't think this would help since the issue is not reproducable on other
machines (except the one of the special colleague). In my opinion, it doesn't
concern to the command line length, because:
* my colleague, who has the same problems, uses a shorter path
* it works for me, when I rename the project directory to a longer value
* it works, when I modify the Java classes
I just tried it again and copied my project folder. The new folder was named
"daev-forms - Kopie". Here the build also failes with a StackOverflow. When I
rename it to e.g. "daev-forms-so", it works. Also "daev-forms-stackoverflow"
and "daev-forms-with-a very-very-long-value-which-is-really-really-long" work.
First of all I thought that the path is saved somewhere in any configuration so
that the system behaves different when I work in this folder. But I never used
the name "daev-forms - Kopie" before. So why does the issue appear with this
directory? Ok, it could be that I used this folder name a long time ago, since
I struggle with this problem for a long time (since last year?).
Is there a configuration file or similar where paths are saved? I could not
find any.
> Stackoverflow while compiling Java Sources, but works after renaming project
> directory
> --------------------------------------------------------------------------------------
>
> Key: MNG-6710
> URL: https://issues.apache.org/jira/browse/MNG-6710
> Project: Maven
> Issue Type: Bug
> Affects Versions: 3.6.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)
