[
https://issues.apache.org/jira/browse/MASSEMBLY-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MASSEMBLY-369.
------------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period
of time. If you think this issue still persists, retest your problem with the
most recent version of Maven and the affected component, reopen and post your
results.
> Assembly plugin process it's commands from it's pom (in addition to an
> external file)
> -------------------------------------------------------------------------------------
>
> Key: MASSEMBLY-369
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-369
> Project: Maven Assembly Plugin
> Issue Type: New Feature
> Environment: N/A
> Reporter: Chris Graham
>
> Currently the plugin requires an external file to get it's configuration from.
> Can we simply not have this expressed inside the pom itself?
> What we currently have:
> {code:xml}
> <plugin>
> <artifactId>maven-assembly-plugin</artifactId>
> <configuration>
> <descriptors>
> <descriptor>assembly.xml</descriptor>
> </descriptors>
> </configuration>
> <executions>
> <execution>
> <id>make-assembly</id>
> <phase>package</phase>
> <goals>
> <goal>attached</goal>
> </goals>
> </execution>
> </executions>
> </plugin>
> {code}
> and assembly.xml:
> {code:xml}
> <assembly>
> <id></id>
> <formats>
> <format>zip</format>
> </formats>
> <includeBaseDirectory>false</includeBaseDirectory>
> <dependencySets>
> <dependencySet>
> <outputDirectory></outputDirectory>
> <outputFileNameMapping></outputFileNameMapping>
> <unpack>true</unpack>
> <unpackOptions>
> <includes>
> <include>*.jar</include>
> </includes>
> </unpackOptions>
> <scope>runtime</scope>
> </dependencySet>
> </dependencySets>
> </assembly>
> {code}
> What I'd like:
> {code:xml}
> <plugin>
> <artifactId>maven-assembly-plugin</artifactId>
> <configuration>
> <assembly>
> <id></id>
> <formats>
> <format>zip</format>
> </formats>
> <includeBaseDirectory>false</includeBaseDirectory>
> <dependencySets>
> <dependencySet>
> <outputDirectory></outputDirectory>
>
> <outputFileNameMapping></outputFileNameMapping>
> <unpack>true</unpack>
> <unpackOptions>
> <includes>
> <include>*.jar</include>
> </includes>
> </unpackOptions>
> <scope>runtime</scope>
> </dependencySet>
> </dependencySets>
> </assembly>
> </configuration>
> <executions>
> <execution>
> <id>make-assembly</id>
> <phase>package</phase>
> <goals>
> <goal>attached</goal>
> </goals>
> </execution>
> </executions>
> </plugin>
> {code}
> I do find it strange that it is a plugin that does *not* take it's input from
> a pom.
> Even a managed artifact would be fine (put assembly.xml in a resource jar and
> list it as a dependency - that would also work for me).
> -Chris
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
