The patch to grant my wish.

Hi Shinobu,

Can't you just use a customized announcements.jsl instead?

My only concern with this type of improvement is that we will be add another property for just a specific part of the announcement. Why not on other parts as well?

Anyway, let's wait for Vincent's opinion.

– Felipe

PS: in case we decide to fix it, could you please provide a full patch, including modifications on xdocs/plugin.properties (explaining the new property), xdocs/changes.xml (with this new fix), project.xml (adding yourself as contributor), plugin.properties (setting the property and it's default value) and the changes itself (in this case, announcement.jsl)?

Hi Felipe,

Oops, I overlooked this guy:
maven.announcement.stylesheet.path

I guess I can live with that. I don't like copy and pasting, though.

1. And if you do decide to add the new property, sure I can make the full patch.

Best regards,
– Shinobu Kawai

I agree with you, a property is better than a full copy-and-paste. I'm just worried we would be 'bloating' the plugin with more properties (I already added a lot in the past issue

Anyway, let's wait for a third opinion (i.e., Vincente .

Hi,

The feature of choosing the group name is already implemented in the plugin. It is using the POM groupId name. I'd like to know why this is not enough and what is the rationale behind choosing another property for this.

Note: I'm not against it, I'd just like to better understand in other to offer the best possible design for this

Thanks

Hi Vincent,

This all came from my plugin devolpment, the Maven DocCheck Plugin.
http://maven-doccheck.sourceforge.net/

This plugin produces a report using Sun's Doc Check Doclet. The doclet itself is made in Sun. I thought the phrase "The doccheck team" could be taken to refer to the Sun team, whereas the plugin itself is by a different team (me!). In order to avoid confusion, I wanted to emphasize that the release was made by "The Maven-DocCheck team". Hence, the new property proposal.
http://maven-doccheck.sourceforge.net/announcements/announcement-1.4-0.1.txt

1. In retrospect, I guess I could have used "maven-doccheck-plugin" as my group id in the first place.

Best regards,
– Shinobu Kawai

Thanks for the details. What would you think if we change the template to use ${pom.name} instead?

It would say: "The ${pom.name} team ..."

Or simply "We are pleased to announce..." and sign with "-The development team"?

Hey, that'll be perfect!

Which one do you prefer:

1/ the use of ${pom.name}
or
2/ the use of "We are pleased..."
?

I like
1/ the use of ${pom.name}
better, but wouldn't complain if it were the other.

Done.