Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cleanup Plexus Utils, convergence with Maven 4 step 1 #1169

Closed
andrzejj0 opened this issue Oct 27, 2024 · 3 comments · Fixed by #1170
Closed

Cleanup Plexus Utils, convergence with Maven 4 step 1 #1169

andrzejj0 opened this issue Oct 27, 2024 · 3 comments · Fixed by #1170
Assignees
Milestone

Comments

@andrzejj0
Copy link
Contributor

Clean up deprecated methods.
Try to get rid as much as possible of Plexus Utils, see e.g. MNG-6825, MNG-7820.

This exercise focuses primarily on easy targets such as eliminating Plexus StringUtils in favour of Apache Commons etc.

The ultimate goal is to ease the upgrade to the upcoming changes from Maven 4.

@slawekjaranowski
Copy link
Member

I think that we not need an issue where we immediately provide PR.
Simply we can describe what we do in PR.

For me issue is useful when we want discus something before implementing or put on task list to do.

What do you think?

We can clarify it in README ...

@andrzejj0
Copy link
Contributor Author

Noted!

@andrzejj0
Copy link
Contributor Author

I think it does serve one important purpose though -- it lets us track progress on development. For example, I'm currently busy replacing ModifiedPOMXMLEventReader with a similar class based on Stax2, not using plexus xml anymore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants