Community
Participate
Working Groups
+++ This bug was initially created as a clone of Bug #394295 +++ As part of the CBI build, it runs the p2 comparator on every bundle it builds. we need to parse the (somewhat large) maven output log and look for comparator failures. PW = = = = = The cloned bug is a work item for us to examine the output, which, we can begin to do shortly. But, we would likely want to always get the comparator output, every build, and to do that, currently, requires turning on debug (-X) and the log file is routinely greater than 400 Megabytes! Lots in there besides comparator information. So, this is a request to provide ability to get the comparator output in a separate file, without specifying -X. Perhaps the task (goal?) could provide a configuration item for optional "comparatorLog" and if it was specified, the comparator output would always go to it, whether -X specified or not. Else, to maintain current behavior (if that's important), still provide it to standard out if -X was specified without a comparatorLog?
Writing comparator output to a separate file is a reasonable requirement. In fact, the comparator already does this for some of its output, so making it possible to redirect all comparator message makes sense. (the extra comparison detailed can be enabled with -Dtycho.debug.artifactcomparator command line parameter. When enabled, for each class file that is different between baseline and build Tycho will generate two bytecode dumps, one with -build and anything -baseline suffix in project target/ folder)
See also bug 401162 for alternative implementations of the comparator.
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.
