Closed adamkewley closed 6 years ago
This relates to #22 - if I'm going to restructure the project into a multimodule maven thing I mayaswell also deal with the naming problem.
This is scheduled as part of the 1.0.0
build, and will be discussed on the main 1.0.0
ticket.
Whenever I talk to end-users about Jobson, they think Jobson is the UI (and the server), and it's annoying to explain that, no, Jobson's "just" the webserver, and the UI is installed separately.
So, to get around that, I'm going to move the contents of this jobson project into a "jobson-webserver" or "jobsond" project and make this project a top-level integration of Jobson + JobsonUI so, when end-users install this, they get what they expect (Jobson with the UI, because that's the advertised version of Jobson).
This will involve breaking changes to the project structure, but the ultimate goal is to have the resulting integration project expose a
jobson
command-line that's exactly the same as the existingjobson
CLI - just that it exposes a full Jobson+UI stack instead of only exposing the webserver.