Ben,
What about having a release of checkstyle with all of the requested changes
and then update maven plugin and then release it?
Checkstyle maven plugin is just a wrapper over checkstyle library.
The best way would be that you (or anyone from Checkstyle) create a PR when
you are ready with the
Hi all,
The checkstyle team is waiting for my PR:
https://github.com/apache/maven-checkstyle-plugin/pull/18
The problem is, that they want to remove a method. If they do this too
early, maven users will not be able to update the checkstyle version
anymore.
Also, the maven Checkstyle plugin
do we really need a vote for this?
this seems to be overadministrativing :)
it's not a release or produce any artifacts so just do it
On Sun, 22 Dec 2019 at 00:18, Karl Heinz Marbaise wrote:
> I suggest to create a tag 3.6.3 in Integration Tests of Maven Core which
> preserves the state of the
The Apache Maven team is pleased to announce the release of the Apache Maven
Source Plugin, version 3.2.1
This plugin creates a jar archive of the source files of the current project.
https://maven.apache.org/plugins/maven-source-plugin/
You should specify the version in your project's plugin
Le samedi 21 décembre 2019, 19:22:42 CET Mark Struberg a écrit :
> To be honest, I didn't even know that there is a 'main project' with tons of
> git-submodules to emulate our old maven master build.
yes, I imagine, I did not make much noise about it :)
It's not about emulating an old master
+1
On Sat, Dec 21, 2019 at 9:18 AM Karl Heinz Marbaise wrote:
>
> I suggest to create a tag 3.6.3 in Integration Tests of Maven Core which
> preserves the state of the history and furthermore we should create a
> tag after each Maven Core release.
>
> Vote open for at least 72 hours.
>
> [ ] +1
