Not sure I see the use case in a standalone application. Seems far more failure-prone than just sucking it up and creating an uberjar.
For webapps, the Tomcat loader looks really compelling. AFAICT, you should be able to deploy/undeploy these contexts at runtime via JMX, which means you could use Maven for releases, then do an undeploy/deploy cycle pointing to the newly released artifacts in your Maven repository. Justin On 9/24/10 1:17 PM, Wayne Fay wrote: > Anyone here using PomStrap? I especially like the Tomcat loader > option, but haven't used it yet, just ran across it last night... > > http://pomstrap.jfluid.com/ > > ############ > PomStrap is a hierarchical Class-Loader based on the Maven's artifact > repository model. In a nutshell, it provides a runtime feature to > Maven. > > Maven manages the build of software modules, their documentation, > their reporting and the rationalized deployment and storage of the > resulting software artifacts. PomStrap is capable - in its simplest > form - of loading classes from software artifacts deployed to a Maven > repository. It can run embedded within any Java environment that > allows the use of custom class-loaders or as primary bootstrap > mechanism to run applications ranging from simple command-line > applications to complex dynamic enterprise applications. > > PomStrap can be configured to access software artifacts from a remote > Maven repository via HTTP. > ############ > > Wayne > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
