This is the ever lasting battle of modularity vs self containment. I remember when I decided to try out OS X for the first time for real, I was amazed and awed how simple the installation process of an application was - you just dropped an application onto your computer and it was "installed".
Contrasting this with Windows and/or Linux way of installing applications, the whole process seemed downright ... simple. Until I stopped to think what it meant that is. Most of the apps in OS X are self contained bundles (folders) of all the dependencies of that app. After being horrified for a moment at the horrible waste of space, I was awed again. Modularity is a great thing. In your application. And sometimes in service/OS level as well. But nothing beats the deployment of an app that can simply be "dropped in" to the container. So yeah - I see nothing special in deploying your app with all the dependencies bundled alongside. I'd even go one step further and bundle in the container (depending on the audience of the application of course). There are certainly examples of this type as well (think Jenkins from the top of my head) -- You received this message because you are subscribed to the Google Groups "Java Posse" group. To view this discussion on the web visit https://groups.google.com/d/msg/javaposse/-/NFwXklXEIuEJ. To post to this group, send email to javaposse@googlegroups.com. To unsubscribe from this group, send email to javaposse+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
