Re: [DISCUSS] Many shared stuff should be dropped

2024-05-21 Thread Tim te Beek
Hi! Happy to help with any automated migrations and/or recipe development. Feel free to log an issue describing the changes needed over on: https://github.com/openrewrite/rewrite-apache I'll have some more time in June and over the summer to help out. >From there on we can track progress and effe

Re: [DISCUSS] Many shared stuff should be dropped

2024-05-20 Thread Sylwester Lachiewicz
Hi, yes, it would be a good idea to review our project and at last update README that we plan to deprecate some components - to avoid unnecessary work on this. A quick search for "org.apache.maven.shared.dependency.graph" for org:apache shows that we should implement changes also in our plugins an

Re: [DISCUSS] Many shared stuff should be dropped

2024-05-20 Thread Hervé Boutemy
hi Tamasz, I think you're right on maven-dependency-tree, as it was with maven-artifact- transfer I'm not really convinced *many* shared stuff should be dropped: IMHO, over- generalization And I think that when replacing a shared stuff with direct use of an existing API, in fact what normal peo

[DISCUSS] Many shared stuff should be dropped

2024-05-20 Thread Tamás Cservenák
Howdy, I see ongoing development against many "shared" libraries, that in fact, should be dropped instead. One notable example is "maven-dependency-tree". This codebase was born (well, factored out) from Maven2 reporting, to be extended with "Maven 3.0 support", then "Maven 3.1 support" and is ju