you can using the "copy-dependencies" goal of the dependency plugin.
<project>
[...]
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-dependency-plugin</artifactId>
<executions>
<execution>
<id>copy-dependencies</id>
<phase>package</phase>
<goals>
<goal>copy-dependencies</goal>
</goals>
<configuration>
<!-- configure the plugin here -->
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
[...]
</project>
i used it in my project.
On Sat, Jan 30, 2010 at 2:03 PM, tbee <[email protected]> wrote:
>
>
>
> Alexander-129 wrote:
> >
> > You are defining this pom project as dependency in module? Right?
> >
>
> I have a series of POM + JARs uploaded to Nexus, e.g.
> - xxx-1.1.jar
> - xxx-skinA-1.1.jar
> - xxx-skinB-1.1.jar
> - xxx-skinC-1.1.jar
>
> This works fine. Now I want a "xxx-all:1.1" pom which will download the
> whole bunch above.
> In a project I indeed have a denpendency:
> ... <artifactId>xxx-all</artifactId><version>1.1</version>
>
> When resolving that project it tries to download "xxx-all-1.1.jar" and
> fails
> on a missing dependency.
>
>
>
> --
> View this message in context:
> http://old.nabble.com/pom-without-artifacts--tp27381618p27383258.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
--
Eyal Edri
