One problem I'm having is obtaining the initial template ZIP. I managed to deploy the template artifact, which is of type JAR. I don't care about the JAR, but it also deploys my ZIP. Apparently 'zip' isn't a valid package type.
Now I want to unpack that to use in another project. I want to use it as an overlay the same way WARs work, but that doesn't seem like an option here so I'm using the dependency plugin. It only grabs the JAR from the template though, not the assembled ZIP. Any ideas? On Tue, Jul 8, 2008 at 2:57 PM, Kallin Nagelberg <[EMAIL PROTECTED]> wrote: > Hi, > > I'm trying to build a simple distribution with the following layout: > > + > |---bin > |---libs > > There are some scripts in the bin folder that build a classpath using the > lib folder. It should be distributed as a ZIP. > > One caveat: Initially it is built as a template. That is, there is a core > artifact with all the basic libs/scripts required. Sub projects may wish to > add additional libraries/scripts. > > I've got some of this working using the assembly plugin, but I'm not sure > that's the right approach. > > Does anyone have suggestions as how this could be done smoothly? I noticed > for WARs it is easy to do this sort of templating due to the support of > 'overlays'. >
