[JBoss JIRA] (JBDS-4263) possible use constraint violation from slf4j / slf4j-api
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4263?page=com.atlassian.jira.plugin.... ]
Lukáš Valach commented on JBDS-4263:
------------------------------------
I tried to install Jboss Data Virtualization Developement from [IS discovery site|http://download.jboss.org/jbosstools/neon/integration/updates/integr...] again.
Whole log:
[^rh-eclipse46-devstudio10.3-0.20170206.0203.el7.log.Jboss_Data_Virtualization_Developement_form_IS_repo_strict.txt]
Slf4j files in ~/.eclipse/org.eclipse.platform_283378046_linux_gtk_x86_64/
[^home_eclipse.txt]
Slf4j files in /opt/rh/
[^opt_rh.txt]
> 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
> Assignee: Lukáš Valach
> Fix For: 10.3.0.GA
>
> Attachments: home_eclipse.txt, opt_rh.txt, rh-eclipse46-devstudio10.3-0.20170206.0203.el7.log.Jboss_Data_Virtualization_Developement_form_IS_repo_strict.txt
>
>
> [~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/
> Problem appears to be in *org.slf4j.impl.StaticLoggerBinder.getLoggerFactory()Lorg/slf4j/ILoggerFactory*. {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)
9 years, 1 month
[JBoss JIRA] (JBDS-4263) possible use constraint violation from slf4j / slf4j-api
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4263?page=com.atlassian.jira.plugin.... ]
Lukáš Valach updated JBDS-4263:
-------------------------------
Attachment: home_eclipse.txt
> 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
> Assignee: Lukáš Valach
> Fix For: 10.3.0.GA
>
> Attachments: home_eclipse.txt, opt_rh.txt, rh-eclipse46-devstudio10.3-0.20170206.0203.el7.log.Jboss_Data_Virtualization_Developement_form_IS_repo_strict.txt
>
>
> [~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/
> Problem appears to be in *org.slf4j.impl.StaticLoggerBinder.getLoggerFactory()Lorg/slf4j/ILoggerFactory*. {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)
9 years, 1 month
[JBoss JIRA] (JBDS-4263) possible use constraint violation from slf4j / slf4j-api
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4263?page=com.atlassian.jira.plugin.... ]
Lukáš Valach updated JBDS-4263:
-------------------------------
Attachment: opt_rh.txt
> 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
> Assignee: Lukáš Valach
> Fix For: 10.3.0.GA
>
> Attachments: home_eclipse.txt, opt_rh.txt, rh-eclipse46-devstudio10.3-0.20170206.0203.el7.log.Jboss_Data_Virtualization_Developement_form_IS_repo_strict.txt
>
>
> [~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/
> Problem appears to be in *org.slf4j.impl.StaticLoggerBinder.getLoggerFactory()Lorg/slf4j/ILoggerFactory*. {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)
9 years, 1 month
[JBoss JIRA] (JBIDE-23867) OCBinary: is mixing platform independent with dependent code
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-23867:
----------------------------------------
Summary: OCBinary: is mixing platform independent with dependent code
Key: JBIDE-23867
URL: https://issues.jboss.org/browse/JBIDE-23867
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.4.3.AM2
Reporter: Andre Dietisheim
OCBinary is suing enums for the different platform. The platform instance is chosen right when you get the instance that you want to work with:
{code}
OCBinary#getInstance
{code}
{code}
public static OCBinary getInstance() {
if (SystemUtils.IS_OS_WINDOWS) {
return WINDOWS;
} else {
return OTHER;
}
}
{code}
But then, latter code (that was introduced later in #getSystemPathLocation ignoring it and start being platform independent again, even setting the default to be linux:
{code}
public String getSystemPathLocation() {
if (locationBinary == null) {
this.locationBinary = new CommandLocationBinary("oc");
locationBinary.addPlatformLocation(Platform.OS_LINUX, OC_DEFAULTLOCATION_LINUX);
locationBinary.setDefaultPlatform(Platform.OS_LINUX);
}
return locationBinary.findLocation();
}
{code}
Even worse is that the above code hard-codes the oc binary to be "oc" while the enum for windows is defining it as "oc.exe"
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23867) OCBinary: is mixing platform independent with dependent code
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23867?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-23867:
----------------------------------------
Assignee: Rob Stryker
> OCBinary: is mixing platform independent with dependent code
> ------------------------------------------------------------
>
> Key: JBIDE-23867
> URL: https://issues.jboss.org/browse/JBIDE-23867
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.3.AM2
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
>
> OCBinary is suing enums for the different platform. The platform instance is chosen right when you get the instance that you want to work with:
> {code}
> OCBinary#getInstance
> {code}
> {code}
> public static OCBinary getInstance() {
> if (SystemUtils.IS_OS_WINDOWS) {
> return WINDOWS;
> } else {
> return OTHER;
> }
> }
> {code}
> But then, latter code (that was introduced later in #getSystemPathLocation ignoring it and start being platform independent again, even setting the default to be linux:
> {code}
> public String getSystemPathLocation() {
> if (locationBinary == null) {
> this.locationBinary = new CommandLocationBinary("oc");
> locationBinary.addPlatformLocation(Platform.OS_LINUX, OC_DEFAULTLOCATION_LINUX);
> locationBinary.setDefaultPlatform(Platform.OS_LINUX);
> }
> return locationBinary.findLocation();
> }
> {code}
> Even worse is that the above code hard-codes the oc binary to be "oc" while the enum for windows is defining it as "oc.exe"
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBDS-4263) possible use constraint violation from slf4j / slf4j-api
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4263?page=com.atlassian.jira.plugin.... ]
Lukáš Valach updated JBDS-4263:
-------------------------------
Attachment: rh-eclipse46-devstudio10.3-0.20170206.0203.el7.log.Jboss_Data_Virtualization_Developement_form_IS_repo_strict.txt
> 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
> Assignee: Lukáš Valach
> Fix For: 10.3.0.GA
>
> Attachments: rh-eclipse46-devstudio10.3-0.20170206.0203.el7.log.Jboss_Data_Virtualization_Developement_form_IS_repo_strict.txt
>
>
> [~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/
> Problem appears to be in *org.slf4j.impl.StaticLoggerBinder.getLoggerFactory()Lorg/slf4j/ILoggerFactory*. {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)
9 years, 1 month