It looks like the program was started from the standard maven artifact. It therefore includes junit and (before the conversion to GitHub) had an empty test folder.

Do you have any unit tests to add (otherwise I'll drop the junit dependency [a small overhaul of the POM is the last thing I plan to do])?

This would show directly which version is available (0.6-Beta, 0.7-Beta and the "new" 0.7 can be in as a starting point), highlight the differences (at least the ones that we're aware of) and allows for direct download.

If you're ok with this but don't want to do it then I'm happy to help.

@ipolevoy
I've did this and some other POM specific changes, hope you're fine with these (otherwise I'll revert them as I wanted to place this into a PR (which got screwed up when I've tried to merge master into this branch).

I just thought I've broken something but it is actually in the code...

I guess the Options dialog would have at least the current settings from the configuration in and maybe filtering options.
Is there anything else that comes to mind?

If the option dialog is expected tbd for the next months, too then it would be reasonable to deactivate the menu entry until then.

Hey!
Just a quick suggestion: it would be really nice if we could input a list of jars separated by ; instead of a root directory.

Feel free to delete if this is non-sense for you, just wanted to highlight it...

Checking https://github.com/javalite/jar-explorer/commits/master everybody sees the email from the account you've used on google code.
This should (theoretically) be replaced by a link to your current account if you add this mail under https://github.com/settings/emails and verify it.