Re: maven-assembly-plugin StackOverflowError
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. We increased it to 2m and the assembler plugin was able to handle the recursive stack size. -- View this message in context: http://maven.40175.n5.nabble.com/maven-assembly-plugin-StackOverflowError-tp3321403p5039058.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-assembly-plugin StackOverflowError
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) org.apache.poi poi-ooxml-schemas Not sure if this would help you. -- View this message in context: http://maven.40175.n5.nabble.com/maven-assembly-plugin-StackOverflowError-tp3321403p4528687.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-assembly-plugin StackOverflowError
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: http://maven.40175.n5.nabble.com/maven-assembly-plugin-StackOverflowError-tp3321403p3321427.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-eclipse-plugin Does not resolve workspace project name
> 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 being
developed in parallel). They will both have the same artifact ID but
eclipse forces a different project name. I don't think asking m-e-p to
offer this functionality is really an isnane request.
The eclipse:eclipse plugin has worked perfectly fine as I have used it minus
this one issue. The resolution was extremely easy.
Including a new configuration parameter the method createEclipseWriterConfig
just needs
if(evaluateArtifactsFromEclipseWorkspace){
projectName = projectBaseDir.getName();
}
Problem solved.
--
View this message in context:
http://maven.40175.n5.nabble.com/maven-eclipse-plugin-Does-not-resolve-workspace-project-name-tp3237890p3242262.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
maven-eclipse-plugin Does not resolve workspace project name
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 originally configured it with. When I run eclipse:eclipse the project name in the .project file will be the artifactId (by default) despite the eclipse project name being something different. Now lets say we have a new project that depends on the project we just created. We run the eclipse goal on the new project, and with useProjectReferences enabled, the classpath references the name of the project based on the artifactID. This causes a problem when eclipse tries to build new projects workspace because the eclipse workspace project is one thing and the .project's project is something completely different. How come the maven-eclipse-plugin will never resolve the workspace project name to the .project project name. Or even offer a flag like true to override the original functionality? -- View this message in context: http://maven.40175.n5.nabble.com/maven-eclipse-plugin-Does-not-resolve-workspace-project-name-tp3237890p3237890.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
