March 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16919) Visual Preview: create navigation from View to Editor

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16919?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov updated JBIDE-16919: ------------------------------------------- Assignee: Ilya Buziuk > Visual Preview: create navigation from View to Editor > ----------------------------------------------------- > > Key: JBIDE-16919 > URL: https://issues.jboss.org/browse/JBIDE-16919 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: visual-page-editor-core > Reporter: Konstantin Marmalyukov > Assignee: Ilya Buziuk > Priority: Critical > Fix For: 4.2.0.Beta2 > > > We need to have navigation from View to Editor via click on element in view -> select it in Editor. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2972) Verify findbugs/2.0.3.20131122-15027 with JBDS 8.0

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-2972?page=com.atlassian.jira.plugin.... ] Martin Malina reassigned JBDS-2972: ----------------------------------- Assignee: Nick Boldt (was: Martin Malina) Hey Nick, this is a dup of JBDS-2938 - I already verified the newer version there. As discussed earlier with Max and others, in such a case when it's just a minor version upgrade (2.0.2 -> 2.0.3) and everything seems to work, there is no reason not to upgrade. > Verify findbugs/2.0.3.20131122-15027 with JBDS 8.0 > --------------------------------------------------- > > Key: JBDS-2972 > URL: https://issues.jboss.org/browse/JBDS-2972 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: 3rd-party-certification > Affects Versions: 8.0.0.Beta1 > Reporter: Len DiMaggio > Assignee: Nick Boldt > Fix For: 8.0.0.Beta1 > > > 1. Decide if we want/need a newer version, and WHY. > 2. Document WHY (how this new version is better / fixes existing problems, etc.) > 3. If it's decided to pull a newer version, use this URL for the newer bits: > http://download.jboss.org/jbosstools/updates/requirements/findbugs/2.0.3.... > 4. Once approved, assign this JIRA to Nick Boldt so the new bits can be pushed into the Central TP site. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-16928) Forge2 runtime should be selected by default in Forge Console view

by Pavol Srna (JIRA)

Pavol Srna created JBIDE-16928: ---------------------------------- Summary: Forge2 runtime should be selected by default in Forge Console view Key: JBIDE-16928 URL: https://issues.jboss.org/browse/JBIDE-16928 Project: Tools (JBoss Tools) Issue Type: Bug Components: forge Affects Versions: 4.2.0.Beta1 Reporter: Pavol Srna Fix For: 4.2.0.Beta1 If I understand it correctly - as per JBDS requirements - Forge2 should be default and silently replace Forge1 (not sure if it applies also to JBT - but I think so) So I suppose that opening Forge Console view will have Forge2 selected by default. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-16928) Forge2 runtime should be selected by default in Forge Console view

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16928?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-16928: ------------------------------- Description: If I understand it correctly - as per JBDS requirements - Forge2 should be used by default and silently replace Forge1 (not sure if it applies also to JBT - but I think so) So I suppose that opening Forge Console view will have Forge2 selected by default. was: If I understand it correctly - as per JBDS requirements - Forge2 should be default and silently replace Forge1 (not sure if it applies also to JBT - but I think so) So I suppose that opening Forge Console view will have Forge2 selected by default. > Forge2 runtime should be selected by default in Forge Console view > ------------------------------------------------------------------ > > Key: JBIDE-16928 > URL: https://issues.jboss.org/browse/JBIDE-16928 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.Beta1 > Reporter: Pavol Srna > Fix For: 4.2.0.Beta1 > > > If I understand it correctly - as per JBDS requirements - Forge2 should be used by default and silently replace Forge1 (not sure if it applies also to JBT - but I think so) > So I suppose that opening Forge Console view will have Forge2 selected by default. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-260) Teiid designer server management tasks fail for JBDS 7.1.1.GA + JBDSIS 7.0.1.CR2

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/JBTIS-260?page=com.atlassian.jira.plugin.... ] Paul Richardson commented on JBTIS-260: --------------------------------------- Designer has for some time assumed a certain id for the Teiid Driver. When a JDBC connection is requested (either previewing or executing), the driver for the driver id is requested from eclipse's Driver Manager. If no driver can be found then Designer creates a new driver based on the connection properties provided during preview or VDB execution. This driver is pretty sparse in not even having a template and this is the problem. Investigations (by [~lfabriko]) have dug up [this|https://github.com/eclipse/datatools.connectivity/commit/c7d5a3632e2...] change in the connectivity plugin. This has tightened up the JDBCConnection class to ensure that the driver selected for the JDBC connection is first validated using the Driver Validator. However, the driver validator assumes the driver should have a template and thereby throws the exception shown above where the template is null. Designer should fix this by ensuring that one of the 3 teiid drivers provided are used for the JDBC connection as there should be no need to create a new one. This will bypass the problem with the created sparse driver and ensure that the correct driver is used for the JDBC query. > Teiid designer server management tasks fail for JBDS 7.1.1.GA + JBDSIS 7.0.1.CR2 > -------------------------------------------------------------------------------- > > Key: JBTIS-260 > URL: https://issues.jboss.org/browse/JBTIS-260 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: teiid > Environment: JBDS 7.1.1.GA, JBDSIS 7.0.1.CR2, server DV6 GA > Reporter: Lucie Fabrikova > Assignee: Paul Richardson > Priority: Blocker > Attachments: DriverValidator-1.2.11 > > > In teiid designer, start server latest DV6 GA and create new model project. Create some source model. > - preview of data in table causes error with empty stack trace, development perspective is not opened > - create and execute vdb: development perspective is opened, but vdb is not connected; trying to connect causes NPE: > java.lang.NullPointerException > at org.eclipse.datatools.connectivity.drivers.DriverValidator.validateJarListFiles(DriverValidator.java:161) > at org.eclipse.datatools.connectivity.drivers.DriverValidator.isValid(DriverValidator.java:92) > at org.eclipse.datatools.connectivity.drivers.jdbc.JDBCConnection.getDriverDefinitionJarPaths(JDBCConnection.java:217) > at org.eclipse.datatools.connectivity.drivers.jdbc.JDBCConnection.getJdbcDriverJars(JDBCConnection.java:169) > at org.eclipse.datatools.connectivity.drivers.jdbc.JDBCConnection.<init>(JDBCConnection.java:67) > at org.teiid.datatools.connectivity.TeiidJDBCConnection.<init>(TeiidJDBCConnection.java:31) > at org.teiid.datatools.connectivity.TeiidJDBCConnectionFactory.createConnection(TeiidJDBCConnectionFactory.java:21) > at org.eclipse.datatools.connectivity.internal.ConnectionFactoryProvider.createConnection(ConnectionFactoryProvider.java:83) > at org.eclipse.datatools.connectivity.internal.ConnectionProfile.createConnection(ConnectionProfile.java:359) > at org.eclipse.datatools.connectivity.sqm.internal.core.connection.ConnectionInfoImpl.initializeJDBCConnection(ConnectionInfoImpl.java:705) > at org.eclipse.datatools.connectivity.sqm.internal.core.connection.ConnectionInfoImpl.<init>(ConnectionInfoImpl.java:690) > at org.eclipse.datatools.connectivity.sqm.internal.core.connection.ConnectionFactory.createConnection(ConnectionFactory.java:38) > at org.eclipse.datatools.connectivity.sqm.core.SQMConnectionFactory.createConnection(SQMConnectionFactory.java:45) > at org.eclipse.datatools.connectivity.sqm.internal.core.connection.ConnectionFactory.createConnection(ConnectionFactory.java:59) > at org.eclipse.datatools.connectivity.internal.ConnectionFactoryAdapterProvider.createConnection(ConnectionFactoryAdapterProvider.java:114) > at org.eclipse.datatools.connectivity.internal.ManagedConnection.createConnection(ManagedConnection.java:163) > at org.eclipse.datatools.connectivity.internal.CreateConnectionJob.run(CreateConnectionJob.java:56) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-16927) Implement navigation between source and visual tabs

by Konstantin Marmalyukov (JIRA)

Konstantin Marmalyukov created JBIDE-16927: ---------------------------------------------- Summary: Implement navigation between source and visual tabs Key: JBIDE-16927 URL: https://issues.jboss.org/browse/JBIDE-16927 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: visual-page-editor-core Reporter: Konstantin Marmalyukov Fix For: 4.2.0.Beta2 We need to have visual/source navigation for visual editor like in view -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-16926) Add refresh buttons to new implementation of visual editor

by Konstantin Marmalyukov (JIRA)

Konstantin Marmalyukov created JBIDE-16926: ---------------------------------------------- Summary: Add refresh buttons to new implementation of visual editor Key: JBIDE-16926 URL: https://issues.jboss.org/browse/JBIDE-16926 Project: Tools (JBoss Tools) Issue Type: Sub-task Reporter: Konstantin Marmalyukov Refresh buttons like we have in view also must be in editor -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-16716) No JAX-RS problems when importing a project that contains HTTPMethod annotation without @Target and @Retention

by Radoslav Rábara (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16716?page=com.atlassian.jira.plugi... ] Radoslav Rábara commented on JBIDE-16716: ----------------------------------------- The bug was resolved in JBIDE-15428 but the JIRA had two fix versions. JIRA was closed after verifying with JBT 4.1.1.Beta1 but before verifying with JBT 4.2.0.Alpha1. So I cloned the original JIRA to have only one fix version for each JIRA. > No JAX-RS problems when importing a project that contains HTTPMethod annotation without @Target and @Retention > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-16716 > URL: https://issues.jboss.org/browse/JBIDE-16716 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.1.0.Final > Reporter: Radoslav Rábara > Assignee: Xavier Coulon > Fix For: 4.2.0.Alpha1 > > > After importing Dynamic Web Project with JAX-RS support with HTTPMethod annotation without @Target and @Retention annotations, there is no error. > This looks like a regression of JBIDE-12690. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-16716) No JAX-RS problems when importing a project that contains HTTPMethod annotation without @Target and @Retention

by Radoslav Rábara (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16716?page=com.atlassian.jira.plugi... ] Radoslav Rábara closed JBIDE-16716. ----------------------------------- Verified in JBDS 8.0.0 Beta1-v20140323-1410-B78 > No JAX-RS problems when importing a project that contains HTTPMethod annotation without @Target and @Retention > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-16716 > URL: https://issues.jboss.org/browse/JBIDE-16716 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.1.0.Final > Reporter: Radoslav Rábara > Assignee: Xavier Coulon > Fix For: 4.2.0.Alpha1 > > > After importing Dynamic Web Project with JAX-RS support with HTTPMethod annotation without @Target and @Retention annotations, there is no error. > This looks like a regression of JBIDE-12690. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-16924) Forge2: Project is not imported into IDE

by Pavol Srna (JIRA)

Pavol Srna created JBIDE-16924: ---------------------------------- Summary: Forge2: Project is not imported into IDE Key: JBIDE-16924 URL: https://issues.jboss.org/browse/JBIDE-16924 Project: Tools (JBoss Tools) Issue Type: Bug Components: forge Affects Versions: 4.2.0.Beta1 Reporter: Pavol Srna Priority: Critical Fix For: 4.2.0.Beta1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

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 March 2014