Community
Participate
Working Groups
Bug 535689 relates a problem due to using a vintage Tycho 1.4.0 that was obscurely diagnosed as an illegal reflective operation in httpclient4. The recent churning of Java versions and deprecations within Eclipse make the nominally free choice of Java, Eclipse, Tycho, Maven versions a far from independent choice. Many bad combinations crash obviously. But more subtle incompatibilities give really obscure diagnosis. Suggest: something in Tycho, ? the maven-enforcer ?, could issue helpful warnings about known subtly bad combinations? NB The underlying metadata for this diagnosis must be version independent to avoid needing to upgrade the metadata to discover the need to upgrade the metadata. An evolving XML file should do, enumerating bad combinations with a reason text and override-able identity. A version inheritance policy is needed to avoid duplicating across versions. NB Warnings are needed only for genuine incompatibility hazards, not for the developer's enthusiasm for the latest version.
(In reply to Ed Willink from comment #0) > NB The underlying metadata for this diagnosis must be version independent Correction: provided the default setting is the "latest" metadata, then versions can be used to replicate historic decisions.
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.
