November 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-20571) OpenShift Explorer: Build/Pod activity should be refreshed automatically

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20571?page=com.atlassian.jira.plugi... ] Jeff Cantrill updated JBIDE-20571: ---------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-openshift/pull/810, https://github.com/openshift/openshift-restclient-java/pull/90, https://github.com/openshift/openshift-restclient-java/pull/91 (was: https://github.com/jbosstools/jbosstools-openshift/pull/810, https://github.com/openshift/openshift-restclient-java/pull/90) > OpenShift Explorer: Build/Pod activity should be refreshed automatically > ------------------------------------------------------------------------ > > Key: JBIDE-20571 > URL: https://issues.jboss.org/browse/JBIDE-20571 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Fix For: 4.3.1.Beta1 > > > Currently, when a build is running on openshift, users need to manually refresh the OpenShift Explorer view, to see when a build or a deployment finishes. > We need to be able to let the explorer "watch" some specific project events (via websockets or some other method). > As a workaround we might be able to trigger automatic refreshes of the viewer, every 5secs, when we detect a pod is in pending, building, deploying or some other status. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20908) Upgrade FreeMarker to 2.3.23

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20908?page=com.atlassian.jira.plugi... ] Jiri Peterka closed JBIDE-20908. -------------------------------- Verified with Build JBDS 9.0.1.Beta1-v20151110-2316-B137 > Upgrade FreeMarker to 2.3.23 > ---------------------------- > > Key: JBIDE-20908 > URL: https://issues.jboss.org/browse/JBIDE-20908 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: freemarker > Reporter: Daniel Dekany > Assignee: Daniel Azarov > Fix For: 4.3.1.Beta1 > > > 2.3.23 has added new listing-related directives and "built-ins". Also it has support for camel case (like `?startsWith` instead of `?starts_with`). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20571) OpenShift Explorer: Build/Pod activity should be refreshed automatically

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20571?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-20571: --------------------------------------- [~fbricon] [~adietish] [~maxandersen] I have updated the PR in JBT to try restart logic when the client disconnects. This triggers the start of watch when a project is expanded. Please review. Note: it additionally is dependent upon an additional PR in the rest client > OpenShift Explorer: Build/Pod activity should be refreshed automatically > ------------------------------------------------------------------------ > > Key: JBIDE-20571 > URL: https://issues.jboss.org/browse/JBIDE-20571 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Fix For: 4.3.1.Beta1 > > > Currently, when a build is running on openshift, users need to manually refresh the OpenShift Explorer view, to see when a build or a deployment finishes. > We need to be able to let the explorer "watch" some specific project events (via websockets or some other method). > As a workaround we might be able to trigger automatic refreshes of the viewer, every 5secs, when we detect a pod is in pending, building, deploying or some other status. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-234) DSL Validation

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-234?page=com.atlassian.jira.plugin.... ] Paul Leacu closed JBTIS-234. ---------------------------- Resolution: Out of Date Closing as out-of-date. Please re-issue a new Jira if this is still a problem. > DSL Validation > -------------- > > Key: JBTIS-234 > URL: https://issues.jboss.org/browse/JBTIS-234 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: drools/ jBPM > Environment: All > Reporter: Jim Tyrrell > Assignee: Kris Verlaenen > > When authoring a DLS file you will typically have variable names of the type: "{disabilityType}"=customer: Customer(disabilityType == "{disabilityType}") or something like this. If the Customer object does not exist some sort of problem should be noted in the Problems section. Also a DSL might look like this: > {percentage}=eval(customer.disabledPercent >= {percentage}) This to is a little harder as the customer is a variable that is implied. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-233) Highlighting a line in the Domain Specific Editor, the Delete key should work

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-233?page=com.atlassian.jira.plugin.... ] Paul Leacu closed JBTIS-233. ---------------------------- Resolution: Out of Date Closing as out-of-date. > Highlighting a line in the Domain Specific Editor, the Delete key should work > ----------------------------------------------------------------------------- > > Key: JBTIS-233 > URL: https://issues.jboss.org/browse/JBTIS-233 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: drools/ jBPM > Environment: All > Reporter: Jim Tyrrell > Assignee: Kris Verlaenen > Attachments: Screen shot 2010-06-09 at 8.24.52 AM.png > > > When I am editing or creating a Domain Specific Language it would be nice to have an Accelerator on the delete key to delete the highlighted line instead of having to click "Remove". It should also be possible to highlight all of them and be able to delete them all, although this might get in the way of what you happens when you click "Edit" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16503) Empty Hibernate Console Configuration dialog

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16503?page=com.atlassian.jira.plugi... ] Jiri Peterka closed JBIDE-16503. -------------------------------- Verified with Build JBDS 9.0.1.Beta1-v20151110-2316-B137 > Empty Hibernate Console Configuration dialog > -------------------------------------------- > > Key: JBIDE-16503 > URL: https://issues.jboss.org/browse/JBIDE-16503 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate, upstream > Affects Versions: 4.2.0.Alpha2 > Environment: JBT 4.2.0.Alpha2 (on Eclipse Luna M5), L64, Fedora 19, OpenJDK 1.7 > Reporter: Jiri Peterka > Assignee: Koen Aers > Fix For: 4.4.0.Alpha1 > > Attachments: empty-hb-console-dialog.png > > > There is empty "Create Hibernate Console" dialog -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21028) Empty Hibernate Console Configuration dialog

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21028?page=com.atlassian.jira.plugi... ] Jiri Peterka closed JBIDE-21028. -------------------------------- Verified with Build JBDS 9.0.1.Beta1-v20151110-2316-B137 > Empty Hibernate Console Configuration dialog > -------------------------------------------- > > Key: JBIDE-21028 > URL: https://issues.jboss.org/browse/JBIDE-21028 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate, upstream > Affects Versions: 4.2.0.Alpha2 > Environment: JBT 4.2.0.Alpha2 (on Eclipse Luna M5), L64, Fedora 19, OpenJDK 1.7 > Reporter: Jiri Peterka > Assignee: Koen Aers > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > Attachments: empty-hb-console-dialog.png > > > There is empty "Create Hibernate Console" dialog -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21100) start process of WildFly-8.2.0-Final never finish (Starting, Synchronized)

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21100?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-21100: -------------------------------------- Assignee: Rob Stryker (was: Jason Greene) > start process of WildFly-8.2.0-Final never finish (Starting, Synchronized) > --------------------------------------------------------------------------- > > Key: JBIDE-21100 > URL: https://issues.jboss.org/browse/JBIDE-21100 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Environment: start process of WildFly-8.2.0-Final never finish (Starting, Synchronized) > Reporter: carl zhang > Assignee: Rob Stryker > > please refer to > https://developer.jboss.org/thread/265726?start=0&tstart=0 > refer to the picture of 28-Oct-2015 9:46 AM (layer 3) > In the left panel: WildFly 8.x is configured to connect to localhost > WildFly 8.x(1) is configured to connect to remote host (Linux) > The localhost cannot finish start process. WildFly 8.x(1) (remote) can. > What ports, or temp files, or anything else are checked when changing from starting to started state? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21100) start process of WildFly-8.2.0-Final never finish (Starting, Synchronized)

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21100?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21100: ----------------------------------- Component/s: server > start process of WildFly-8.2.0-Final never finish (Starting, Synchronized) > --------------------------------------------------------------------------- > > Key: JBIDE-21100 > URL: https://issues.jboss.org/browse/JBIDE-21100 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Environment: start process of WildFly-8.2.0-Final never finish (Starting, Synchronized) > Reporter: carl zhang > Assignee: Jason Greene > > please refer to > https://developer.jboss.org/thread/265726?start=0&tstart=0 > refer to the picture of 28-Oct-2015 9:46 AM (layer 3) > In the left panel: WildFly 8.x is configured to connect to localhost > WildFly 8.x(1) is configured to connect to remote host (Linux) > The localhost cannot finish start process. WildFly 8.x(1) (remote) can. > What ports, or temp files, or anything else are checked when changing from starting to started state? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21100) start process of WildFly-8.2.0-Final never finish (Starting, Synchronized)

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21100?page=com.atlassian.jira.plugi... ] Tomaz Cerar updated JBIDE-21100: -------------------------------- Project: Tools (JBoss Tools) (was: WildFly) Key: JBIDE-21100 (was: WFLY-5681) Component/s: (was: IDE) Affects Version/s: (was: 8.2.0.Final) > start process of WildFly-8.2.0-Final never finish (Starting, Synchronized) > --------------------------------------------------------------------------- > > Key: JBIDE-21100 > URL: https://issues.jboss.org/browse/JBIDE-21100 > Project: Tools (JBoss Tools) > Issue Type: Bug > Environment: start process of WildFly-8.2.0-Final never finish (Starting, Synchronized) > Reporter: carl zhang > Assignee: Jason Greene > > please refer to > https://developer.jboss.org/thread/265726?start=0&tstart=0 > refer to the picture of 28-Oct-2015 9:46 AM (layer 3) > In the left panel: WildFly 8.x is configured to connect to localhost > WildFly 8.x(1) is configured to connect to remote host (Linux) > The localhost cannot finish start process. WildFly 8.x(1) (remote) can. > What ports, or temp files, or anything else are checked when changing from starting to started state? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues November 2015