[
https://jira.codehaus.org/browse/MNG-4636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Benedict updated MNG-4636:
-------------------------------
Fix Version/s: (was: Issues to be reviewed for 3.x)
> Deploy minimal pom at release
> -----------------------------
>
> Key: MNG-4636
> URL: https://jira.codehaus.org/browse/MNG-4636
> Project: Maven
> Issue Type: Improvement
> Components: Artifacts and Repositories
> Affects Versions: 3.0-alpha-7
> Environment: All
> Reporter: Erik Brakkee
> Priority: Minor
>
> It would be good to filter poms when deploying them to a repository.
> A typical use case is where I want to exclude test dependencies and
> repository and plugin settings from a pom at deploy because they are not
> relevant for users. A current issue is where my productin code uses JPA 2.0
> and uses hibernate for testing. In this case, the hibernate (test) dependency
> is not essential and can be removed.
> Another example are repository settings which can point to, for instance,
> local proxies that have no meaning outside of the development environment.
> Implementing this feature means that it will be possible to use local
> repositories for efficiency, yet still deploy them to the central maven repo.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
