I ment I had tried this before. My conclutions was that outputDirectory alwas was located in target dir. I think I tested this for the assembly plugin, and it might be that there are a difference between these two.
-Ronny -----Opprinnelig melding----- Fra: dan tran [mailto:[EMAIL PROTECTED] Sendt: 19. september 2006 15:26 Til: Maven Users List Emne: Re: Make dependencies availible you can configure the outputDirectory to some where else http://mojo.codehaus.org/dependency-maven-plugin/copy-dependencies-mojo. html <outputDirectory>......</outputDirectory> On 9/19/06, Naess, Ronny <[EMAIL PROTECTED]> wrote: > > What I now have done is that I use dependency-maven-plugin (to be > changed) and runs the goal 'copy-dependencies'. Instead of push I now > use pull, meaning I have a script(ant) that pulls the dependencies > from my maven parent dir by copying all files to the BEA portal dir. > > This works fine and I think the resonsibility is more correct > conserning dependency. Maven should not have repsonsibility to update > its client and not the other way. > > To summarize: Maven copies all dependencyes to target/dependency for > all modules. A client ant script then copies all jars under target/ > using flatten=true to the BEA portal dir, giving me exactly what I want. > > The ideal way would been that maven put every dependeny to a "stage" > area, and that the client could reference this area as an dependency. > Bea Portal (v8.1) does not have this feature so it must be feed all > its dependencies. > > -Ronny > > -----Opprinnelig melding----- > Fra: dan tran [mailto:[EMAIL PROTECTED] > Sendt: 19. september 2006 14:39 > Til: Maven Users List > Emne: Re: Make dependencies availible > > This is a common pattern that fits nicely with dependency and assemly > plugins. > Here is the suggested structures. > > parent > pom.xml > module1 > module2 > ...... > assemby-module > > In the parent pom, define dependencyManagement section that all other > sub modules will share teh same dependency info. > > In you assembly-module, use dependency:copy to prepare a staging area > that assembly plugin can consume. > I would suggest to give maven-dependency-plugin a try, and file JIRA > if it does not work out for you. > dependency-maven-plugin at codehaus is EOL. > > -D > > > On 9/19/06, Naess, Ronny <[EMAIL PROTECTED]> wrote: > > > > Hi. > > > > Our project uses Maven2 to build some artifacts, and these artifacts > > and their dependensies must be availible for the client. The client > > is > > > BEA Portal. > > > > I want to fetch all my artifacts and their depencendies in one go! > > > > I have looked at both dependency-maven-plugin > > (maven-dependency-plugin > > > seems to fail on me?) and maven-assembly-plugin. > > > > My project is orginized with a master dir containing the parent pom, > > and all modules as subprojects. > > > > * Is the dependency plugin capable of handling modules (new in maven > 2)? > > If I have to configure every artifact I suppose it does not! > > * I have to first run copy goal to copy artifacts, then > > dependencies-copy. Also, will this have to be configured for each > > artifact or only in parent pom (I guess the previous question will > > answer this question)? > > * Also how do I override property <outputDirectory> to go outside > > basedir? I guess I always can post run an ant task but I would > > rather override it. > > > > > > Any help or tips is welcome. > > > > > > -Ronny > > > > -------------------------------------------------------------------- > > - 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] > > !DSPAM:450ff00792341367111490! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
