I ended up getting this resolved some time ago but I figure I post the best
solution. The stackoverflow isnt a product of infinite recursion it's just
a matter of recursion that is simply too deep because of how far down the
file directory tree goes.
Simply increasing the stack size with -Xss.
The best I could do was to exclude the dependency itself (this works for me
because I needed a subset of the code that was not effected by the
exclusion)
exclusion
groupIdorg.apache.poi/groupId
artifactIdpoi-ooxml-schemas/artifactId
/exclusion
Not sure if this would help you.
A quick update. Despite having other poi dependencies, this is the only one
which causes the StackOverFlow. It occurs when the plugin imports the xsb's
into the jar.
--
View this message in context:
This is not m-e-p's problem. Stop renaming your projects if you want
to use m-e-p and use it to regenerate the .project files. Keep the
name as the artifactId, or change the artifactId in the pom to meet
your needs.
Lets assume a person is working on two different version (two releases
When running the eclipse goal, the project name that gets set in the project
description may not be the project you will initially save it as.
For example, I create a project with some name. I configure a pom to have a
different artifactId, groupId that do not relate to the project name I
