Migrate away from JSP - part 1

[markt-asf]

Part one (Jakarta EE 12) will consist of a global search and replace for JSP to Jakarta Pages (JSP)

[markt-asf]

There are somewhere around 6,600 uses of JSP. I think there are good reasons to retain some of those uses. So far the ones I've identified are:

• @since tags where the referenced spec is a Java EE spec version (JSP 2.2 and earlier)
• class names or parts thereof
• package names or parts thereof
• <body-content> in TLDs and similar
• URIs for schema identifiers

The assertion IDs I propose to change directly from JSP to PAGES.

For consistency with other specifications, I intend to use @since Pages (JSP) X.Y for @since tags (and drop the (JSP) in the next release).

There are likely others. The above is the result of a quick scan of search results. I'm expecting more to emerge as work progresses.

[joakime]

There are somewhere around 6,600 uses of JSP. I think there are good reasons to retain some of those uses. So far the ones I've identified are:

• @since tags where the referenced spec is a Java EE spec version (JSP 2.2 and earlier)

Agreed: 👍
But this would be a minimal impact change if we decided to do that.

• class names or parts thereof
• package names or parts thereof

Agreed: 👍
This level of change is out of scope, and would cause an undesired impact with implementers.

• <body-content> in TLDs and similar
• URIs for schema identifiers

Agree: 👍
We could introduce new ones with the new names, but we would have to leave the old ones unchanged.

The assertion IDs I propose to change directly from JSP to PAGES.

Agreed: 👍

For consistency with other specifications, I intend to use @since Pages (JSP) X.Y for @since tags (and drop the (JSP) in the next release).

Agreed 👍

There are likely others. The above is the result of a quick scan of search results. I'm expecting more to emerge as work progresses.

Thanks for digging deeper into this.