Hi,

We have a  parent POM that has the following configuration inside the
<build/> section (NOT pluginManagement):

----------------SNIP-----------------
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-assembly-plugin</artifactId>
        <version>2.2-beta-5</version>
        <configuration>
          <descriptors>
            <descriptor>assembly.xml</descriptor>
          </descriptors>
          <outputDirectory>target</outputDirectory>
          <workDirectory>target/assembly_work</workDirectory>
          <finalName>${artifactId}-${version}</finalName>
        </configuration>
      </plugin>
----------------SNIP-----------------

A child project  wants to use one of the build-in descriptors instead:

----------------SNIP-----------------
      <plugin>
        <artifactId>maven-assembly-plugin</artifactId>
        <configuration>
          <descriptorRefs>
            <descriptorRef>jar-with-dependencies</descriptorRef>
          </descriptorRefs>
          <descriptors/>        
        </configuration>
      </plugin>
----------------SNIP-----------------

Somehow the plugin still picks up the inherited <descriptors/> element
and always complains about a missing "assembly.xml" file.

Is there a way to unset the inherited descriptor ? I remember just using
an empty element instead worked for other plugins (but the property
wasn't a collection type so maybe that's the cause of this bug).

Regards,

Tobias

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to