September 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-25060) Make CDK integration tests run on mac machines in jenkins

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25060?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-25060: ---------------------------------- Story Points: 13 (was: 8) > Make CDK integration tests run on mac machines in jenkins > --------------------------------------------------------- > > Key: JBIDE-25060 > URL: https://issues.jboss.org/browse/JBIDE-25060 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: integration-tests, qa > Affects Versions: 4.5.1.AM2 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Labels: central-ci, jenkins > Fix For: 4.5.1.AM3 > > > Prepare job be be able to run cdk on macOS based slaves. > Upgrade macOS based slaves to utilize xhyve for cdk. This would requires to configure those steps: > # Download proper version of docker-machine-driver-xhyve binary > # enabled root access to this binary and add it into wheel group > # Add user as owner of the file > Execute on these machines: > * bigmek > * domek > * zamek > Refrence: https://docs.openshift.org/latest/minishift/getting-started/setting-up-dr... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25060) Make CDK integration tests run on mac machines in jenkins

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25060?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-25060: ---------------------------------- Description: Prepare job be be able to run cdk on macOS based slaves. Upgrade macOS based slaves to utilize xhyve for cdk. This would requires to configure those steps: # Download proper version of docker-machine-driver-xhyve binary # enabled access to this binary # Add user as owner of the file Execute on these machines: * bigmek * domek * zamek was:Prepare job be be able to run cdk on macOS based slaves. > Make CDK integration tests run on mac machines in jenkins > --------------------------------------------------------- > > Key: JBIDE-25060 > URL: https://issues.jboss.org/browse/JBIDE-25060 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: integration-tests, qa > Affects Versions: 4.5.1.AM2 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Labels: central-ci, jenkins > Fix For: 4.5.1.AM3 > > > Prepare job be be able to run cdk on macOS based slaves. > Upgrade macOS based slaves to utilize xhyve for cdk. This would requires to configure those steps: > # Download proper version of docker-machine-driver-xhyve binary > # enabled access to this binary > # Add user as owner of the file > Execute on these machines: > * bigmek > * domek > * zamek -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25060) Make CDK integration tests run on mac machines in jenkins

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25060?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-25060: ---------------------------------- Description: Prepare job be be able to run cdk on macOS based slaves. > Make CDK integration tests run on mac machines in jenkins > --------------------------------------------------------- > > Key: JBIDE-25060 > URL: https://issues.jboss.org/browse/JBIDE-25060 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: integration-tests, qa > Affects Versions: 4.5.1.AM2 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Labels: central-ci, jenkins > Fix For: 4.5.1.AM3 > > > Prepare job be be able to run cdk on macOS based slaves. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25051) Deadlock after startup

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25051?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov closed JBIDE-25051. ------------------------------------ Resolution: Rejected > Deadlock after startup > ---------------------- > > Key: JBIDE-25051 > URL: https://issues.jboss.org/browse/JBIDE-25051 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.0.Final > Reporter: Emond Papegaaij > Priority: Minor > Attachments: Screenshot_20170926_103927.png, eclipse-stackdump.txt > > > Eclipse deadlocked on me directly after startup (the workspace is shown). As the deadlock involves main, the UI is frozen entirely. I've reported the bug to Eclipse IDE first, but they suggested it is likely a JBoss Tools bug. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25132) Remove interface 'org.jboss.tools.hibernate.runtime.spi.IMappings'

by Koen Aers (JIRA)

Koen Aers created JBIDE-25132: --------------------------------- Summary: Remove interface 'org.jboss.tools.hibernate.runtime.spi.IMappings' Key: JBIDE-25132 URL: https://issues.jboss.org/browse/JBIDE-25132 Project: Tools (JBoss Tools) Issue Type: Task Components: hibernate Affects Versions: 4.5.1.AM2 Reporter: Koen Aers Assignee: Koen Aers Fix For: 4.5.1.AM3 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25051) Deadlock after startup

by Emond Papegaaij (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25051?page=com.atlassian.jira.plugi... ] Emond Papegaaij commented on JBIDE-25051: ----------------------------------------- I'm sorry, that's my fault. I updated eclipse after filing this bugreport. I did not recall any updates to jboss tools, but a closer look at the install history shows that 'JBoss AS, WildFly & EAP Server Tools' was updated from {{3.3.0.v20170613-1537}} to {{3.3.0.v20170801-2206}}. The other JBoss Tools components were not updated. I'm sorry for the confusion. > Deadlock after startup > ---------------------- > > Key: JBIDE-25051 > URL: https://issues.jboss.org/browse/JBIDE-25051 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.0.Final > Reporter: Emond Papegaaij > Priority: Minor > Attachments: Screenshot_20170926_103927.png, eclipse-stackdump.txt > > > Eclipse deadlocked on me directly after startup (the workspace is shown). As the deadlock involves main, the UI is frozen entirely. I've reported the bug to Eclipse IDE first, but they suggested it is likely a JBoss Tools bug. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25131) Expand credentials API to allow different credential types

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25131?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-25131: ------------------------------------- https://github.com/robstryker/jbosstools-base/tree/JBIDE-25131 and https://github.com/robstryker/jbosstools-openshift/tree/JBIDE-25131 > Expand credentials API to allow different credential types > ---------------------------------------------------------- > > Key: JBIDE-25131 > URL: https://issues.jboss.org/browse/JBIDE-25131 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: foundation > Affects Versions: 4.5.1.AM2 > Reporter: Rob Stryker > Assignee: Rob Stryker > > The Credentials API is pretty much restricted to a simple user/pass combination. This may be insufficient for the needs of the future. Make something more extendable ;) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25131) Expand credentials API to allow different credential types

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-25131: ----------------------------------- Summary: Expand credentials API to allow different credential types Key: JBIDE-25131 URL: https://issues.jboss.org/browse/JBIDE-25131 Project: Tools (JBoss Tools) Issue Type: Bug Components: foundation Affects Versions: 4.5.1.AM2 Reporter: Rob Stryker Assignee: Rob Stryker The Credentials API is pretty much restricted to a simple user/pass combination. This may be insufficient for the needs of the future. Make something more extendable ;) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25095) WildFly 11 runtime should add "wildfly-elytron-1.1.1.Final.jar" to build path

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25095?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-25095: ------------------------------------- Thanks for the heads up, wolfie :D > WildFly 11 runtime should add "wildfly-elytron-1.1.1.Final.jar" to build path > ----------------------------------------------------------------------------- > > Key: JBIDE-25095 > URL: https://issues.jboss.org/browse/JBIDE-25095 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.5.0.Final > Reporter: Wolfgang Knauf > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.5.1.AM3 > > > When a client app (e.g. a JavaEE application client) wants to perform a login to a WildFly 11 server, it has to either use a "wildfly-config.xml" file or add some code to setup security (see e.g. [Client authentication with Elytron client|https://docs.jboss.org/author/display/WFLY/Client+Authentication+w...] for a code snippet). > To make this code compile, two jar files are required: > %WILDFLY11_HOME%\modules\system\layers\base\org\wildfly\security\elytron-private\main\wildfly-elytron-1.1.1.Final.jar > %WILDFLY11_HOME%\modules\system\layers\base\org\wildfly\common\main\wildfly-common-1.2.0.Final.jar > I think the runtime should add them by default. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25051) Deadlock after startup

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25051?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-25051: ------------------------------------- For the record, the class in question in the stacktrace is at org.jboss.ide.eclipse.as.ui.actions.ChangeTimeStampActionDelegate.getServers(ChangeTimeStampActionDelegate.java:150) Baffled how this is even possible. > Deadlock after startup > ---------------------- > > Key: JBIDE-25051 > URL: https://issues.jboss.org/browse/JBIDE-25051 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.0.Final > Reporter: Emond Papegaaij > Priority: Minor > Attachments: Screenshot_20170926_103927.png, eclipse-stackdump.txt > > > Eclipse deadlocked on me directly after startup (the workspace is shown). As the deadlock involves main, the UI is frozen entirely. I've reported the bug to Eclipse IDE first, but they suggested it is likely a JBoss Tools bug. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues September 2017