[
https://issues.apache.org/jira/browse/MCHECKSTYLE-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16304625#comment-16304625
]
Roman Ivanov edited comment on MCHECKSTYLE-346 at 12/27/17 3:57 PM:
--------------------------------------------------------------------
{quote} we're probably even in worse shape. {quote}
I do understand you. Just try to find compromise to avoid blocks.
{quote} I can think of several other solutions, but in the end it all depends
how much control you want over this plugin and if the current situation is
acceptable. {quote}
Please share your thoughts .... , we can provide fixes (migration for new
versions of checkstyle, as we are in full context of how to make it), but it
would be awesome for us to know when we can expect release of such fixes.
We are completely understand that release will not be immediate, but at least
ones in few month, or any other trigger. I know that release process is not big
fun for engineers, and is postponed as much as possible, and .... . But
contributors will unlikely send you code if they know that release will take a
while, so fork is better for them or do any other workaround.
Please share your thought and thanks lot for cooperation.
was (Author: romani):
> we're probably even in worse shape.
I do understand you. Just try to find compromise to avoid blocks.
> I can think of several other solutions, but in the end it all depends how
> much control you want over this plugin and if the current situation is
> acceptable.
Please share your thoughts .... , we can provide fixes (migration for new
versions of checkstyle, as we are in full context of how to make it), but it
would be awesome for us to know when we can expect release of such fixes.
We are completely understand that release will not be immediate, but at least
ones in few month, or any other trigger. I know that release process is not big
fun for engineers, and is postponed as much as possible, and .... . But
contributors will unlikely send you code if they know that release will take a
while, so fork is better for them or do any other workaround.
Please share your thought and thanks lot for cooperation.
> Release a new version
> ---------------------
>
> Key: MCHECKSTYLE-346
> URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-346
> Project: Maven Checkstyle Plugin
> Issue Type: Bug
> Affects Versions: 2.17
> Environment: All
> Reporter: richard
> Priority: Blocker
>
> Hello,
> Since my posts in another issue have gone unnoticed
> (https://issues.apache.org/jira/browse/MCHECKSTYLE-332), I am creating this
> one to bring it up front.
> The main checkstyle community have been waiting years for a 2.18 release for
> fixes and functionality needed. As it is now, we cannot remove old deprecated
> code from our utility as the plugin relies on them too much and breaks if
> they are removed which forces us to continue supporting them just for you.
> See Issue: https://github.com/checkstyle/checkstyle/issues/2883
> The last release for maven checkstyle plugin was 2015, but you continue to
> update the code base. Why is this? Is there something that prevents you from
> creating a new release? Do you lack personnel of some kind? Is it possible to
> give us a time table for a 2.18 release?
> If things continue as they are now, we may begin looking into breaking
> compatibility with the plugin in newer versions as this project seems to have
> run stagnant and is lacking support. If compatibility is broken, the current
> plugin released will then only work with old and outdated versions. I, and I
> am sure the community, don't wish to see this happen but the checkstyle
> utility needs to keep evolving and remove outdated code.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
