If needed, to copy all the dependencies, in m1 there's a tag :
maven:copy-deps

Arnaud


On 1/3/06, Man-Chi Leung <[EMAIL PROTECTED]> wrote:
>
> hi
>
> for m2 , I am doing this configuration to copy *.jar to my target
> directory as well as  tar to my assembled file.
>
> /pom.xml
> </plugins>
> <!-- this will package all dependencies to your target/lib. command:
> mvn package-->
> <plugin>
>                <groupId>org.codehaus.mojo</groupId>
>                <artifactId>dependency-maven-plugin</artifactId>
>                <executions>
>                        <execution>
>                                <id>copy-dependencies</id>
>                                <phase>package</phase>
>                                <goals>
>                                        <goal>copy-dependencies</goal>
>                                </goals>
>                                <configuration>
>                                        <outputDirectory>${
> project.build.directory}/lib</outputDirectory>
>                                </configuration>
>                        </execution>
>                </executions>
>        </plugin>
> <!-- this will copy all dependencies to your assembled tar.gz.
> command:  mvn assembly:assembly -->
>                <plugin>
>                        <artifactId>maven-assembly-plugin</artifactId>
>                        <configuration>
>
> <descriptor>src/main/assembly/bin.xml</descriptor>
>                        </configuration>
>                </plugin>
> </plugins>
>
> /src/main/assembly/bin.xml
> <assembly>
>   <id>bin</id>
>   <formats>
>     <format>tar.gz</format>
>   </formats>
>   <fileSets>
>     <fileSet>
>       <includes>
>         <include>README*</include>
>         <include>bin/run.sh*</include>
>       </includes>
>     </fileSet>
>     <fileSet>
>       <directory>target</directory>
>       <outputDirectory></outputDirectory>
>       <includes>
>         <include>*.jar</include>
>       </includes>
>     </fileSet>
>     <fileSet>
>       <directory>target/lib</directory>
>       <outputDirectory>lib</outputDirectory>
>       <includes>
>         <include>*.jar</include>
>       </includes>
>     </fileSet>
>   </fileSets>
> </assembly>
>
>
>
> > Yeah, I missed the obvious first sentence, sorry.
> >
> > -----Original Message-----
> > From: Arnaud HERITIER [mailto:[EMAIL PROTECTED]
> > Sent: Monday, January 02, 2006 6:47 PM
> > To: Maven Users List
> > Subject: Re: Copy Jar?
> >
> > Hi Brian, this tip is only for m2.
> >
> > Arnaud
> >
> > On 1/2/06, Brian E. Fox <[EMAIL PROTECTED]> wrote:
> >>
> >> Take a look at the dependency-maven-plugin at mojo
> >> http://mojo.codehaus.org/dependency-maven-plugin. After building and
> >> installing, this plugin could execute and copy it where ever you
> >> like.
> >> It expects the artifact to be in the local or remote repository
> >> but if
> >
> >> you execute it in the install phase, it should already be in your
> >> local repo by the time the plugin executes.
> >>
> >> -----Original Message-----
> >> From: Davis Ford [mailto:[EMAIL PROTECTED]
> >> Sent: Monday, January 02, 2006 9:53 AM
> >> To: users@maven.apache.org
> >> Subject: Copy Jar?
> >>
> >> Hi, I'm using Maven 1.0.2 to build my jar.  The jar is used as
> >> part of
> >
> >> a different project called GeoServer that uses Jetty.
> >>
> >> Every time I build my jar, I need to manually copy it to
> >> $someDir$/geoserver/server/WEB-INF/lib/ in order to test my changes.
> >> I don't rebuild GeoServer software everytime...I only rebuild my jar
> >> that I run inside GeoServer.  What is the best way for me to add a
> >> target or over-ride a plugin property to copy my jar to this
> > directory?
> >>
> >> I looked at jar:install, but if I think if I over-ride that, then my
> >> jar dependencies will get screwed up as it won't point to my
> >> .maven/repository anymore.
> >>
> >> I looked at distribution plugin, but it doesn't seem to have any
> >> documentation.
> >>
> >> I'm not that swift yet with Jelly, but is there a maven.xml example
> >> somewhere that does this?  Also, different developers have installed
> >> GeoServer in different directories on their machines.  This means
> >> somehow, whatever solution I create has to be able to accomodate this
> >> discrepancy.  Environment variable?
> >>
> >> Regards,
> >> Davis
> >>
> >> ---------------------------------------------------------------------
> >> 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]
> >
>
>
>

Reply via email to