[
https://jira.codehaus.org/browse/MNG-4468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Benedict updated MNG-4468:
-------------------------------
Fix Version/s: (was: Issues to be reviewed for 3.x)
> Support lazy loading dependencies
> ---------------------------------
>
> Key: MNG-4468
> URL: https://jira.codehaus.org/browse/MNG-4468
> Project: Maven
> Issue Type: Improvement
> Components: Dependencies
> Affects Versions: 2.2.1
> Environment: All
> Reporter: redstun
>
> we have an auto-test project powered by maven, that has the ability to
> install our product on a testing environment and run the auto-test nightly.
> We have two major scenarios
> 1. we have the nightly test build server which executes all the auto-test and
> will activate the relevant profiles so that the product will be deployed as
> part of the test environment, which has dependency on artifacts of our
> products.
> 2. for each team member we can configure the auto-test to run against an
> external product server, to execute specific tests, instead of letting the
> auto-test build to deploy it's server every time we need to run a test. And
> we don't activate the profiles which will deploy our product to run the test.
> The problem is for team members is, although they don't need the product
> artifacts, they don't activate the relevant profiles, but the product
> artifacts are still being downloaded.
> Probably we should separate the dependencies into 2 categories,
> 1. the dependencies that need to be downloaded preemptively.
> 2. the dependencies that can be downloaded lazily, like lazy loading, they
> are downloaded only when the relevant goals are executed.
> Thanks
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
