On Thu, 27 Oct 2022 at 22:46, Gary Gregory wrote:
>
> Would you mind creating a ticket for the proper Maven plugin?
https://issues.apache.org/jira/browse/MCHANGES-413
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
Would you mind creating a ticket for the proper Maven plugin?
Gary
On Wed, Oct 26, 2022, 12:58 Eric Bresie wrote:
> Looking on the plug-in side (1) if this hasn’t changed any and I’m reading
> it correctly, seems like the json Node in use has no displayName or name
> attributes present.
>
>
Thanks Alex!
Gary
On Thu, Oct 27, 2022, 08:39 Alex Herbert wrote:
> On Thu, 27 Oct 2022 at 12:36, Alex Herbert
> wrote:
> >
> > I have reopened the tickets, removed the P2 priority field (just in case
> it was also contributing to the problem), assigned the priority as minor
> and closed the
On Thu, 27 Oct 2022 at 12:36, Alex Herbert wrote:
>
> I have reopened the tickets, removed the P2 priority field (just in case it
> was also contributing to the problem), assigned the priority as minor and
> closed the tickets.
>
> The Jira report is now fixed.
Strangely it was not fixed in
I have reopened the tickets, removed the P2 priority field (just in case it
was also contributing to the problem), assigned the priority as minor and
closed the tickets.
The Jira report is now fixed.
Alex
On Thu, 27 Oct 2022 at 09:26, Alex Herbert wrote:
> Hi Eric,
>
> Thanks for the tip
Hi Eric,
Thanks for the tip for investigating the jira report. I got the latest
source code for the changes plugin and printed out the offending nodes
that have no priority (issue id, key):
Missing priority 12619331: BCEL-165
Missing priority 12619323: BCEL-157
Missing priority 12619318:
Looking on the plug-in side (1) if this hasn’t changed any and I’m reading
it correctly, seems like the json Node in use has no displayName or name
attributes present.
Reference
(1)
