December 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-11172) Database Development: Postgres 9.1 tables are not listed

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11172?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-11172: ---------------------------------- Assignee: Koen Aers (was: Brian Fitzpatrick) > Database Development: Postgres 9.1 tables are not listed > -------------------------------------------------------- > > Key: JBIDE-11172 > URL: https://issues.jboss.org/browse/JBIDE-11172 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate, upstream > Environment: Mac OS X Lion > Reporter: Burr Sutter > Assignee: Koen Aers > Priority: Critical > Fix For: 4.5.0.AM1 > > Attachments: Screen Shot 2012-03-05 at 7.52.01 PM.png, Screen Shot 2012-03-05 at 7.55.21 PM.png, Screen Shot 2012-03-05 at 8.00.22 PM.png, Screen Shot 2012-03-05 at 8.00.38 PM.png, pagila-ds.xml, postgresql-9.1-901.jdbc4.jar > > > Postgres 9.1 - connection to a pagila database schema does not return a list of tables in the database explorer, nor in the Hibernate configuration. See attached screenshots. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3866) vagrant up failed due to rsync error, eclipse tooling confused about state of cdk server

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3866?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3866: ----------------------------- Fix Version/s: 10.3.0.AM1 (was: 10.2.0.GA) > vagrant up failed due to rsync error, eclipse tooling confused about state of cdk server > ---------------------------------------------------------------------------------------- > > Key: JBDS-3866 > URL: https://issues.jboss.org/browse/JBDS-3866 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: cdk > Affects Versions: 9.1.0.Beta1 > Environment: Windows 7/64 bit. > (previous installs of CDK and dependencies) > Reporter: Robert Terzi > Assignee: Rob Stryker > Fix For: 10.3.0.AM1 > > > vagrant up through the CDK server tooling failed because of an rsync problem. The tooling lost track of the state of the vagrant box. The vagrant box couldn't be stopped from inside of Eclipse. > The vagrant up failed because of an error with rsync. Something was confused about the user's home directory. It was trying to write to /home/username/.ssh, however, $HOME isn't /home/username, it's /cygdrive/c/Users/username, so /home/username/ doesn't exist. > The CDK server was shown as 'Started, Sychronized'. > The error message appeared in the server console tab. However the stop button wouldn't work. Provisioning had never finished so the OpenShift connection wasn't working either. > Synchronized seems misleading here, since no files had been sync'd yet. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11172) Database Development: Postgres 9.1 tables are not listed

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11172?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-11172: ------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.1.x) > Database Development: Postgres 9.1 tables are not listed > -------------------------------------------------------- > > Key: JBIDE-11172 > URL: https://issues.jboss.org/browse/JBIDE-11172 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate, upstream > Environment: Mac OS X Lion > Reporter: Burr Sutter > Assignee: Brian Fitzpatrick > Priority: Critical > Fix For: 4.5.0.AM1 > > Attachments: Screen Shot 2012-03-05 at 7.52.01 PM.png, Screen Shot 2012-03-05 at 7.55.21 PM.png, Screen Shot 2012-03-05 at 8.00.22 PM.png, Screen Shot 2012-03-05 at 8.00.38 PM.png, pagila-ds.xml, postgresql-9.1-901.jdbc4.jar > > > Postgres 9.1 - connection to a pagila database schema does not return a list of tables in the database explorer, nor in the Hibernate configuration. See attached screenshots. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10116) Issues that affect AS7/EAP integration to tools

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10116?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-10116: ------------------------------------ [~rob.stryker] can you check if this is still relevant > Issues that affect AS7/EAP integration to tools > ----------------------------------------------- > > Key: JBIDE-10116 > URL: https://issues.jboss.org/browse/JBIDE-10116 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Blocker > Labels: f2f2012 > Fix For: 4.4.3.AM1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10116) Issues that affect AS7/EAP integration to tools

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10116?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-10116: ------------------------------- Fix Version/s: 4.4.3.AM1 (was: 4.4.x) > Issues that affect AS7/EAP integration to tools > ----------------------------------------------- > > Key: JBIDE-10116 > URL: https://issues.jboss.org/browse/JBIDE-10116 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Blocker > Labels: f2f2012 > Fix For: 4.4.3.AM1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-9405) Add Preview step to maven profile dialog

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-9405?page=com.atlassian.jira.plugin... ] Jeff MAURY updated JBIDE-9405: ------------------------------ Fix Version/s: 4.5.0.AM1 (was: 3.3.x) > Add Preview step to maven profile dialog > ---------------------------------------- > > Key: JBIDE-9405 > URL: https://issues.jboss.org/browse/JBIDE-9405 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Reporter: Max Rydahl Andersen > Assignee: Alexey Kazakov > Fix For: 4.5.0.AM1 > > > Especially for multiple projects it sometimes feel unsafe to click ok, suggest that we add a Preview... button similar to what is seen under Refactoring that will show the list of projects that will be changed/updated. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18848) setup tests for ide-config.properties

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18848?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18848: ------------------------------- Labels: releasework (was: ) > setup tests for ide-config.properties > ------------------------------------- > > Key: JBIDE-18848 > URL: https://issues.jboss.org/browse/JBIDE-18848 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, common > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Labels: releasework > Fix For: 4.4.2.Final > > > JBIDE-18837 and other jiras showed that ide-config.properties risk having errors introduced into it. > we should have a test that runs every day to check if it is still consistent. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-4920) New Hibernate Console Configuration File (cfg.xml) file doesn't save state for Classpath tab in New Hibernate Console Configuration Step after '<Back' is pressed

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-4920?page=com.atlassian.jira.plugin... ] Jeff MAURY updated JBIDE-4920: ------------------------------ Fix Version/s: 4.5.0.AM1 (was: 4.3.x) > New Hibernate Console Configuration File (cfg.xml) file doesn't save state for Classpath tab in New Hibernate Console Configuration Step after '<Back' is pressed > ----------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-4920 > URL: https://issues.jboss.org/browse/JBIDE-4920 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 3.1.0.M4 > Reporter: Denis Golovin > Assignee: Koen Aers > Priority: Trivial > Fix For: 4.5.0.AM1 > > > 1. EXECUTE: Create Java Project > 2. EXECUTE: Select Java Project from step 1 and invoke New Hibernate Configuration file Wizard > 3. EXECUTE: Go through all steps to New Hibernate Console Configuration step > 4. EXECUTE: Select 'Classpath' tab, remove 'default classpath' entry > 5. EXECUTE: Press '<Back' > 6. EXECUTE: Press 'Next>' and select 'Classpath' tab > 7. ASSERT: State is the same as it was after step 4 above executed > Now it restores default values -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-8849) JPA project revalidation after export to db

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8849?page=com.atlassian.jira.plugin... ] Jeff MAURY reassigned JBIDE-8849: --------------------------------- Assignee: Koen Aers > JPA project revalidation after export to db > ------------------------------------------- > > Key: JBIDE-8849 > URL: https://issues.jboss.org/browse/JBIDE-8849 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: hibernate, upstream > Affects Versions: 3.2.1.M1 > Environment: JBDS 4.1.0 m1 H359 > Reporter: Jiri Peterka > Assignee: Koen Aers > Labels: jpa > Fix For: 4.5.0.AM1 > > > 1. Create datasource and open it > 2. Let's have JPA Project referenced datasource from step above > 3. Create entity M with table name Z, you'll get Table "Z" cannot be resolved > 4. Project -> JPA Tools -> Generate Tables from Entities with "Check Export to database" selected > 5. Finish > After doing this project entity is not yet valid > It would be nice, if connection could be refreshed and code revalidated automatically after export to db (it could be also configurable if desired) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-8849) JPA project revalidation after export to db

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8849?page=com.atlassian.jira.plugin... ] Jeff MAURY updated JBIDE-8849: ------------------------------ Fix Version/s: 4.5.0.AM1 (was: 4.3.x) > JPA project revalidation after export to db > ------------------------------------------- > > Key: JBIDE-8849 > URL: https://issues.jboss.org/browse/JBIDE-8849 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: hibernate, upstream > Affects Versions: 3.2.1.M1 > Environment: JBDS 4.1.0 m1 H359 > Reporter: Jiri Peterka > Assignee: Koen Aers > Labels: jpa > Fix For: 4.5.0.AM1 > > > 1. Create datasource and open it > 2. Let's have JPA Project referenced datasource from step above > 3. Create entity M with table name Z, you'll get Table "Z" cannot be resolved > 4. Project -> JPA Tools -> Generate Tables from Entities with "Check Export to database" selected > 5. Finish > After doing this project entity is not yet valid > It would be nice, if connection could be refreshed and code revalidated automatically after export to db (it could be also configurable if desired) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 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 December 2016