2009/8/5 David Weintraub <qazw...@gmail.com>: > 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. >
Doesn't matter really, the process is still the same... > 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? > If they zip it and publish it to the repo yes...but they will probably do that using the assembly plugin like I showed in the blog... > 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. Yes, that's what the dependency plugin does, it either copies the file or unpacks it. > > Maybe I am better off just using the antrun mojo to do the unzipping during > the packing phase. > The dependency plugin does the same thing without ant. > -- > David Weintraub > qazw...@gmail.com > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
