Eclipse plugin won't work in dropins folder in Eclipse 3.4 (Ganymede)
---------------------------------------------------------------------

                 Key: CDV-814
                 URL: https://jira.terracotta.org/jira//browse/CDV-814
             Project: Community Development
          Issue Type: Bug
          Components: Eclipse Plugin
    Affects Versions: trunk-nightly
            Reporter: Walter Harley
            Assignee: Issue Review Board


Installed nightly build (rev9424) of Eclipse plugin in the 'dropins' folder per 
Ganymede (Eclipse 3.4) recommendations.  Added Terracotta nature to a project 
and clicked finish.  Received following stack trace.

Note that 'dropins' is a new thing for Ganymede; it is no longer recommended to 
put third-party plugins directly into the 'plugins' folder, because of the new 
provisioning code (aka p2).

I suspect that what's going on is that TC is using the bundle location as a way 
of building a path to somewhere to store config information.  This is not ideal 
Eclipse practice; rather, APIs like Plugin.getStateLocation, 
Platform.getConfigurationLocation, or Platform.getInstallLocation are probably 
better, if that's in fact the issue.

org.eclipse.core.runtime.AssertionFailedException: assertion failed: Path for 
IClasspathEntry must be absolute: 
file:/Developer/Applications/eclipse/dropins/deploy/build.eclipse/src.classes
        at org.eclipse.core.runtime.Assert.isTrue(Assert.java:111)
        at org.eclipse.jdt.core.JavaCore.newLibraryEntry(JavaCore.java:4013)
        at org.eclipse.jdt.core.JavaCore.newLibraryEntry(JavaCore.java:3901)
        at 
org.eclipse.jdt.launching.JavaRuntime.newArchiveRuntimeClasspathEntry(JavaRuntime.java:610)
        at 
org.terracotta.dso.ClasspathProvider.computeUnresolvedClasspath(ClasspathProvider.java:49)
        at 
org.eclipse.jdt.internal.launching.RuntimeClasspathProvider.computeUnresolvedClasspath(RuntimeClasspathProvider.java:53)
        at 
org.eclipse.jdt.launching.JavaRuntime.computeUnresolvedRuntimeClasspath(JavaRuntime.java:1173)
        at 
org.eclipse.jdt.launching.AbstractJavaLaunchConfigurationDelegate.getBootpathExt(AbstractJavaLaunchConfigurationDelegate.java:301)
        at 
org.eclipse.jdt.launching.AbstractJavaLaunchConfigurationDelegate.getVMSpecificAttributesMap(AbstractJavaLaunchConfigurationDelegate.java:568)
        at 
org.eclipse.jdt.launching.JavaLaunchDelegate.launch(JavaLaunchDelegate.java:68)
        at 
org.terracotta.dso.BootJarHelper.getBootJarName(BootJarHelper.java:92)
        at 
org.terracotta.dso.actions.BuildBootJarAction.doFinish(BuildBootJarAction.java:143)
        at 
org.terracotta.dso.actions.BuildBootJarAction.run(BuildBootJarAction.java:102)
        at 
org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://jira.terracotta.org/jira//secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        
_______________________________________________
tc-dev mailing list
[email protected]
http://lists.terracotta.org/mailman/listinfo/tc-dev

Reply via email to