Am 2015-12-25 um 14:25 schrieb Robert Scholte:
Op Fri, 25 Dec 2015 13:09:26 +0100 schreef Michael Osipov
[...]
I would continue as instructed by our retirement plan, issue, final
release with notice. Moreover, I would add warning log output to every
mojo that this plugin has been retired.
Since the last release there weren't any plugin specific issues fixed,
only some parent related commits were done.
And what is the benefit of adding such messages if there is nothing to
refer to? For those few still using the plugin it is just frustrating to
have extra logging even though the plugin does its job fine.
Only if there is someone who takes over the plugin, we should do so,
since eclipse:eclipse would pick up the wrong plugin if you don't
specify it with the new groupId in your pom.
IMHO an announcement should be good enough to inform everybody.
That makes sense. An empty release might cause confusion in the community.
Am 2015-12-25 um 12:41 schrieb Robert Scholte:
Hi Michael,
it was half forgotten, half intended. My original idea was to donate it
to MojoHaus and once they made there first release we could do final
release here and refer to the the maintainers.
However, MojoHaus hasn't found someone to maintain it over there. Other
argument: sources are available, so if people want to apply patches, let
them fork it and fix it for themselves.
I've asked Brian if it was possible to make the MECLIPSE project
readonly. He responded that it should be possible but would require some
investigation to do so.
Summary of MECLIPSE[1] was already updated, as was the plugin-page[2].
I will update the page of the plugin and close all issues. Not sure what
to do with github.
thanks,
Robert
[1]
https://issues.apache.org/jira/browse/MECLIPSE/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel
[2] http://maven.apache.org/plugins/index.html
Op Thu, 24 Dec 2015 23:43:50 +0100 schreef Michael Osipov
<[email protected]>:
Hi Robert,
back in October the result of the retirement vote [1] was positive.
The plugin is still online without notice, issues are still open in
JIRA
and no repo is at GitHub.
Did you simply forget that?
Michael
[1] https://www.mail-archive.com/dev%40maven.apache.org/msg107104.html
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
