You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dennis Lundberg (JIRA)" <ji...@codehaus.org> on 2012/11/02 11:07:13 UTC
[jira] (MASSEMBLY-271) For repository assembly, include pom.xml
project plugins, as an option
[ https://jira.codehaus.org/browse/MASSEMBLY-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg updated MASSEMBLY-271:
--------------------------------------
Description:
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>
was:
One use case for creating a repository archive, like so:
<assembly>
<repositories>
<repository>
<outputDirectory>repository</outputDirectory>
<includeMetadata>true</includeMetadata>
</repository>
</repositories>
</assembly>
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>
Issue Type: New Feature (was: Bug)
> For repository assembly, include pom.xml project plugins, as an option
> ----------------------------------------------------------------------
>
> Key: MASSEMBLY-271
> URL: https://jira.codehaus.org/browse/MASSEMBLY-271
> Project: Maven 2.x 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira