Yes, you can.
Take a look at:
maven-assembly-plugin (version 2.2-beta-2 i believe)
Define an assembly descriptor project as
<project>
<modelVersion>4.0.0</modelVersion>
<artifactId>your-artifact-id</artifactId>
<groupId>your-group_id</groupId>
<version>your-version</version>
<packaging>assembly-descriptor</packaging>
<build>
<extensions>
<extension>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-assembly-artifact-types</artifactId>
<version>2.2-beta-2</version>
</extension>
</extensions>
<plugins>
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
<version>2.2-beta-2</version>
</plugin>
</plugins>
</build>
</project>
And use it in other project like:
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
<executions>
<execution>
<id>do-assembly</id>
<goals>
<goal>attached</goal>
</goals>
</execution>
</executions>
<configuration>
<descriptors>
<descriptor>your-group-id:your-artifact-id:your-version</descriptor>
</descriptors>
</configuration>
</plugin>
Kind regards,
Wouter
Keith Bonawitz-2 wrote:
>
> Is there an easy way for a project to share an assembly descriptors
> with all projects that have it as a parent or as a dependency? I've
> tried various combinations of
> build-helper-maven-plugin:attach-artifact,
> maven-dependency-plugin:copy and
> maven-dependency-plugin:copy-dependencies, but I'm having trouble
> getting a working configuration. In particular,
> dependency:copy-dependencies does not seem to consider parent projects
> as dependencies, while dependency:copy fails if it attempts to copy
> the assembly descriptor from the same project that is being built.
>
> At a higher level, my goal is to have each of my maven projects
> produce an artifact that is an archive of the build setup for that
> project; e.g. it should contain everything in src/ as well as pom.xml
> and (to support eclipse) .project, .classpath, and .settings/ , such
> that someone could download and unzip this artifact and immediately do
> a mvn compile. In the long run, I hope to be able to use the
> maven-dependency-plugin:copy-dependencies to aggregate such artifacts
> for all of a given project's dependencies (or rather, all dependencies
> that came from my organization) so that I can produce a single
> artifact that has everything needed to completely recreate the portion
> of my organization's build environment that is implicated by a
> particular project.
>
> As far as I can tell, the assembly plugin is the correct way to
> produce such artifacts, but it will require a non-standard assembly
> descriptor, and it seems foolish to replicate this assembly descriptor
> in every project. Is there a better way?
>
> Thanks for your help!
> Keith
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/Sharing-assembly-descriptors-in-a-multi-project-setting-tp17121023p17124841.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]
