[ https://issues.apache.org/jira/browse/MASSEMBLY-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Karl Heinz Marbaise closed MASSEMBLY-271. ----------------------------------------- Resolution: Won't Fix > For repository assembly, include pom.xml project plugins, as an option > ---------------------------------------------------------------------- > > Key: MASSEMBLY-271 > URL: https://issues.apache.org/jira/browse/MASSEMBLY-271 > Project: Maven Assembly Plugin > Issue Type: New Feature > Affects Versions: 2.2-beta-1 > Reporter: Elias Ross > Priority: Major > > One use case for creating a repository archive, like so: > {code:xml} > <assembly> > <repositories> > <repository> > <outputDirectory>repository</outputDirectory> > <includeMetadata>true</includeMetadata> > </repository> > </repositories> > </assembly> > {code} > Is to allow the project pom to be runnable at a customer or remote site, > which does not have access to the central repository. Runnable, in the sense > that targets such as "exec:java" or the like can be called. > However, the repository archive does not include any plugins, especially > custom ones, that may be required to use a remotely deployed pom.xml. > I classified this as a "bug" since I feel without project plugins included, > the repository is not complete, but may be considered more of a "feature > request" instead. > A work-around is indicate custom plugins using <depend> -- This message was sent by Atlassian JIRA (v7.6.3#76005)