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 ther
On Dec 22, 2010, at 1:16 PM, Dennis Lundberg wrote:
> On 2010-12-22 22:09, Ralph Goers wrote:
>>
>> On Dec 22, 2010, at 12:58 PM, Dennis Lundberg wrote:
>>
>>> On 2010-12-22 20:31, Ralph Goers wrote:
My thought was to
a) enhance the release plugin to invoked the changes plugin and the
On 2010-12-22 22:09, Ralph Goers wrote:
>
> On Dec 22, 2010, at 12:58 PM, Dennis Lundberg wrote:
>
>> On 2010-12-22 20:31, Ralph Goers wrote:
>>> My thought was to
>>> a) enhance the release plugin to invoked the changes plugin and then commit
>>> the release notes before tagging and then remove
On Dec 22, 2010, at 12:58 PM, Dennis Lundberg wrote:
> On 2010-12-22 20:31, Ralph Goers wrote:
>> My thought was to
>> a) enhance the release plugin to invoked the changes plugin and then commit
>> the release notes before tagging and then remove then after
>> b) enhance the changes plugin to ha
On 2010-12-22 20:31, Ralph Goers wrote:
> My thought was to
> a) enhance the release plugin to invoked the changes plugin and then commit
> the release notes before tagging and then remove then after
> b) enhance the changes plugin to have goals to commit and delete the release
> notes.
> or c) c
I'd favour b or c. Don't add complexity to m-release-p
- 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 19:32, "Ralph Goers" wrote:
> My thought was to
> a) enha
My thought was to
a) enhance the release plugin to invoked the changes plugin and then commit the
release notes before tagging and then remove then after
b) enhance the changes plugin to have goals to commit and delete the release
notes.
or c) create a new plugin to do this.
I'm already able to
Hello,
changes.xml for changes plugin is included ?
Can we play with this to include a generated text release notes ?
Could me more easy (I remember stuff in m1 which updated the changes.xml).
--
Olivier
2010/12/22 Ralph Goers :
> Apache Commons has a policy (which is in alignment with
> http:/
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
Ok, but I don't see a delete operation in the scm plugin. Any idea on how to
do the removal without that?
OTOH, my first instinct was to think that the release plugin should be able to
generate the release notes on its own.
Ralph
On Dec 21, 2010, at 7:57 PM, Stephen Connolly wrote:
> The nex
The next release of the release plugin will have the completionGoals
parameter which you will want to hook in the remove of the release notes
- 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
Apache Commons has a policy (which is in alignment with
http://incubator.apache.org/guides/releasemanagement.html#best-practice) to
include release notes in the source distribution. I would like to generate the
release notes using the changes plugin during release:prepare and have them
committe
12 matches
Mail list logo
