[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yi Xiao updated GERONIMODEVTOOLS-781: ------------------------------------- Attachment: slf4jVersionConflict_781.patch I remove all the org.self4j.* packages from manifest.mf, and test the scenario in description, also have some deploy/remove application tests in the new gep build, it works fine. > slf4j version conflict > ---------------------- > > Key: GERONIMODEVTOOLS-781 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-781 > Project: Geronimo-Devtools > Issue Type: Bug > Components: eclipse-plugin > Affects Versions: 3.0-beta-1 > Reporter: Jarek Gawor > Assignee: Yi Xiao > Attachments: slf4jVersionConflict_781.patch > > > I tired installing "Maven Integration for Eclipse" plugin via Eclipse > Marketplace on Eclipse 3.6.2 Java EE with the GEP plugin and Rational OSGI > tooling installed. The Maven plugin installed fine but it failed to start. I > tracked down the problem to a conflict in org.slf4j APIs. The GEP runtime > plugins export the org.slf4j.* APIs with the given Geronimo version. For > example, the GEP v3 runtime plugin exports org.slf4j.api with version 3. That > confuses other plugins in Eclipse and causes the Maven plugin not to start. > I'm not sure 1) why we export the org.slf4j.* API out of GEP plugins in the > first place and 2) if we need to export them why are we exporting them with > the Geronimo version instead of the actual SLF4J version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira