Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.6, 1.6.1
-
Fix Version/s: 1.6.1
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
The introduction of the maven.jdepend.components property causes a backwards compatibility problem. Our JDepend reports stop reporting on all packages with 1.6 and 1.6.1-SNAPSHOT; 1.5.1 works great.
1.6 introduces it and defaults to pom.project. To have the same behavior as 1.5.1 in 1.6 and 1.6.1-SNAPSHOT, the components property must be empty.
With the changes made by MPJDEPEND-7, the components property can be set to nothing (1.6 would crash if set to nothing).
I think the best answer is to default maven.jdepend.components to nothing, so upgrades are transparent (instead of having to set the property to nothing to get it to work - and other users spending a bunch of time as I did!) and more aligns with JDepend's components setting is optional.
Activity
| Field | Original Value | New Value |
|---|---|---|
| Resolution | Fixed [ 1 ] | |
| Fix Version/s | 1.6.1 [ 12368 ] | |
| Status | Open [ 1 ] | Closed [ 6 ] |