[jbosstools-issues] [JBoss JIRA] (JBDS-4263) possible use constraint violation from slf4j / slf4j-api

[Nick Boldt (JIRA)]

Nick Boldt created JBDS-4263:
--------------------------------

             Summary: possible use constraint violation from slf4j / slf4j-api
                 Key: JBDS-4263
                 URL: https://issues.jboss.org/browse/JBDS-4263
             Project: Red Hat JBoss Developer Studio (devstudio)
          Issue Type: Bug
          Components: rpm
    Affects Versions: 10.3.0.AM2
            Reporter: Nick Boldt


[~lvalach] said: {quote}
Hi Nick,

I tested installation of stuff from central as you described. I am not finished yet, but here is what I found.

-install latest integration stack bits from IS
 -JBoss Fule Development - OK
 -JBoss Business P. and Rules D. - OK
 -JBoss Integration and SOA D. - OK
 -JBoss Data Virtualization D. (IS early acess) 
   -there is problem with slf4j
   -IS contains Teiid 11.0.1.CR1-v20170117-222 which should be fixed
   -there are error like this:

{code}
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.equinox.preferences".
!STACK 0
java.lang.LinkageError: loader constraint violation: when resolving method "org.slf4j.impl.StaticLoggerBinder.getLoggerFactory()Lorg/slf4j/ILoggerFactory;" the class loader (instance of org/eclipse/osgi/internal/loader/EquinoxClassLoader) of the current class, org/slf4j/LoggerFactory, and the class loader (instance of org/eclipse/osgi/internal/loader/EquinoxClassLoader) for the method's defining class, org/slf4j/impl/StaticLoggerBinder, have different Class objects for the type org/slf4j/ILoggerFactory used in the signature{code}

-install everything from Central (including PMD and Findbugs, and early access stuff. NOTE: newer versions of the Integration Stack connectors should already be installed from the step above)
 -I installed everything using Central-Software/update, *no remediation action* was needed.
 -Eclipse started but with many errors. So I have to find out which feature causes the problem.{quote}

[~nickboldt] said:
{quote}
loader constraint violation == two different versions of slf4j in the installed plugins
check in :~/.eclipse/org.eclipse.platform_283378046_linux_gtk_x86_64 vs. in /opt/rh/{quote}

[~lvalach] said:

{quote}
{code}
cd ~/.eclipse/org.eclipse.platform_283378046_linux_gtk_x86_64
find . -iname *slf4j*
./configuration/org.eclipse.osgi/1293/0/.cp/lib/slf4j-api-1.6.1.jar
{code}
The output for /opt/rh/ is quite long but I can say that it contains slf4j.api_1.7.4.jar
{quote}

So, we may have a conflict between slf4j and slf4j-api, which both use the same bundle names, but expose packages differently.

Unclear which IS project is causing this problem as I thought we'd fixed both SY and TD already.

* https://issues.jboss.org/browse/SWITCHYARD-2976 
* https://issues.jboss.org/browse/TEIIDDES-2999



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)