On Tue, Aug 4, 2009 at 6:57 PM, Alexander <the.malk...@gmail.com> wrote:
> You could declare these documentaion as dependecy. Then use dependency > plugin for unpacking this module. [?] > See > http://maven.apache.org/plugins/maven-dependency-plugin/unpack-mojo.html > > On Tue, Aug 4, 2009 at 8:39 PM, Brian Fox <bri...@infinity.nu> wrote: > > http://www.sonatype.com/people/2008/04/how-to-share-resources-across-projects-in-maven/ > > Well, this isn't quite a shared dependency. The documentation is only for this particular module and is irrelevant anywhere else. Do I need to have the techwriters zip up the documentation and download it into our Maven repository, and then when I do a build, download it, and unzip it? Is it possible to use the maven-dependency-plugin just to merely do the unzipping? Otherwise, I'll have to give our techwriters access to the repository, and let the developers know they have to coordinate the version numbering of the documentation in the pom.xml. Maybe I am better off just using the antrun mojo to do the unzipping during the packing phase. -- David Weintraub qazw...@gmail.com
