March 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-10139) Help for Teiid Designer is missing

by Paul Nittel (Created) (JIRA)

Help for Teiid Designer is missing ---------------------------------- Key: JBIDE-10139 URL: https://issues.jboss.org/browse/JBIDE-10139 Project: Tools (JBoss Tools) Issue Type: Bug Components: Help Affects Versions: 3.2.2.M2 Environment: JBDS 4.1.1GA Reporter: Paul Nittel Assignee: Isaac Rooskov When Help > Contents is displayed, there is nothing pertaining to the Teiid Designer. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

11
27
0 / 0

[JBoss JIRA] Created: (JBIDE-8974) provide composite*.xml

by Nick Boldt (JIRA)

provide composite*.xml ---------------------- Key: JBIDE-8974 URL: https://issues.jboss.org/browse/JBIDE-8974 Project: Tools (JBoss Tools) Issue Type: Bug Components: testing Affects Versions: 3.3.0.M1 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 3.3.0.M2 create clone of http://download.jboss.org/jbosstools/builds/staging/_composite_/3.3.indigo/* with relative paths to dirs on disk (~/trunk/jmx/site/target/site/) so that locally built files can be used to test installation. Place this in ~/trunk/build/aggregate/site/ ? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5448) No CA path proposals for img src="" for whatsnew project

by Maxim Areshkau (JIRA)

No CA path proposals for img src="" for whatsnew project -------------------------------------------------------- Key: JBIDE-5448 URL: https://jira.jboss.org/jira/browse/JBIDE-5448 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.1.0.CR1 Reporter: Maxim Areshkau Assignee: Alexey Kazakov Fix For: 3.1.0.GA Attachments: Screenshot.png #1 import https://svn.jboss.org/repos/jbosstools/trunk/documentation/whatsnew project #2 open page vpe-news-3.1.0.CR1.html #3 set cursor in 63 <img src="images/3.0|" .../> ASSERT PATH proposals should be in CA -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

4
19
0 / 0

[JBoss JIRA] Created: (JBIDE-9639) using Tycho 0.13.0-SNAPSHOT, cannot resolve hibernate when building birt

by Nick Boldt (JIRA)

using Tycho 0.13.0-SNAPSHOT, cannot resolve hibernate when building birt ------------------------------------------------------------------------ Key: JBIDE-9639 URL: https://issues.jboss.org/browse/JBIDE-9639 Project: Tools (JBoss Tools) Issue Type: Bug Components: birt Affects Versions: 3.3.0.M4 Reporter: Nick Boldt Assignee: Snjezana Peco Fix For: 3.3.0.M4 $ mvn3 clean install -DtychoVersion=0.13.0-SNAPSHOT -U ERROR] /home/nboldt/eclipse/workspace-jboss/jbosstools_trunk/birt/plugins/org.jboss.tools.birt.oda/src/org/jboss/tools/birt/oda/impl/Parameter.java (at line 32):[-1,-1] [ERROR] hibernateTypes.put(TimestampType, Hibernate.TIMESTAMP); [ERROR] ^^^^^^^^^ [ERROR] Hibernate cannot be resolved to a variable [ERROR] [ERROR] /home/nboldt/eclipse/workspace-jboss/jbosstools_trunk/birt/plugins/org.jboss.tools.birt.oda/src/org/jboss/tools/birt/oda/impl/Parameter.java (at line 33):[-1,-1] [ERROR] hibernateTypes.put(BooleanType, Hibernate.BOOLEAN); [ERROR] ^^^^^^^^^^^^^^ [ERROR] Type cannot be resolved to a type [ERROR] [ERROR] /home/nboldt/eclipse/workspace-jboss/jbosstools_trunk/birt/plugins/org.jboss.tools.birt.oda/src/org/jboss/tools/birt/oda/impl/Parameter.java (at line 33):[-1,-1] [ERROR] hibernateTypes.put(BooleanType, Hibernate.BOOLEAN); [ERROR] ^^^^^^^^^ [ERROR] Hibernate cannot be resolved to a variable [ERROR] [ERROR] /home/nboldt/eclipse/workspace-jboss/jbosstools_trunk/birt/plugins/org.jboss.tools.birt.oda/src/org/jboss/tools/birt/oda/impl/Parameter.java (at line 90):[-1,-1] [ERROR] public Type getHibernateType() { [ERROR] ^^^^ [ERROR] Type cannot be resolved to a type [ERROR] [ERROR] /home/nboldt/eclipse/workspace-jboss/jbosstools_trunk/birt/plugins/org.jboss.tools.birt.oda/src/org/jboss/tools/birt/oda/impl/Parameter.java (at line 91):[-1,-1] [ERROR] return hibernateTypes.get(type); [ERROR] ^^^^^^^^^^^^^^ [ERROR] Type cannot be resolved to a type etc. This could be a problem w/ feature-feature or plugin-plugin dependencies not being clearly stated in the feature.xml or MANIFEST.MF files. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
3
0 / 0

[JBoss JIRA] (JBIDE-11323) Windows - ssh directory is missing a "." before "ssh"

by Burr Sutter (JIRA)

Burr Sutter created JBIDE-11323: ----------------------------------- Summary: Windows - ssh directory is missing a "." before "ssh" Key: JBIDE-11323 URL: https://issues.jboss.org/browse/JBIDE-11323 Project: Tools (JBoss Tools) Issue Type: Bug Environment: JBDS 5 Beta1 -Windows 7 Reporter: Burr Sutter Attachments: ssh_key_path.png The default directory in JBDS is "C:\Users\Burr\ssh" and on my machine it is "C:\Users\Burr\.ssh" - on a Mac JBDS defaults to /Users/burr/.ssh -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

4
10
0 / 0

[JBoss JIRA] (JBIDE-10047) Update site instructions are inaccurate for novice user

by Burr Sutter (Created) (JIRA)

Update site instructions are inaccurate for novice user ------------------------------------------------------- Key: JBIDE-10047 URL: https://issues.jboss.org/browse/JBIDE-10047 Project: Tools (JBoss Tools) Issue Type: Bug Environment: JBoss Tools 3.3.M4 Reporter: Burr Sutter http://download.jboss.org/jbosstools/updates/JBossTools-3.3.0.M4/ "To verify which sites are enabled, open Window > Preferences > Install/Update > Available Software Sites. To add sites, Click the Add... button, then right-click the link(s) below, copy the link(s), and paste them into Eclipse one by one as needed." If you follow this path, then you never seen the screen to check the box for "All JBoss Tools" therefore you do not actually receive/download JBoss Tools. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

9
10
0 / 0

[JBoss JIRA] Created: (JBDS-1799) Hide 3rd party features from JBDS 5 Extras site - only com.jboss.jbds.* features should be exposed

by Nick Boldt (JIRA)

Hide 3rd party features from JBDS 5 Extras site - only com.jboss.jbds.* features should be exposed -------------------------------------------------------------------------------------------------- Key: JBDS-1799 URL: https://issues.jboss.org/browse/JBDS-1799 Project: Developer Studio (JBoss Developer Studio) Issue Type: Enhancement Components: 3rdPartyDependencies, Build, updatesite Affects Versions: 4.1.0.CR4, 5.0.0.M2 Reporter: Nick Boldt Assignee: Nick Boldt Priority: Blocker Fix For: 4.1.0.GA, 5.0.0.M3 1. instead of including 3rd party features in com.jboss.jbds.* features, include contained plugins. 2. rewrite com.jboss.jbds.* features to list out contents so it's clear what versions of 3rd party stuff are included. Benefits: * anything installable from JBDS Extras site is a feature we build and maintain (and test and support). * to install any non-com.jboss 3rd party feature, must go to 3rd party site (or jboss.org community mirror). Because this is "off the reservation", it's not supported, and users' mileage may vary. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
10
0 / 0

[JBoss JIRA] (JBIDE-10048) All JBoss Tools is very confusing

by Burr Sutter (Created) (JIRA)

All JBoss Tools is very confusing --------------------------------- Key: JBIDE-10048 URL: https://issues.jboss.org/browse/JBIDE-10048 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Burr Sutter Attachments: Available_Software.png All JBoss Tools is very confusing. it is unclear to the novice user what checkboxes should be checked. I believe the right "subset" is - All JBoss Tools - Application Development - Maven Support - Web and Java EE Development Those 4 should be "All JBoss Tools" or "the Right Set of JBoss Tools" for the average user. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

12
53
0 / 0

[JBoss JIRA] Created: (JBDS-1562) SpringIDE has startup bug

by Max Rydahl Andersen (JIRA)

SpringIDE has startup bug -------------------------- Key: JBDS-1562 URL: https://issues.jboss.org/browse/JBDS-1562 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: Upstream Affects Versions: 4.0.0.GA Reporter: Max Rydahl Andersen Fix For: 4.0.x As found in JBDS-1518 there are a startup bug in SpringIDE/SpringSTS which triggers non-normal pluginloading and can cause problems for plugins depending on the "normal" plugin load sequence. For now we avoid it by not using latest version of SpringIDE but the version before that. Snjeza reproduced the problem on plain STS and its reported at https://issuetracker.springsource.com/browse/STS-1554 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

4
9
0 / 0

[JBoss JIRA] Created: (JBDS-1699) Product build should be able to source from upstream Updatesite build when set to RELEASE=Yes

by Nick Boldt (JIRA)

Product build should be able to source from upstream Updatesite build when set to RELEASE=Yes --------------------------------------------------------------------------------------------- Key: JBDS-1699 URL: https://issues.jboss.org/browse/JBDS-1699 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: installer Affects Versions: 5.0.0.M2 Reporter: Nick Boldt Fix For: 5.0.0.M3 When RELEASE=Yes, zips are generated w/ a suffix such as http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_stable... When RELEASE=No, zips are generated w/ a static suffix: http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_stable... Currently, a number of files in JBDS product builder assume the filename for this file is static. For example, releng/org.jboss.ide.eclipse.releng/builders/jbds-all-package/build.properties, line 38, points at jar:file:${repoBaseLocation}/extras-Update-SNAPSHOT.zip!/ and cannot resolve variables like ${ZIPSUFFIX} or ${jbds.extra.build.archive} as defined in releng/org.jboss.ide.eclipse.releng/requirements/jbds-extra-update/build.properties. As such, this filename must currently be hard-coded and the upstream updatesite job must be set to RELEASE=No. Instead, any suffix should be supported via fetching the file's name from here: http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_stable... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
4
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 2012