You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jason van Zyl (JIRA)" <ji...@codehaus.org> on 2014/01/19 21:31:49 UTC

[jira] (MNG-5259) Mechanism to download POMs only

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

Jason van Zyl closed MNG-5259.
------------------------------

    Resolution: Won't Fix
    
> Mechanism to download POMs only
> -------------------------------
>
>                 Key: MNG-5259
>                 URL: https://jira.codehaus.org/browse/MNG-5259
>             Project: Maven 2 & 3
>          Issue Type: Improvement
>          Components: Dependencies
>    Affects Versions: 3.0.4
>         Environment: Any
>            Reporter: Peter Johnson
>            Priority: Minor
>         Attachments: patch_pomsonly.txt
>
>
> We often run various reports (e.g., dependency:tree) on a high-level POM that pulls in numerous artifacts at various levels in the dependency hierarchy. (Our highest-level POM defines a release of our product, it has dependencies that are OVAs (VM images), which in tern have dependencies that are typically installation packages (TAR.GZs, ZIps, MSIs, EXEs, ISOs), which in turn reference individual components (JARs, WARs, EXEs, DLLs, etc).) Some of our artifacts tend to be rather large (the OVAs are GBs in size), and since the reports need only the information in the POMs and not the artifacts themselves, we found it handy to add a "poms.only" flag to our report generation to prevent the artifacts from being downloaded from the remote repository. Thus we run:
> mvn dependency:tree -Dpoms.only
> Now our reports complete within a few minutes, rather than in a few hours.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira