Ah sorry...
now I'm not able to read...
everything fine...
Kind regards
Karl Heinz Marbaise
On 15.12.19 22:58, Karl Heinz Marbaise wrote:
Hi,
to be honest I'm confused as well?
Have we decided to do a another 3.6.X release? Did I miss something?
Kind regards
Karl Heinz Marbaise
On
Hi,
to be honest I'm confused as well?
Have we decided to do a another 3.6.X release? Did I miss something?
Kind regards
Karl Heinz Marbaise
On 15.12.19 12:07, Elliotte Rusty Harold wrote:
I notice I'm confused. Wasn't Maven 3.6.0-3.6.3 already released?
On Sat, Dec 14, 2019 at 2:28 PM
Hi Jochen,
someone else was faster. It was closed yesterday after it was reported by
me. You can see the transitions in JIRA if you click on "all" or "activity"
next to the comments header.
Thanks for looking into this as well!
Ben
On Sun, 15 Dec 2019, 16:44 Jochen Wiedmann,
wrote:
> Hi,
Hi, Ben,
afaict, the issue *is* closed.
Jochen
On Sat, Dec 14, 2019 at 6:09 PM Benjamin Marwell wrote:
>
> Hi all,
>
> I think issue this can be closed:
>https://issues.apache.org/jira/browse/MCHECKSTYLE-373
> The original author is just asking for how to specify a property via
> command
@Elliotte
I am so sorry
I meant to send that email to d...@zookeeper.apache.org
Gmail autopletion changed that address
I apologize for the inconvenience
Enrico
Il giorno dom 15 dic 2019 alle ore 12:08 Elliotte Rusty Harold <
elh...@ibiblio.org> ha scritto:
> I notice I'm confused. Wasn't Maven
hi Elliotte,
I'm checking that on Infra Slack Channel...
If you like you could join also on Maven Slack Channel...
Kind regards
Karl Heinz Marbaise
On 15.12.19 12:46, Elliotte Rusty Harold wrote:
I have now reached:
Your request has been rate limited, as we have detected excessive
usage
I've closed a few issues that I'm reasonably confident were invalid or
fixed. I've also assigned to myself several RFEs I'd like to close as
Won't Fix, but where there might not be consensus.
I have now reached:
Your request has been rate limited, as we have detected excessive
usage from your IP
If it's necessary to maintain Maven 2.x or whatever old version,
that's what version control systems and branches provide. I strongly
prefer not to have work at head confused by tests that don;t run or
code that's commented out. In this case, refactorings at head such as
renaming a method could
Tentative +1.
Is there any reason we would ever backport a fix to 3.0 or 3.2? E.g.
this was the last release to support Java 1.6.
Or would we simply tell users to upgrade to 3.6.3?
On Sat, Dec 14, 2019 at 6:31 AM Karl Heinz Marbaise wrote:
>
> Hi,
>
> based on the history we have defined
I'm seeing a lot of forward progress on triaging bugs, especially in
Maven checkstyle. This is great! Thanks everyone.
Before I jump into the pool, are there any community rules, written or
otherwise, about procedures to follow when closing a bug or an RFE?
E.g. is it OK to make a unilateral
I notice I'm confused. Wasn't Maven 3.6.0-3.6.3 already released?
On Sat, Dec 14, 2019 at 2:28 PM Enrico Olivelli wrote:
>
> HI,
> I have moved to fixversion=3.7.0 all of the issues with fixversion = 3.6.0
> and resolution = empty.
>
> Please add the '3.6.0' label to the issues that should go
11 matches
Mail list logo
