Repository navigation
error importing libraries into eclipse #54
Description
We have tried to get Strongback working in eclipse on multiple Windows machines with the same failure. When we get to the point where we import Strongback.userlibraries there is a path error. It appears that there is a slash missing. I have not been able to identify where the path is set.
Here is the relevant error:
org.eclipse.jdt.internal.core.ClasspathEntry$Asser tionFailedException: Path for IClasspathEntry must be absolute: C:Usersjoe_bstrongback/java/lib/strongback.jar
My username is joe_b on this machine, you will note the missing '/' before 'strongback'.
We were able to get things working with ease on a Mac, but most of our team's machines are Windows.
I submit this issue on Chief Delphi in case others run into it as a reply to the introduction post at: http://www.chiefdelphi.com/forums/showpost.php?p=1521168&postcount=17
Activity
rhauch commentedon Jan 11, 2016
What are the contents of the
strongback.propertiesfile that is located in the Strongback installation directory?rhauch commentedon Jan 11, 2016
@Zabot, can you check that this line is properly handling values for
user.homethat do not end with a slash? That might be the case on Windows.rhauch commentedon Jan 11, 2016
@Bussell, you can try to correct the
/strongback/java/templates/Strongback.userlibraries.import.templatefile to have the valid paths, and then import again into Eclipse. I know it's not ideal, but it should allow you to work around the problem until we can fix it.rhauch commentedon Jan 11, 2016
@Bussell: Thanks for supplying your
strongback.propertiesfile; that helps narrow down the problem to likely be in the command line tool rather than the environment.I'm not convinced that workaround will solve all of the problems, but it should allow you to manually import the user library so that your projects can compile. If the problem is where I suspect, the
strongbackcommand line functionality will have problems on Windows, but you could always have your Mac users create the projects or add Strongback to them. Then when they share their code, you should get the correct project definitions, and each of your Eclipse workspaces should compile your robot project since each would have the correct user library.We'll try to get this fixed in the next day or two, though.
rhauch commentedon Jan 12, 2016
@Bussell: I've found the problem (see #55 for the changes), and have released a new version of Strongback with the fix. I've updated the book, so please remove the existing
strongbackdirectory, then download and install the version 1.1.1. Everything else like your path should work as-is, and you can even verify the version withstrongback.bat version(orstrongback.sh versionon OS X and Linux).rhauch commentedon Jan 12, 2016
@Bussell: are you sure you are using 1.1.1?
rhauch commentedon Jan 12, 2016
Please follow the instructions to create a temporary project.
rhauch commentedon Jan 12, 2016
Make sure that the
Strongbackuser library doesn't exist in your workspace preferences, and if it does then remove it.Then check the
C:\Users\joe_b\strongback\java\eclipsedirectory: there should be a single file, and if that has corrupted paths then no matter what you do you will not be able to import it into Eclipse.rhauch commentedon Jan 12, 2016
See the "Adding Strongback to your project" section of the (Getting Started chapter)[https://strongback.gitbooks.io/using-strongback/content/getting_started.html].
With the
-eoption? You can try adding a-Doption, which will output some debug messages. I wouldn't mind seeing that output.Again, check the contents of the
C:\Users\joe_b\strongback\java\eclipse\Strongback.userlibrariesfile.Delete the
.metadatafolder inside your Eclipse workspace folder. You are sure you have the latest WPILib plugins, too? What version of Windows? I tested this on Windows 10, and I don't have access to anything older tonight.rhauch commentedon Jan 12, 2016
@Bussell wrote:
What
build.propertiesfile? There's only one in the Strongback installation directory, and it's inside anantfolder and won't have the Strongback version in it. There is astrongback/strongback.propertiesfile that will have the version number in it.rhauch commentedon Jan 12, 2016
@Bussell:
The strange thing is that if you completely removed the
strongbackdirectory, then the first time you would have runstrongback.bat new-projectwith 1.1.1 it would have created the correctuserlibrariesfile. Subsequent runs shouldn't have changed it.Regardless, I think most of that was leftover from your previous attempts. Glad you got it working and thanks for your patience -- it shouldn't have been that difficult.
rhauch commentedon Jan 12, 2016
Thanks again for logging this and working with me to verify your problem was indeed fixed. Best of luck to your team!
renamed MotorOutput to DutyCycle (strongback#54)
Move networktables into strongback (#1)