Details
-
Type:
Bug
-
Status:
Open
-
Priority:
Critical
-
Resolution: Unresolved
-
Affects Version/s: 1.0-alpha-1
-
Fix Version/s: 1.0-alpha-4
-
Component/s: Install
-
Labels:None
Description
The install goal seems only to be taking the already built jar and installing it with the "testing" version into the repo. The plugins contain metadata that has the version. If this version is not also updated to "testing" then bad things can happen. Specifically the plugin isn't found and default phases aren't used when running tests under 2.1.
We had a similar problem with the plugin-testing-harness that corrupted the default artifact with "test" and thus screwed people up at runtime. More info is here: MECLIPSE-239
Issue Links
- is depended upon by
-
MRPM-80
Integration tests fail using maven 2.2.1
-
- is duplicated by
-
MSHITTY-33
Maven SHITTY Plugin fails when used with Maven 2.1.0 (Needs to update internal plugin metadata)
-
- is related to
-
MNG-3284
Cached plugins are used, even when the specifically declared
-
-
MNG-1323
Plugin extensions (dependencies) not resolved in reactor build
-
- relates to
-
MOJO-1359
-Pintegration-tests doesn't work on mvn 2.1.0
-
This is actually causing gmaven release:prepare builds to fail... so need to sort this out soon.