[JBoss JIRA] (JBIDE-23536) components.py should store the assigned user
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23536?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23536:
-------------------------------
Attachment: run.log
> components.py should store the assigned user
> --------------------------------------------
>
> Key: JBIDE-23536
> URL: https://issues.jboss.org/browse/JBIDE-23536
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.4.2.Final
> Reporter: Jeff MAURY
> Assignee: Nick Boldt
> Labels: build, release, release-eng
> Fix For: 4.4.3.Final
>
> Attachments: run.log
>
>
> The file components.py is used when created JIRAs during the release process. One JIRA is created per component. But those JIRAs are not initially assigned to a user, so the user of the scripts (createnewandnotworthy,....) must update all the created JIRAs. If the file stored as well the JIRA user id, then this could be done automatically
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23536) components.py should store the assigned user
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23536?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23536:
-------------------------------
Fix Version/s: 4.4.3.Final
(was: 4.4.3.AM2)
> components.py should store the assigned user
> --------------------------------------------
>
> Key: JBIDE-23536
> URL: https://issues.jboss.org/browse/JBIDE-23536
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.4.2.Final
> Reporter: Jeff MAURY
> Assignee: Jeff MAURY
> Labels: build, release, release-eng
> Fix For: 4.4.3.Final
>
> Attachments: run.log
>
>
> The file components.py is used when created JIRAs during the release process. One JIRA is created per component. But those JIRAs are not initially assigned to a user, so the user of the scripts (createnewandnotworthy,....) must update all the created JIRAs. If the file stored as well the JIRA user id, then this could be done automatically
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23422) Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error
by Rob Cernich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23422?page=com.atlassian.jira.plugi... ]
Rob Cernich commented on JBIDE-23422:
-------------------------------------
There is a timeout on the port-forwarder itself:
https://github.com/openshift/origin/blob/master/vendor/k8s.io/kubernetes/...
https://github.com/openshift/origin/blob/master/vendor/k8s.io/kubernetes/...
https://github.com/openshift/origin/blob/master/vendor/k8s.io/kubernetes/...
Can't find where the default is set, but here's a start (it's a config option): https://github.com/openshift/origin/blob/master/vendor/k8s.io/kubernetes/...
> Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-23422
> URL: https://issues.jboss.org/browse/JBIDE-23422
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: javascript, openshift
> Affects Versions: 4.4.2.AM2
> Environment: windows 10
> Fedora 24
> Reporter: Ilya Buziuk
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: nodejs, openshift_v3, server_adapter
> Fix For: 4.4.3.Final
>
>
> We've found, that when one is debugging (the code is stopeed at breakpoint, stepping through code, inspecting variables, ...) longer than ~1 minute, browser displays error code 502 and the debug session gets terminated. This makes this feature not very useful, because all debugging must be quicker than that timeout.
> The behavior is captured in this screencast: https://youtu.be/BJf7wcPqNmM (note how at the time 0:42 the page is finally loaded (502 error) and the debug session is terminated (in debug view)).
> We were able to reproduce this issue on F24 and Win10 (using CDK and console.engint.openshift.com)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23862) Server adapter: if "oc" in preferences is set to path with a " " syncing fails
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23862?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23862:
-------------------------------------
Steps to Reproduce:
# ASSERT: make sure that you have "oc" available at a path that contains a " " (ex. /Users/adietish/Download/oc binaries/oc)
# ASSERT: have an OpenShift server adapter
# EXEC: start the adapter
Result:
Publishing fails, reporting that the "oc" binary could not be found
was:
# ASSERT: make sure that you have "oc" available at a path that contains a " " (ex. /Users/adietish/Download/oc binaries/oc"
# ASSERT: have an OpenShift server adapter
# EXEC: start the adapter
Result:
Publishing fails, reporting that the "oc" binary could not be found
> Server adapter: if "oc" in preferences is set to path with a " " syncing fails
> ------------------------------------------------------------------------------
>
> Key: JBIDE-23862
> URL: https://issues.jboss.org/browse/JBIDE-23862
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.3.Final
> Reporter: Andre Dietisheim
> Fix For: 4.4.3.Final
>
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBDS-4263) possible use constraint violation from slf4j / slf4j-api
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4263?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4263:
-----------------------------
Description:
[~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
was:
[~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
> 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
>
>
> [~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, 2 months
[JBoss JIRA] (JBDS-4263) possible use constraint violation from slf4j / slf4j-api
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4263?page=com.atlassian.jira.plugin.... ]
Nick Boldt reassigned JBDS-4263:
--------------------------------
Assignee: Lukáš Valach
> 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
>
>
> [~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)
9 years, 2 months
[JBoss JIRA] (JBDS-4263) possible use constraint violation from slf4j / slf4j-api
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4263?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4263:
-----------------------------
Fix Version/s: 10.3.0.GA
> 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
>
>
> [~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)
9 years, 2 months
[JBoss JIRA] (JBDS-4263) possible use constraint violation from slf4j / slf4j-api
by 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)
9 years, 2 months