Community
Participate
Working Groups
Build Identifier: I20110613-1736 Maven Integration for Eclipse 1.0.0.20110607-2117 produces no output to eclipse Maven Console view so that it is impossible to track plugin's activity (background maven builds, source and javadoc downloads, etc), which is very inconvenient. At the same time Sonatype Maven Integration for Eclipse 0.12.1.201101012-1712 version of plugin displays expected plugin activity output, e.g. output for downloading artifact sources: 5.07.11 10:47:15 EEST: Downloading http://repo1.maven.org/maven2/commons-io/commons-io/1.3.2/commons-io-1.3.2-sources.jar 5.07.11 10:47:16 EEST: Downloaded http://repo1.maven.org/maven2/commons-io/commons-io/1.3.2/commons-io-1.3.2-sources.jar 5.07.11 10:47:17 EEST: Downloaded sources for commons-io:commons-io:1.3.2 5.07.11 10:47:18 EEST: Maven Builder: AUTO_BUILD Reproducible: Always Steps to Reproduce: There is no output in Maven Console for background activity at all.
Please attach eclipse configuration details and exact steps to reproduce the problem. FWIW, I see java sources download and plugin execute log messages in Maven console when using Eclipse 3.7 "for java developers" distribution.
[eclipse.ini] -startup plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar -vm C:/Program Files/Java/jdk1.6.0_21/bin --launcher.library plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.100.v20110502 -showsplash org.eclipse.platform --launcher.XXMaxPermSize 256m --launcher.defaultAction openFile -vmargs -Xms40m -Xmx384m [Eclipse bundle] Eclipse Classic 3.7 (eclipse-SDK-3.7-win32-x86_64) with m2e installed separately through default indigo update site. Steps to reproduce: File -> New -> Other -> Maven -> Maven Project -> [Next] -> Create a simple project -> [Group Id = test, Artifact Id = test] -> Finish Expected Maven Console view output: 05.07.11 13:54.12 GMT+03:00: [INFO] Using org.eclipse.m2e.jdt.JarLifecycleMapping lifecycle mapping for MavenProject: test:test:0.0.1-SNAPSHOT @ C:\download\eclipse-java-indigo-win32-x86_64\eclipse\workspace\test\pom.xml. 05.07.11 13:54.12 GMT+03:00: [INFO] Adding source folder /test/src/main/java 05.07.11 13:54.12 GMT+03:00: [INFO] Adding resource folder /test/src/main/resources 05.07.11 13:54.12 GMT+03:00: [INFO] Adding source folder /test/src/test/java 05.07.11 13:54.12 GMT+03:00: [INFO] Adding resource folder /test/src/test/resources 05.07.11 13:54.12 GMT+03:00: [INFO] Using org.eclipse.m2e.jdt.JarLifecycleMapping lifecycle mapping for MavenProject: test:test:0.0.1-SNAPSHOT @ C:\download\eclipse-java-indigo-win32-x86_64\eclipse\workspace\test\pom.xml. 05.07.11 13:54.12 GMT+03:00: [WARN] Using platform encoding (Cp1257 actually) to copy filtered resources, i.e. build is platform dependent! 05.07.11 13:54.12 GMT+03:00: [INFO] Copying 0 resource 05.07.11 13:54.12 GMT+03:00: [WARN] Using platform encoding (Cp1257 actually) to copy filtered resources, i.e. build is platform dependent! 05.07.11 13:54.12 GMT+03:00: [INFO] Copying 0 resource Actual output: NONE P.S. I tried it with Eclipse IDE 3.7 for Java Developers," bundle and it really works there. The problem seems to be somewhere in integration with/installation to Eclipse Classic.
[Workspace log file for the period of problem reproduce] !SESSION 2011-07-05 14:01:47.273 ----------------------------------------------- eclipse.buildId=I20110613-1736 java.version=1.6.0_21 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=et_EE Command-line arguments: -os win32 -ws win32 -arch x86_64 !ENTRY org.eclipse.ui 4 4 2011-07-05 14:04:36.285 !MESSAGE Invalid preference page path: XML Syntax
Double-check you have org.eclipse.m2e.logback.feature feature installed as you need to install it separately. And I would still like to see your eclipse configuration details (AboutEclipse->InstallationDetails->Configuration).
Thanks Igor, you were right - with org.eclipse.m2e.logback.feature.feature.group feature installed Maven Console view output works fine. I believe that there is still something that could be done to prevent same kind of problems in the future: - the feature "m2e - slf4j over logback logging" is optional on update site, but without having it installed a portion of expected functionality (that was previously present in sonatype releases by default) is not available. Why not make this feature required when installing "m2e - Maven Integration for Eclipse"? Does it cause any licensing issues? - the logging feature title is not descriptive, and the description is also poor. I filtered by keyword "maven", and found only "m2e - Maven Integration for Eclipse". I remember that sonatype plugin did not require installation of any additional logging features, so I just installed the only found plugin. But even if I would have filtered by "m2e" and found "m2e - slf4j over logback logging" - why would I decide to install it if it is optional and does not say exactly what effect it has. The description "slf4j over logback logging configuration for Maven Integration for Eclipse" does not say much about Maven Console view perspective functioning properly. If it is impossible to make the logging feature required - there could at least be a hint saying what impact the installation of this feature has.
Added a note about Maven Console View support provided by slf4j feature. http://git.eclipse.org/c/m2e/m2e-core.git/commit/?id=0d332c2fa822aaca9cf9119981074ee9684840a2 As a tool, m2e is not in the position to impose any specific slf4j logging backend on the host Eclipse installation.
Moved to https://github.com/eclipse-m2e/m2e-core/issues/
