Community
Participate
Working Groups
I noticed that org.apache.maven.ProjectDependenciesResolver is deprecated with the following notice: > deprecated As of 3.2.2, and there is no direct replacement. > This is an internal class which was not marked as such, > but should have been. As of the recent discussion on the platform mailinglist and because this is used in a central place of tycho, I think we should take actions because it becomes a problem: - should we try to convince the maven team to make this public API? - can we use some already available API? - ... Any ideas/thoughts?
FWIW, unlike people who have complained on Platform, Tycho pro-actively tests its snapshots against the next release of Maven to notice and anticipate API removals. This job helps: https://ci.eclipse.org/tycho/job/tycho-build-with-maven-snapshots/ But indeed, it would be great if Tycho can use a better way to achieve the same functionality without such deprecated code. This would need to be investigated, and as long as we didn't investigate it enough to ensure we cannot do without the class, we shouldn't bug the Maven project to keep this API.
I just more think about if the API where removed (and we notice this) then people would maybe forced to use a specific maven version from there on so maybe it would be good to do the transition early. But I don't know maven internals enough to guess if there is an alternative way to to the desired dependency collection.
Eclipse Tycho is moving away from this bugs.eclipse.org issue tracker to https://github.com/eclipse/tycho/issues/ instead. If this issue is relevant to you, your action is required. 0. Verify this issue is still happening with latest Tycho 2.4.0-SNAPSHOT if issue has disappeared, please change status of this issue to "CLOSED WORKFORME" with some details about your testing environment and how you did verify the issue; and you're done if issue is still present when latest release: * Create a new issue at https://github.com/eclipse/tycho/issues/ ** Use as title in GitHub the title of this Bugzilla ticket (may include the bug number or not, at your own convenience) ** In the GitHub description, start with a link to this bugzilla ticket ** Optionally add new content to the description if it can helps towards resolution ** Submit GitHub issue * Update bugzilla ticket ** Add to "See also" property (up right column) the link to the newly created GitHub issue ** Add a comment "Migrated to <link-to-newly-created-GitHub-issue>" ** Set status as CLOSED MOVED ** Submit All issues that remain open will be automatically closed next week or so. Then the Bugzilla component for Tycho will be archived and made read-only.
