Hi, I am trying to create an assembly that I can deploy to our internal repository.
The envisaged steps in this process are: 1) Get all of the dependencies. 2) Do some final packaging; e.g. consolidate all SQL creation scripts into a single script. 3) Create a zip file ready for deployment. I'm trying to work out the best way of structuring the module responsible for doing this. Can I do it all in a single module, by binding different plugins to the appropriately sequenced phase? e.g. 1) Use maven-assembly-plugin bound to compile to create a temporary working directory of all of the dependencies. 2) Use maven-antrun-plugin bound to test to do the final packaging. 3) Use the maven-assembly-plugin bound to package to create a zip file. Does this sound reasonable / feasible, should I be looking at multiple modules straight away or some other approach? Cheers, James --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
