geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yi Xiao (Assigned) (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (GERONIMODEVTOOLS-781) slf4j version conflict
Date Wed, 11 Jan 2012 09:42:40 GMT

     [ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Yi Xiao reassigned GERONIMODEVTOOLS-781:
----------------------------------------

    Assignee: Yi Xiao
    
> 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
>
> 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

        

Mime
View raw message