[
http://jira.codehaus.org/browse/MASSEMBLY-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey closed MASSEMBLY-426.
--------------------------------
Resolution: Not A Bug
Assignee: John Casey
If your assemblies are in a plugin-level dependency, as described in:
http://maven.apache.org/plugins/maven-assembly-plugin/examples/sharing-descriptors.html
...then you need to use <descriptorRefs/> instead of <descriptors/>.
If, on the other hand you wish to use an assembly descriptor in your project
directory, you can use a relative path in the <descriptors/> section instead.
Both of these methods work well.
> Inconsistant inheritance
> ------------------------
>
> Key: MASSEMBLY-426
> URL: http://jira.codehaus.org/browse/MASSEMBLY-426
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-4
> Environment: mvn 2.0.9 jdk1.5
> Reporter: fabrice
> Assignee: John Casey
> Fix For: 2.2-beta-6
>
> Attachments: basedir.zip
>
>
> Hi
> A concret example is easy to understand :
> My superPom contains :
> <pluginManagement>
> <plugins>
> ...
> <plugin>
>
> <artifactId>maven-assembly-plugin</artifactId>
> <dependencies>
> <dependency>
>
> <groupId>com.almerys.assemblies</groupId>
> <artifactId>
>
> My-jar-assembly-descriptor
> </artifactId>
>
> <version>1.0.0.0.3</version>
> </dependency>
> </dependencies>
> <executions>
> <execution>
> <id>make-assembly</id>
> <phase>package</phase>
> <goals>
>
> <goal>single</goal>
> </goals>
> </execution>
> </executions>
> </plugin>
> ....
> </pluginManagement>
> And a child project overwritte the plugin conf to specify the assembly.xml
> that is placed in My-jar-assembly-descriptor. But In this way I can specify
> another assembly.xml that the default (in My-jar-assembly-descriptor)
> <plugin>
> <artifactId>maven-assembly-plugin</artifactId>
>
> <configuration>
> <descriptors>
> <descriptor>
> assembly.xml
> </descriptor>
> </descriptors>
> </configuration>
> </plugin>
> I have the error bellow :
> Reason: Error reading assemblies: Error locating assembly descriptor file:
> D:\workspace7.5\BatchAGLBPS\assembly.xml
> Ok but if in my child I add for exemple the version (anyone it does not
> matter) it works ! assembly plugin find the assembly.xml in my-jar-descriptor
> !
> <version>2.2-beta-2</version> for instance
> I do not understand is a bug ?
> Fabrice
> When I do a help:effective-pom I have my maven that say it uses 2.2-beta-1 in
> the pluginManagment section and 2.2-beta-2 in the child...
--
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
