[ 
http://jira.codehaus.org/browse/MASSEMBLY-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

John Casey updated MASSEMBLY-76:
--------------------------------

    Fix Version/s:     (was: 2.2)
                   2.2-beta-3

This is a documentation issue. Actually, the simplest way to solve the problem 
is to create a project to house your new assembly descriptor, where that 
descriptor might be called 'myassembly.xml'. It should live in the following 
directory structure within your assembly-descriptor project:

{noformat}
src/main/resources/assemblies/myassembly.xml
{noformat}

Then, you can build/release/deploy this project, and reference it from the 
projects in which you want to create an assembly of this new type, using:

{code:xml}
<plugin>
  <artifactId>maven-assembly-plugin</artifactId>
  <version>2.2-beta-2</version>
  <dependencies>
    <dependency>
      <groupId>your.group.id</groupId>
      <artifactId>my-assembly-descriptor</artifactId>
      <version>blah</version>
    </dependency>
  </dependencies>
  [...]
</plugin>
{code}

I just need to document this on the plugin website.

> [assembly plugin] improve or clarify inheriting/reusing descriptors
> -------------------------------------------------------------------
>
>                 Key: MASSEMBLY-76
>                 URL: http://jira.codehaus.org/browse/MASSEMBLY-76
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Improvement
>            Reporter: Jacob Robertson
>             Fix For: 2.2-beta-3
>
>
> I want to declare a new reusable assembly descriptor.  Then, in my parent pom 
> I can reference that descriptor, and all children projects will be able to do 
> assembly:assembly without specifying the descriptor.  This actually works 
> halfway, but then the assembly plugin can't find the descriptor - because it 
> doesn't live inside of the child project.  I was trying to play around with 
> putting the descriptor in the parent project, but since the packaging has to 
> be "pom" that of course wouldn't work.
> Unless I misunderstand, the way this currently works, I'd have to declare the 
> descriptor for each and every child project.  Which would be very 
> unfortunate, since the 3 supplied predefined descriptors don't meet my needs.
> If there is a way to do this, then the improvement request is to improve the 
> documentation for this since I couldn't figure it out...

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to