[jbosstools-issues] [JBoss JIRA] (JBIDE-10803) Installation of central only installs part of astools, servers cannot start

[ https://issues.jboss.org/browse/JBIDE-10803?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-10803: ------------------------------------- It seems to me that downstream components need to know themselves if they want a full installation of their upstreams, or the minimum required to get compilation needed. I had a similar issue when RSE features needed wtp plugins, but I did not want to force a complete installation of all of RSE, since there was a mimimum set needed for compilation. I chose only the plugins I needed for compilation, and then users complained they could not actually USE rse at all, since the core APIs were there, but absolutely none of the impl. Clearly I had to expand my list so that RSE was at least usable, but I still did not choose to force-include the entire rse suite. I chose a further addition of plugins that made RSE usable at a minimum. It would seem to me that examples and central need to decide if they want their users to get a full installation of astools, or the bare minimum needed for compilation, or, some subset they manually declare as dependencies. If they want only compilation dependencies, then issues like this (where servers do not start) become the responsibility of their teams to tell the users to get the full astools installation. Or, if they prefer, they can open a bug against ASTools for better error messaging in this situation. If they want to manually declare their deps they can do that also. Or, of course, they can depend on the main feature and require a pulling in of everything astools. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira