maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roman Ivanov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MCHECKSTYLE-346) Release a new version
Date Wed, 27 Dec 2017 16:19:00 GMT

    [ https://issues.apache.org/jira/browse/MCHECKSTYLE-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16304642#comment-16304642
] 

Roman Ivanov commented on MCHECKSTYLE-346:
------------------------------------------

It might be off topic here, 
but it would be awesome to upgrade checkstyleVersion to 7.X release but this will require
upgrade of plugin to jdk8 , as it major update for Checkstyle http://checkstyle.sourceforge.net/releasenotes.html#Release_7.0
.
can you help us to upgrade to jdk8 parent poms and ..... , we will contribute all other checkstyle
related update, I could create separate issue on this if you agree to help.

> 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)

Mime
View raw message