Community
Participate
Working Groups
I am facing a target file where I don't know which feature/depencency brings is a certain bundle. I am not aware of any feature in Eclipse which allows me to find this out. Therefore I am thinking about implementing an option/mojo to write the the resolved target file to disk in a p2 metadata respository format. This would at least allow me to trace inclusion/dependency chains with a text editor.
... or Igor's p2-browser [1] [1] https://github.com/ifedorenko/p2-browser
http://wiki.eclipse.org/Tycho/Target_Platform#Listing_IUs_available gives information on listing the IUs of a repository. Is there an option in Tycho to list all the plug-ins from the resolved target? If my target is composed of 5 repositories, it is difficult to see the aggregated target. May be I have an older version of a plug-in but the the source being built needs a newer version and it is not found. For some strange reasons, our development target is different from Tycho's and we run into this problem frequently.
I got hold of https://issues.sonatype.org/browse/TYCHO-297 in the meantime and am experimenting it. I will update the result here.
Using -Dtycho.debug.resolver=true helped. Thanks.
I'm currently debugging a build error where some product configuration IUs are missing in one module, but only if the module is built as part of the overall reactor, not if it is built separately. Apparently, there is some other reactor project which produces a product configuration IU with the same ID (hence it it filtered from the external IUs). However that project is downstream of the failing project... I haven't found the downstream project contributing the IU yet, so a map of (preliminary) reactor IU IDs to project locations would be useful here.
New Gerrit change created: https://git.eclipse.org/r/58822
New Gerrit change created: https://git.eclipse.org/r/58821
target milestone 0.25.0 not met
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.
