For Developers - JOverseer/joverseer GitHub Wiki

appveyor build status travisci

Continuous Integration

The master branch is now monitored by TavisCI for linux and mac builds, and Appveyor for windows.

Initially this performs ant test which compiles the jars, and does minimal test, but at least launches the program, giving us a baseline level of confidence.

Ideally, we'll migrate to continuous deployment, when we have a more automated tests.

What the exercise has also shown is that we should probably migrate to Maven to offload managing most of the third-party libraries.

Setting up development with Eclipse

  • Start with a an empty workspace. (That's just an empty folder to you and me.)
  • Then File->Import...*
  • select sub folder Git->Projects from Git
  • Next
  • select Clone URI
  • Next
  • copy and paste the URI from the github JO repository and the green 'Code' button.
  • https://github.com/JOverseer/joverseer.git
  • Next
  • Select the branche(s) you want by ticking and unticking. Typically you will want just the 'master' branch.
  • Next
  • Pick somewhere sensible for the download. I don't recommend making it a subdirectory of the eclipse workspace.

create a new working set as the logical container for the java projects

select only the projects

  • joverseerjar
  • joverseerupdaterjar
  • jOverseerRelease
  • lib
  • orderchecker
  • txt2xmljar

Not anything else that looks like an 'overall' project like JOverseerDevelopment

joverseerupdaterjar may show a red ! and in the Build Path may complain about directory 'test' missing.

if so, outside eclipse, create the test directory under joverseerupdaterjar.

refresh the joverseerupdaterjar and the test directory should appear at the same level as src.

compiling should have started.

assuming everything managed to compile...

you need to create a Run... configuration.

  • select joverseerjar in the project explorer.
  • right click, Run As... , Java Application,
  • select JOverseerJIDEClient for the instance of main() to run.

It will fail.

go back and Run As... but select Run Configurarions

on the second tab 'Arguments' under the panel VM Arguments add

--add-exports java.desktop/com.sun.java.swing.plaf.windows=ALL-UNNAMED --add-opens=java.desktop/sun.awt.shell=ALL-UNNAMED

now you should be able to Run jOverseer.