Brad, you can use a combination of assembly and dependency plugin to copy final built artfacts into a single directory the way you want it it and have assembly to zip( tgz, etc) them up.
Use a separate maven project for that purpose. -Dan On 9/5/06, Douglas Ferguson <[EMAIL PROTECTED]> wrote:
Can you define multiple source directories? I am guessing that transitive dependencies aren't getting linked in? D- -----Original Message----- From: Brad Harper Sent: Tuesday, September 05, 2006 12:25 PM To: users Subject: RE: directory v. outputDirectory The libraries will be built as a mixture of .lib and .dll files (on Windows) and .a and .so archives (on *nix platforms). Brad > -----Original Message----- > From: Douglas Ferguson > Sent: Tuesday, September 05, 2006 11:36 AM > To: users > Subject: RE: directory v. outputDirectory > > > What format must the archive be in? > > > > -----Original Message----- > From: Brad Harper > Sent: Tuesday, September 05, 2006 10:02 AM > To: users > Subject: RE: directory v. outputDirectory > > Dan: > > My intent is to have copies of a set of archive libraries collected > into a single directory. The libraries are sibling modules of a parent > project. > > Each library could be copied into the target area as it is built, or > the libraries could be copied (from their respective projects) by the > parent project in a roll-up operation. > > I considered running the assembly plugin in the parent project, > but the archive libraries cannot be in a .zip/.tar/.tgz format. > > Brad > > > -----Original Message----- > > From: dan tran [mailto:[EMAIL PROTECTED] > > Sent: Saturday, September 02, 2006 12:32 AM > > To: Maven Users List > > Subject: Re: directory v. outputDirectory > > > > > > native-maven-plugin''s outputDirectory purposely set to > > readonly so that all > > outputs ( .o, .dll, etc) stay inside > > target directory. and mvn clean can clear them as well. > > > > Why do you want the output files outside of project? > perhaps there is > > another way to accomplish > > what you need after the build. > > > > -D > > > > > > On 9/1/06, Brad Harper <[EMAIL PROTECTED]> wrote: > > > > > > > > > What's the difference between > > > > > > <build> > > > <directory> > > > <outputDirectory> > > > ... > > > > > > I'm using maven-native-plugin, which has identical configuration > > > elements, but I'm prevented from using them, i.e. > > > > > > <build> > > > <plugins> > > > <plugin> > > > <configure> > > > <directory> > > > <outputDirectory> > > > > > > by errors complaining about over-written read-only parameters. > > > > > > It would be OK if libraries (modules) were to build in their own > > > target/ sub-directories, but I'd like to move a copy of the > > resulting > > > libraries into a central location higher in the project hierarchy. > > > > > > Brad > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
