Maven 2 & 3

lazily resolve extensions

Details

  • Type: Improvement Improvement
  • Status: Open Open
  • Priority: Minor Minor
  • Resolution: Unresolved
  • Affects Version/s: None
  • Fix Version/s: 3.1
  • Component/s: Plugins and Lifecycle
  • Labels:
    None
  • Complexity:
    Expert
  • Number of attachments :
    0

Description

try and resolve extensions only when they might be required. Currently, even clean:clean would resolve an extension for the project (not that projects will often have an extension, but this is still undesirable, especially if it is a snapshot).

Issue Links

This issue relates to:
MNG-1911 Building plugins with extensions in a reactor fails Critical Open

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Jason van Zyl added a comment -

By this do you mean looking at something like an SCM url, or a distributionManagement url and pulling in the right extension?

Show
Jason van Zyl added a comment - By this do you mean looking at something like an SCM url, or a distributionManagement url and pulling in the right extension?
Hide
Permalink
Brett Porter added a comment -

no, this is just a matter of reviewing how extensions are loaded into the core, and if there is any way to ensure they are only resolved/loaded when they'll actually be needed (in the same way dependencies are). It's annoying to have to resolve them to do "clean" for example.

I wouldn't say this is major at all.

Show
Brett Porter added a comment - no, this is just a matter of reviewing how extensions are loaded into the core, and if there is any way to ensure they are only resolved/loaded when they'll actually be needed (in the same way dependencies are). It's annoying to have to resolve them to do "clean" for example. I wouldn't say this is major at all.
Hide
Permalink
Brett Porter added a comment -

this crosses the current thread on dev@ about abolishing extensions

Show
Brett Porter added a comment - this crosses the current thread on dev@ about abolishing extensions
Hide
Permalink
Brett Porter added a comment -

given extensions are still supported in 3.0, will put it in to review in 3.1 when some of the deprecated functionality gets removed

Show
Brett Porter added a comment - given extensions are still supported in 3.0, will put it in to review in 3.1 when some of the deprecated functionality gets removed

People

Vote (1)
Watch (3)

Dates

  • Created:
    Updated:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.