-
Notifications
You must be signed in to change notification settings - Fork 317
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ZipException when running Mwe2Launcher in IntelliJ IDEA (caused by broken classpath) #1953
Comments
maybe there is something broken in your maven repo. |
thus the question would be: why is this file added to pathes. |
The file is part of the IntelliJ IDEA installation, which is why I've initially opened the bug report there (link in my first post). Why the file is there and why it gets added to the classpath by IntelliJ is beyond me. I have opened this issue to see if the problem could also be adressed in xText: I believe it is problematic that the Maven goal fails with a ZIP exception and no information which file causes the problem. This had stumped several colleages until I decided to debug the build process. So either more information (i.e. which file caused the exception to be thrown) or not failing the build at all and only issuing a warning would be great. Also I'm sorry if this is the wrong bug tracker and it should be moved to one of the Mwe2 projects at eclipse.org. But the top stack trace entry says org.eclipse.xtext, so I figured this is the right place. |
PathTraverser is part of the xtext-core codebase the issue location is correct. |
Signed-off-by: Christian Dietrich <christian.dietrich@itemis.de>
Signed-off-by: Christian Dietrich <christian.dietrich@itemis.de>
[eclipse/xtext#1953] print broken zip file when traversing archive fails
logging added. |
I'm experiencing the same issue on Xtext 2.27.0. Although the logging helps with identifying the faulty file, it would be nice if |
When executing the Mwe2Launcher in an xText project using Maven and IntelliJ IDEA, the execution fails with a ZipException. As far as I can tell (using the debugger), this is caused by a non-JAR file (plexus-classworlds.license) being on the classpath. I have already opened an issue in the IntelliJ bugtracker for this but I think this also should be adressed in Mwe2/xText: a broken classpath entry should not (in my opinion) cause the execution to fail, a warning would suffice (including the broken file).
The text was updated successfully, but these errors were encountered: