Fix JavadocParagraph

[Pankraz76]

Fix JavadocParagraph

depends on:

• JavadocParagraph openrewrite/rewrite-static-analysis#545

enabler for

• https://checkstyle.org/checks/javadoc/javadocparagraph.html
• Fix JavadocParagraph maven#2302

ref

• Fix IllegalCatch #73

[Pankraz76]

is this any good? @gnodet

[gnodet]

Well, it will impact all maven projects, so it's really disruptive without any idea how much work it will require.

@slawekjaranowski ?

[Pankraz76]

all maven projects

this is by design then. We waiting for rewrite to deliver quick fix. @timtebeek

Might be doable with s&r as done in this PR.

• JavadocParagraph openrewrite/rewrite-static-analysis#545

This change will rollout instantly, right? So all have to migrate not just when going to latest version?

[timtebeek]

Good to have some wider context.. I'm traveling so can't pick up that recipe request for the coming weeks myself, but should be able to fit in a review.

[slawekjaranowski]

Well, it will impact all maven projects, so it's really disruptive without any idea how much work it will require.

@slawekjaranowski ?

Exactly we use shared configuration for all Maven project.
Version of shared is defined in Maven parent pom as property:

https://github.com/apache/maven-parent/blob/237aabdc41f90c7de15ebaafa27643ed80e5f4da/pom.xml#L972

So we can override it if really needed during parent upgrade.

We also use the same configuration for mojohaus projects:
https://github.com/mojohaus/mojo-parent/blob/979b051b927d24226bd78d0521c108feb29ee456/pom.xml#L309-L312

[Pankraz76]

disruptive

IDE can fix this.

Assuming this is out happy path and remaining violations are small better not existent.

Can we pull this change and then migrate, or will an merge apply instant and enforcing the new style?

[Pankraz76]

how is this being released, pull, or push?

On pull, we could merge and then try migration by IDE.