Skip to content

[4.3.0] [m] Deprecate root jfieldvar - #176

Merged
phax merged 4 commits into
phax:masterfrom
glelouet:deprecate_jfieldvar
Sep 10, 2026
Merged

phax merged 4 commits into
phax:masterfrom
glelouet:deprecate_jfieldvar

Conversation

@glelouet

@glelouet glelouet commented Jul 23, 2026 •

Copy link
Copy Markdown
Collaborator

change minor (require new minor release)

depends (embarks) #175
closes #173

@glelouet glelouet added this to the 4.3.0 milestone Jul 23, 2026
@glelouet glelouet linked an issue Jul 23, 2026 that may be closed by this pull request
@glelouet
glelouet requested a review from phax July 23, 2026 18:23
@glelouet glelouet changed the title Deprecate root jfieldvar [4.3.0] [m] Deprecate root jfieldvar Jul 23, 2026
/**
* @return The owning class. Never <code>null</code>.
*/
@Deprecated(forRemoval = true, since = "4.3.0")

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, the method names should not be deprecated - effectively its only the constructor and the class.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lol, I deprecated the wrong one :P

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

actually it's save actions that added deprecated on all public methods. crahp.

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I assumed this. If possible try to turn off that specific save action

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I did it, as you can see the cleanup was changed to have it removed,

120a2a7#diff-9c5202a180f0e1f846ac307a432e16f75b5fcad52a3f396c5bd0d2e6d1b1112eR39

meanwhile I deactivated my "additional actions" because they were conflicting (replacing) the cleanup actions, without a way to have them exported.

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Then you can disable the save action "wrap in paranthesis" as well ;-)

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah you disabled them all - okay

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I disabled all "additional actions" so that the actions are not in duplicate between "clean up" profile and "save actions".
Yeah it's a complete mess, I agree with myself on that.

exported reduced save actions, removed addition of @deprecated on
methods in save actions.
@glelouet glelouet added the minor minor-level change : new feature, no breaking change label Jul 24, 2026
@glelouet

glelouet commented Sep 9, 2026

Copy link
Copy Markdown
Collaborator Author

@phax this one needs to be integrated too.

I changed the version to 4.4.0 in case you bump the minor in the next release. If not, revert the last commit after merging.

@glelouet

Copy link
Copy Markdown
Collaborator Author

@phax nooo you missed this one :p

@phax
phax merged commit 12dee91 into phax:master Sep 10, 2026
4 checks passed
@phax

phax commented Sep 10, 2026

Copy link
Copy Markdown
Owner

Okay - we will make a 4.4.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

minor minor-level change : new feature, no breaking change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

/JFieldVar marked as deprecated

2 participants