Make plugin discovery reactor aware

Details

  • Type: New Feature New Feature
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 2.0-beta-2
  • Component/s: Plugins and Lifecycle
  • Labels:
    None
  • Complexity:
    Expert

Description

If plugin discovery is reactor aware, plugins that are part of a reactor build and are used to aid the build
can be used in one go. Else first the plugin should be installed, and then the rest of the project can
be built.

But mainly this aids in integration testing for plugins: the maven-it-plugin in sandbox can't add the current plugin
+ artifact to the lifecycle without making some methods public. If the plugin were to be discovered using the reactor,
those methods can remain private.

  1. File
    MNG-870.diff
    04/Oct/06 6:54 AM
    0.7 kB
    Vincent Siveton

Issue Links

is duplicated by

Bug - A problem which impairs or prevents the functions of the product. MNG-1883 it plugin not picking up the plugin being built (goes to the local repo instead)

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Bug - A problem which impairs or prevents the functions of the product. MNG-2677 Plugin discovery not reactor aware

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
is related to

Improvement - An improvement or enhancement to an existing feature or task. MNG-249 compile and package should be reactor-aware

  • Critical - Crashes, loss of data, severe memory leak.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
relates to

Bug - A problem which impairs or prevents the functions of the product. MNG-2135 multi-project build that creates it's own plugins needs bootstrapping

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Brett Porter added a comment -

opening a new issue as I have not hooked in plugin's dependencies, reports, or extensions yet

Show
Brett Porter added a comment - opening a new issue as I have not hooked in plugin's dependencies, reports, or extensions yet
Hide
Permalink
Vincent Siveton added a comment -

The it test (it0042) which should be succeeded

Show
Vincent Siveton added a comment - The it test (it0042) which should be succeeded
Hide
Permalink
Kenney Westerhof added a comment -

It fails currently. Another IT test probably installed a test:test-plugin (81?); after making the artifactId unique (it0042-test-plugin) it fails.

Show
Kenney Westerhof added a comment - It fails currently. Another IT test probably installed a test:test-plugin (81?); after making the artifactId unique (it0042-test-plugin) it fails.
Hide
Permalink
Kenney Westerhof added a comment -

It's affected by this: it0042, it0096 and it0097.

Show
Kenney Westerhof added a comment - It's affected by this: it0042, it0096 and it0097.
Hide
Permalink
Brett Porter added a comment -

you can't reopen stuff fixed in the past without upsetting JIRA. If it's a regression, please open a new ticket.

Show
Brett Porter added a comment - you can't reopen stuff fixed in the past without upsetting JIRA. If it's a regression, please open a new ticket.
Hide
Permalink
Kenney Westerhof added a comment -

Hm, stupid jira..

I've created a new issue at MNG-2677.

Show
Kenney Westerhof added a comment - Hm, stupid jira.. I've created a new issue at MNG-2677.

People

  • Assignee:
    Brett Porter
    Reporter:
    Kenney Westerhof
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:

Time Tracking

Estimated:
1h
Original Estimate - 1 hour
Remaining:
0m
Remaining Estimate - 0 minutes
Logged:
1h
Time Spent - 1 hour