Local repository corrupted?

[Robert Leach]

USE CASE: WHAT DO YOU WANT TO DO?

Get a working copy of TreeView3 loaded into Eclipse

STEPS TO REPRODUCE AN ISSUE (OR TRIGGER A NEW FEATURE)

1. Switch to master
2. Pull
3. Try to run treeview using the run button

CURRENT BEHAVIOR

After I did a pull on master today (10/13/2016), my directory structure radically changed, I have all sorts of errors and warnings, and I cannot run treeview. Here is the error I get when I try to run treeview (ignoring errors):

Error: Could not find or load main class edu.stanford.genetics.treeview.app.TreeView3

Here are a few screen-caps:

Directory structure of the working branch I'd switched from:

Directory structure of master after pulling:

Window I get when I try to run treeview:

While that window is open, I get multiple of these warnings:

I eventually get this error:

Errors exist in src.test.java.ui/MapContainerTest.java

I opened it up and it's littered with tons of errors.

EXPECTED BEHAVIOR

I expected a minor change to master involving the recent update to resolve the classpath issue.

DEVELOPERS ONLY SECTION

SUGGESTED CHANGE (Pseudocode optional)

I don't know whether my installation got corrupted or what. Our internet was down for a good chunk of the afternoon. But when I try to pull on master, it says I'm up to date. When I try to run treeview, I don't get that build progress window anymore.

Anyone know how I fix this?

FILES AFFECTED (where the changes will be implemented) - developers only

most/all of them

LEVEL OF EFFORT - developers only

major

COMMENTS

[Christopher Keil]

Did you attempt to run gradle? (navigate to the treeview root folder in Terminal and just type gradle)

The .classpath file was removed from the repo. It is generated by the eclipse task in the build script.

[Robert Leach]

Copied the .classpath over from another branch where I still had it, then did a clean, refresh, fresh build. Seems to have fixed it, though I have a weird src directory now containing 2 empty directories: main & test

[Robert Leach]

Not merged to master, because it involves a local .classpath file.

[Robert Leach]

Oh, gradle. OK. Didn't think of that. Doh!

[Christopher Keil]

@hepcat72 Incidentally I did a complete fresh install of Eclipse, Git, Gradle and then setup TreeView after I had committed the classpath issue. The Gradle build job creates an Eclipse project setup. In fact you can always use the "import existing project" option in Eclipse after running the Gradle build script once because it generates all necessary files (.project is another one)!

I found that very convenient just now (my entire hard drive was wiped and this in conjunction with Git made setup super quick)