You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Erik Brakkee (JIRA)" <ji...@codehaus.org> on 2010/04/19 23:34:12 UTC

[jira] Created: (MNG-4636) Deploy minimal pom at release

Deploy minimal pom at release
-----------------------------

                 Key: MNG-4636
                 URL: http://jira.codehaus.org/browse/MNG-4636
             Project: Maven 2 & 3
          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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira