Hi Dave, We use maven to create an installer that gets deployed to our repo. When we want to install it somewhere we do:
wget http://my_repo/ebs/installer/MyInstaller-1.0.2.sh sh MyInstaller-1.0.2.sh In the past we used InstallShield, but for our apps it is overkill. Instead we use simple Pythion scripts. The way it works is that we have an "installer" directory next to our "java" directory. In the installer directory there must be a file called "install.sh" that kicks the pythn scripts off. In Maven1 we have a plugin that runs after the jar goal. It creates an assembly directory containing the subdirectories: bin, config, jars, and installer. The "jars" directories contains all of the jars the app depended on. The assembly directory is then zipped into a self extracting archive. When exectuted the archive uncompresses itself and runs the install.sh script. In Maven2 I think I can do this with the existing assembly plugin -- not sure, I have other non-maven problems preventing me from doing this. Regards, Christopher Helck -----Original Message----- From: Dave Rathnow [mailto:[EMAIL PROTECTED] Sent: Friday, September 21, 2007 11:48 AM To: Maven Users List Subject: General question about how to use Maven to build and deploy So I've now got Maven to build my jars, wars, and ears, it installs them in my local repository and deploys to my remote repositories. But what do I do now? In order to run and test my apps, I have to manualy copy files to the appropriate directories, which seems a bit primative for such a complex tool as Maven. The next step I'll have to figure out is how to build an install kit with Maven, which may not be that hard since everything is in the respository. Still, I'm wondering how others are using Maven in their development process? Do you us Maven to build and deploy your files and then have another script copy them to directories for testing/kit building? Thanks, Dave. ********************************************************************** This communication and all information (including, but not limited to, market prices/levels and data) contained therein (the "Information") is for informational purposes only, is confidential, may be legally privileged and is the intellectual property of ICAP plc and its affiliates ("ICAP") or third parties. No confidentiality or privilege is waived or lost by any mistransmission. The Information is not, and should not be construed as, an offer, bid or solicitation in relation to any financial instrument or as an official confirmation of any transaction. The Information is not warranted, including, but not limited, as to completeness, timeliness or accuracy and is subject to change without notice. ICAP assumes no liability for use or misuse of the Information. All representations and warranties are expressly disclaimed. The Information does not necessarily reflect the views of ICAP. Access to the Information by anyone else other than the recipient is unauthorized and any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it is prohibited. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify the sender. ********************************************************************** --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
