Community
Participate
Working Groups
Even though Maven 3.1+ uses SLF4J, tt is surprisingly very difficult to configure logging for Tycho. See for example: https://stackoverflow.com/questions/4782089/how-to-change-maven-logging-level-to-display-only-warning-and-errors https://stackoverflow.com/questions/4275433/maven-log-file-configuration By default, Tycho logs at INFO level because that's the default logging configuration in Maven 3.1+. However, INFO-level logging produces so much output that this can easily exceed Travis-CI's 4MB output limit thereby resulting in terminating the job! Amazingly, the simplest workaround to this problem is to filter the output of maven. It would be helpful to have support for configuring logging either globally or for particular plugins. Without this flexibility, there is an incentive for switching from Tycho to more flexible build technologies like SBT or Gradle.
this is more or less a maven core question as Tycho uses the same logging mechanism as any other maven plugin provide by maven core. There are levels info, warning, error and debug available. info,warning and error are logged by default and you already found out maven only has options -q to suppress info and -X to enable debug. a hard 4MB output limit sounds like a bug in travis to me https://github.com/travis-ci/travis-ci/issues/1382
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.
