September 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-18298) Text in OpenShift dialogs cannot be read

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18298?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-18298: ------------------------------------- [~snjeza], [~dgolovin] : any idea that might help [~adietish]? > Text in OpenShift dialogs cannot be read > ---------------------------------------- > > Key: JBIDE-18298 > URL: https://issues.jboss.org/browse/JBIDE-18298 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.CR1 > Environment: RHEL 6 > Java 1.7 > Reporter: Len DiMaggio > Assignee: Andre Dietisheim > Priority: Critical > Labels: respin-b > Fix For: 4.2.0.CR1 > > Attachments: Screenshot-1.png, Screenshot.png > > > See the attached screenshots - some text boxes cannot be read as the background and text are both dark. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18298) Text in OpenShift dialogs cannot be read

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18298?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-18298: -------------------------------- Assignee: Andre Dietisheim > Text in OpenShift dialogs cannot be read > ---------------------------------------- > > Key: JBIDE-18298 > URL: https://issues.jboss.org/browse/JBIDE-18298 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.CR1 > Environment: RHEL 6 > Java 1.7 > Reporter: Len DiMaggio > Assignee: Andre Dietisheim > Priority: Critical > Labels: respin-b > Fix For: 4.2.0.Final > > Attachments: Screenshot-1.png, Screenshot.png > > > See the attached screenshots - some text boxes cannot be read as the background and text are both dark. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18298) Text in OpenShift dialogs cannot be read

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18298?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-18298: -------------------------------- Fix Version/s: 4.2.0.CR1 (was: 4.2.0.Final) > Text in OpenShift dialogs cannot be read > ---------------------------------------- > > Key: JBIDE-18298 > URL: https://issues.jboss.org/browse/JBIDE-18298 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.CR1 > Environment: RHEL 6 > Java 1.7 > Reporter: Len DiMaggio > Assignee: Andre Dietisheim > Priority: Critical > Labels: respin-b > Fix For: 4.2.0.CR1 > > Attachments: Screenshot-1.png, Screenshot.png > > > See the attached screenshots - some text boxes cannot be read as the background and text are both dark. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18298) Text in OpenShift dialogs cannot be read

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18298?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-18298: -------------------------------- Labels: respin-b (was: ) > Text in OpenShift dialogs cannot be read > ---------------------------------------- > > Key: JBIDE-18298 > URL: https://issues.jboss.org/browse/JBIDE-18298 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.CR1 > Environment: RHEL 6 > Java 1.7 > Reporter: Len DiMaggio > Assignee: Andre Dietisheim > Priority: Critical > Labels: respin-b > Fix For: 4.2.0.CR1 > > Attachments: Screenshot-1.png, Screenshot.png > > > See the attached screenshots - some text boxes cannot be read as the background and text are both dark. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18224) Table Selection has poor performance if "Verify Database Connection" is checked in previous step

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18224?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-18224: -------------------------------- Assignee: George Gastaldi > Table Selection has poor performance if "Verify Database Connection" is checked in previous step > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-18224 > URL: https://issues.jboss.org/browse/JBIDE-18224 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.CR1 > Reporter: Pavol Srna > Assignee: George Gastaldi > Priority: Critical > Labels: respin-a > Fix For: 4.2.0.CR2, 4.3.0.Alpha1 > > > If the "Verify Database Connection" *is checked* then there is very *poor performance* in the next step during tables selection on JPA: Generate Entities From Tables wizard. > I don't understand what is going on behind the scenes - but there is for sure some communication with DB happening. Not sure if this is necessary as the list of tables is read correctly and imho the list should be just checked if there is at least one table selected. > It works *without performance problems* if "Verify Database Connection" was *not checked* in previous step. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18284) Broken history in Forge console

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18284?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-18284: -------------------------------- Assignee: Koen Aers > Broken history in Forge console > ------------------------------- > > Key: JBIDE-18284 > URL: https://issues.jboss.org/browse/JBIDE-18284 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.Beta3 > Environment: Windows 7, Eclipse Luna > Reporter: Vineet Reynolds > Assignee: Koen Aers > Priority: Critical > Fix For: 4.2.0.CR1 > > > When I press the up arrow key, instead of seeing the previous entry, I see a strange character {{à}}. Pressing the key multiple times appends more characters to the console, instead of cycling through the history entries multiple times. > This occurs only on Windows, and not on Linux (Fedora 20) or Mac. > History appears to be recorded correctly though. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18287) Seam project fails to deploy after IDE restart

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18287?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18287: ----------------------------------- Component/s: server > Seam project fails to deploy after IDE restart > ---------------------------------------------- > > Key: JBIDE-18287 > URL: https://issues.jboss.org/browse/JBIDE-18287 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: seam2, server > Affects Versions: 4.2.0.CR1 > Reporter: Martin Malina > > When you create a seam web project and deploy to EAP 5.2, then stop the server, restart JBDS and start the server again, the project fails to deploy properly: > {code} > 10:55:27,380 INFO [config] Initializing Mojarra (1.2_13-b01-FCS) for context '/seamproj' > 10:55:27,900 INFO [ServletContextListener] Welcome to Seam 2.2.6.EAP5 > 10:55:28,862 WARN [PersistentPermissionResolver] no permission store available - please install a PermissionStore with the name 'org.jboss.seam.security.jpaPermissionStore' if persistent permissions are required. > 10:55:28,961 INFO [ProfileServiceBootstrap] Loading profile: ProfileKey@6d4879f2[domain=default, server=default, name=default] > 10:55:28,962 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): > DEPLOYMENTS MISSING DEPENDENCIES: > Deployment "persistence.unit:unitName=seamproj.war#seamproj" is missing the following dependencies: > Dependency "jboss.jca:name=seamprojDatasource,service=DataSourceBinding" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.jca:name=seamprojDatasource,service=DataSourceBinding' **") > DEPLOYMENTS IN ERROR: > Deployment "jboss.jca:name=seamprojDatasource,service=DataSourceBinding" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.jca:name=seamprojDatasource,service=DataSourceBinding' ** > 10:55:28,968 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-localhost%2F127.0.0.1-8080 > 10:55:28,982 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-localhost%2F127.0.0.1-8009 > 10:55:28,988 INFO [ServerImpl] JBoss (Microcontainer) [5.2.0 (build: SVNTag=JBPAPP_5_2_0 date=201211232041)] Started in 15s:311ms > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18287) Seam project fails to deploy after IDE restart

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18287?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18287: ----------------------------------- Fix Version/s: 4.2.0.CR1 > Seam project fails to deploy after IDE restart > ---------------------------------------------- > > Key: JBIDE-18287 > URL: https://issues.jboss.org/browse/JBIDE-18287 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: seam2, server > Affects Versions: 4.2.0.CR1 > Reporter: Martin Malina > Fix For: 4.2.0.CR1 > > > When you create a seam web project and deploy to EAP 5.2, then stop the server, restart JBDS and start the server again, the project fails to deploy properly: > {code} > 10:55:27,380 INFO [config] Initializing Mojarra (1.2_13-b01-FCS) for context '/seamproj' > 10:55:27,900 INFO [ServletContextListener] Welcome to Seam 2.2.6.EAP5 > 10:55:28,862 WARN [PersistentPermissionResolver] no permission store available - please install a PermissionStore with the name 'org.jboss.seam.security.jpaPermissionStore' if persistent permissions are required. > 10:55:28,961 INFO [ProfileServiceBootstrap] Loading profile: ProfileKey@6d4879f2[domain=default, server=default, name=default] > 10:55:28,962 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): > DEPLOYMENTS MISSING DEPENDENCIES: > Deployment "persistence.unit:unitName=seamproj.war#seamproj" is missing the following dependencies: > Dependency "jboss.jca:name=seamprojDatasource,service=DataSourceBinding" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.jca:name=seamprojDatasource,service=DataSourceBinding' **") > DEPLOYMENTS IN ERROR: > Deployment "jboss.jca:name=seamprojDatasource,service=DataSourceBinding" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.jca:name=seamprojDatasource,service=DataSourceBinding' ** > 10:55:28,968 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-localhost%2F127.0.0.1-8080 > 10:55:28,982 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-localhost%2F127.0.0.1-8009 > 10:55:28,988 INFO [ServerImpl] JBoss (Microcontainer) [5.2.0 (build: SVNTag=JBPAPP_5_2_0 date=201211232041)] Started in 15s:311ms > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18293) New seam with new version is not selected as a default runtime envirnment for its version

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18293?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-18293: -------------------------------------- Assignee: Daniel Azarov (was: Alexey Kazakov) > New seam with new version is not selected as a default runtime envirnment for its version > ----------------------------------------------------------------------------------------- > > Key: JBIDE-18293 > URL: https://issues.jboss.org/browse/JBIDE-18293 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: seam2 > Affects Versions: 4.2.0.CR1 > Reporter: Radoslav Rábara > Assignee: Daniel Azarov > Priority: Optional > Fix For: 4.3.x > > > If there is a seam runtime environment, then there has to be also defined a default runtime environment for its version. > However, when a new seam is being added, which has a version that has not defined runtime environment, then the seam will be added but it will not be checked (marked as default for its version). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18293) New seam with new version is not selected as a default runtime envirnment for its version

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18293?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-18293: ---------------------------------------- This is not something new. You don't have check any default Seam runtime when you create it in Preferences. If you didn't select any Seam runtime as a default one explicitly then JBT will did it for you as soon as you use it in New Seam Project wizard. For example you created two Seam 2.3 runtimes in Preferences. No defaults one. Then you invoke a new Seam project wizard. It will pick up the first Seam runtime. The runtime you used in this wizard will be set as default then. > New seam with new version is not selected as a default runtime envirnment for its version > ----------------------------------------------------------------------------------------- > > Key: JBIDE-18293 > URL: https://issues.jboss.org/browse/JBIDE-18293 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: seam2 > Affects Versions: 4.2.0.CR1 > Reporter: Radoslav Rábara > Assignee: Alexey Kazakov > Priority: Optional > Fix For: 4.3.x > > > If there is a seam runtime environment, then there has to be also defined a default runtime environment for its version. > However, when a new seam is being added, which has a version that has not defined runtime environment, then the seam will be added but it will not be checked (marked as default for its version). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 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 September 2014