maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joël Royer (JIRA) <j...@codehaus.org>
Subject [jira] (MASSEMBLY-271) For repository assembly, include pom.xml project plugins, as an option
Date Fri, 20 Jun 2014 13:29:10 GMT

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

Joël Royer updated MASSEMBLY-271:
---------------------------------

    Comment: was deleted

(was: I've got the same problem.
I want to build a repository archive that allows my customer to build the projet without access
to the central repository.
Plugins described in the pom are not packaged.

Maven 3.0.5 / Maven Assembly Plugin 2.4)

> For repository assembly, include pom.xml project plugins, as an option
> ----------------------------------------------------------------------
>
>                 Key: MASSEMBLY-271
>                 URL: https://jira.codehaus.org/browse/MASSEMBLY-271
>             Project: Maven Assembly Plugin
>          Issue Type: New Feature
>    Affects Versions: 2.2-beta-1
>            Reporter: Elias Ross
>
> 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
(v6.1.6#6162)

Mime
View raw message