That might be useful, but it sounds like a launcher rather than an installer (certainly part of an installer though). Most launchers you might want to use already do something like that, or instance the Wrapper config specifies the classpath for it. Also, isn't that the same type of functionality the ClassWorlds has (being able to manager/load classes from a local/remote location)?
Most of the jobs I've done are web based but I've done about 3 that were applications. All the applications had the early requirement that they could not load resources from outside the customers network. There are various reasons for that, but primary among them is that those networks are secure and an application that does anything that goes outside the customer network is suspect and harder to sell (imagine a bank discovering that some piece of software they are using loads application code from the internet). Few can get away with that, and even an application like Norton AntiVirus is suspect. I realize that a lot of the applications that use the installer plugin will be free and open but I personally would like a commercial grade solution. That doesn't mean that the ability wouldn't/shouldn't be there for the type of launcher your talking about, but it's not my focus unfortunately... - Brill Pappin > -----Original Message----- > From: Michael McCallum [mailto:[EMAIL PROTECTED] > Sent: December 3, 2006 4:07 PM > To: [email protected] > Subject: Re: [mojo-dev] On Appassembler features > > pomstrap could be used for the engine that launches the application > > strictly speaking you have no need to install much beyond a > pom.xml, a pomstrap jar and a batch/shell script to launch > it. It then uses standard > maven2 resolution to build up the class path and run the > defined class/application. > > you can bundle the pomstrap jar and the pom.xml into an executable jar > > You could even start with a seed repository if you wanted to > speed up the first start up process. > > > On Monday 04 December 2006 09:53, Brill Pappin wrote: > > How do you imagine it would work? > > I may have misunderstood what PomStrap does but it looks > like it might be > > used for updating an application? > > > > The goal (as far as I need anyway) is a repeatable installer build. > > The installer will not only have to deal with Maven but > native components > > as well. > > > > Think of the packaging you do with a tool like > InstallAnywere that produces > > an executable file that deploys an application on a machine. > > > > - Brill Pappin > > > > > -----Original Message----- > > > From: Michael McCallum [mailto:[EMAIL PROTECTED] > > > Sent: December 3, 2006 2:51 PM > > > To: [email protected] > > > Subject: Re: [mojo-dev] On Appassembler features > > > > > > Have you looked at pomstrap.... > > > > > > http://pomstrap.tigris.org > > > > > > On Monday 04 December 2006 06:19, Brill Pappin wrote: > > > > Sorry for the long post. I'm including the history in > the post so > > > > others can follow the discussion so far. > > > > [...] > > > > > > > --------------------------------------------------------------------- > > To unsubscribe from this list please visit: > > > > http://xircles.codehaus.org/manage_email > > -- > Michael McCallum > Associate > RHE & Associates > cell: 021.576.907 > phone: +64.9.377.8341 x 772 > skype: michaelamccallum > aim: gholamses > http://www.rhe.co.nz > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
