I've started working on this but ran into a bit of a problem. The plugin I need to write would want to use the functionality in the changes plugin. However, the changes plugin doesn't separate the actual logic into a separate jar so it is difficult to make use of it from another plugin. Is there any reason I can't refactor the changes plugin into 2 subprojects?
Ralph On Dec 21, 2010, at 8:46 PM, Stephen Connolly wrote: > The scm api supports both add and remove. I think you will need to add your > own plugin though, as the preparation goals and completion goals do not > provide a means to specify properties, and, more importantly, the property > includes is shared with a number of plugins, so you really only want scm:add > to be in its own fork of maven. If you write your own plugin, it can create > and add the release notes using one goal and remove the release notes using > an other goal without requiring properties to be set... Also looking at > m-scm-p it would not be too difficult to use the scm api from your plugin > > - Stephen > > --- > Sent from my Android phone, so random spelling mistakes, random nonsense > words and other nonsense are a direct result of using swype to type on the > screen > On 22 Dec 2010 04:14, "Ralph Goers" <[email protected]> wrote: --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
