[ http://jira.codehaus.org/browse/MPANNOUNCEMENT-19?page=comments#action_50310 ]
Felipe Leme commented on MPANNOUNCEMENT-19: ------------------------------------------- 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.... > Failing when the version is missing should be optional > ------------------------------------------------------ > > Key: MPANNOUNCEMENT-19 > URL: http://jira.codehaus.org/browse/MPANNOUNCEMENT-19 > Project: maven-announcement-plugin > Type: Improvement > Versions: 1.3 > Reporter: Felipe Leme > Assignee: Felipe Leme > Fix For: 1.4 > > Original Estimate: 1 hour > Remaining: 1 hour > > 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). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
