Hi everybody! I am still not sure, what is the best direction for me to solve the following task. Maybe someone on maillist implemented something similar, or knows the technology/approach, that can simplify things.
What ideally I want to achieve is: 1. Create a "lightweight" installator, that will not contain any maven artifacts (or, if not possible, contain all of them). 2. When end user launches the installator, it is asked for some input, which is saved as .property file. 3. Installator then fetches only the artifacts needed (selected by user + those which are obligatory), and replaces the property file(s) in those artifacts. Finally it creates ready to-use WAR package. If you have an example of above -- give me a link, please. That would be great! Right now I see the only way is to create a temporary maven project and after doing steps (1) and (2) launch maven to complete the packaging. Thanks in advance! Dmitry Katsubo wrote on 30/01/2010 16:34: > Hi all! > > Sorry, that my question seems to have been asked in maven user list > http://mail-archives.apache.org/mod_mbox/maven-users/200710.mbox/%3c2fbbcb49-65d3-4258-906f-e252372e9...@massol.net%3e > > but I have the situation, similar to that. I hope you can help me, as > you might know what are the latest approaches to that. > > I have some service, packaged as .WAR, which is completely build by > maven. However, this .WAR file requires customization: I need to package > it in different ways, depending on user input. Basically, user should > himself select the components, he would like to add to WAR, and define > some simple configuration for these components. After the packaging the > installer should optionally launch tomcat (or jetty) and start a WAR > application. > > I need to write the installer, that: > 1. Asks user for the list of components (=checkboxes) > 2. For each component, asks for the configuration options (then to be > saved as .property file) > 3. Package everything from steps 1 and 2 into WAR file. Dependences > should be fetched from publicly available maven repository. > 4. Optionally launch tomcat (or jetty) in a background > 5. Maybe execute some other script, depending on choices in 1 (like > "demo application"). > > Let me know, if there is a universal solution for that. > > Thanks in advance for any hint. > -- With best regards, Dmitry --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
