Open cristianbogdan opened 6 years ago
There are a few tools (JSP independent or not) that are actually needed at runtime, not during development. A solution is needed for those as well.
So how should this go then? Migrate the mak-tools to core?
Mak-tools currently do need a UI, and currently the only way makumba is supporting UI is through JSP
So how should this go then? Migrate the mak-tools to core?
My idea is to still keep makumba-core independent of servlets or other UI. In that sense the solution is a separate project (mak-tools.jar). That also gives the option of deploying makumba-jsp without tools (e.g. in production)
Mak-tools currently do need a UI,
Yes but they use servlets to create UI, they don't use JSP.
The makumba developer support is currently part of the jsp package
It makes sense to look at (or run) queries and look at mdds without using JSP.
The JSP-specific tools can stay in makumba-jsp.jar