Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.3
-
Fix Version/s: 1.4
-
Component/s: None
-
Labels:None
-
Testcase included:yes
-
Number of attachments :
Description
The announcement goal fails if the current version is not added on the <versions> element. Although this is nice, sometimes it might not be convenient (for instance, you might have a project made of several sub-projects and you would want to run the announcement on each sub-project using multi-project).
So, we should add a new property, like maven.announcement.versions.ignore, whose default value is false (to keep backwards compatibility).
On a second thought, there are more places where those restrictions should be ignored - for instance, if the project does not have a changes.xml. So, we better add a generic maven.announcement.lenient property instead....