Charles, unless you are going to be sshing into the machine hosting the
server and doing your work directly on it, I believe you will need to at
least install the WMQ
get them connected just to be able to use the APIs, but I might be
wrong on that one.
As for your deployment issues, have you looked at something like
boxen http://boxen.github.com/, puppet http://puppetlabs.com/, or
Instead of packaging everything into a single executable installer, youd
essentially script an installation that could then set up your app on
clients machines. While there would be some time spent configuring your
scripts initially, what you want to do sounds like exactly the sort of
situation these tools were built for: repeatable, predictable automated
deployments into multiple environments .
As you say, there is no 1-click solution. Any app of enough complexity
with requirements that differ enough from usual conventions that tools
rawr or warbler arent working for you off the shelf, is going to need
significant customization and configuration in its build process. Tools
that offer enough flexibility to give said app the room to make those
configurations are going to either be too low level (rake, for
or too complex (maven) to truly be single-click. Youll either take
low-level tools and get the customized build process you need by
and scripting them to do what you want, or take a complex, high-level
tool and configure your build with some sort of config files, or command
line options, or whatever.
All that said, Im certain theres plenty of room for improvements in our
build tools, additional automation and better abstractions.
BTW, Ive mentioned it a couple times before, but the JavaFX packaging
tools (which can be used on any Java/Jruby app that needs native
installers, not just JavaFX/JRubyFX apps) will package the JRE along
the app. It becomes completely self-contained .deb or .rpm installers
linux, .dmg for osx, and exe or msi for windows.
On Fri, Oct 11, 2013 at 6:32 PM, Charles M. [email protected]