Skip to content
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

EclipseHelperMojo doesn't load EclipseHelper when project linked #10

Open
hinerm opened this issue Jan 21, 2015 · 2 comments
Open

EclipseHelperMojo doesn't load EclipseHelper when project linked #10

hinerm opened this issue Jan 21, 2015 · 2 comments

Comments

@hinerm
Copy link
Member

hinerm commented Jan 21, 2015

When building SCIFIO in Eclipse with project-linkage to SciJava-common, I get an exception with the message: Could not load EclipseHelper.

This comes from a failure to load the org.scijava.annotations.EclipseHelper.class in the EclipseHelperMojo when SJC is project-linked in Eclipse as a dependency of the project I was building.

I checked the built classpath and confirmed that it did point to a path on disk that would find the EclipseHelper class.

The temporary workaround is to close the SJC project in Eclipse.

Occurred on Windows 8.1, Eclipse 4.4.0 and scijava-maven-plugin 0.4.4.

stack trace

java.net.URLClassLoader$1.run(Unknown Source)
java.net.URLClassLoader$1.run(Unknown Source)
java.security.AccessController.doPrivileged(Native Method)
java.net.URLClassLoader.findClass(Unknown Source)
java.lang.ClassLoader.loadClass(Unknown Source)
java.lang.ClassLoader.loadClass(Unknown Source)
org.scijava.maven.plugin.EclipseHelperMojo.execute(EclipseHelperMojo.java:105)
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133)
org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:328)
@hinerm hinerm added the bug label Jan 21, 2015
@ctrueden
Copy link
Member

Thanks to 3f371b4, there is a friendly suggestion to close scijava-common in case it is an open project linkage. This is good enough for me—it helped me when I ran into the same situation. Technically, this is still an open issue, but I'm assigning to unscheduled milestone since I see no need to address it in the foreseeable future.

@ctrueden ctrueden added this to the unscheduled milestone Mar 23, 2015
@hinerm
Copy link
Member Author

hinerm commented Mar 23, 2015

🐙

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants