August 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-5728) Enhance OpenOn for the name param of some JSF 2.0 tags (add JAR files and i18n support)

by Yahor Radtsevich (JIRA)

Enhance OpenOn for the name param of some JSF 2.0 tags (add JAR files and i18n support) ---------------------------------------------------------------------------------------- Key: JBIDE-5728 URL: https://jira.jboss.org/jira/browse/JBIDE-5728 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: jsp/jsf/xml source editing Affects Versions: 3.1.0.CR1 Reporter: Yahor Radtsevich Assignee: Alexey Kazakov Fix For: 3.2.next JSF 2.0 allows the following tags to refer to the resources: h:outputStylesheet name="RESOURCE_NAME" h:outputScript name="RESOURCE_NAME" h:graphicImage name="RESOURCE_NAME" This is quotation from the JSF 2.0 Documentation (http://java.sun.com/javaee/6/docs/api/javax/faces/application/ResourceHan... ): The default implementation must support packaging resources in the web application root under the path resources/<resourceIdentifier> relative to the web app root. For the default implementation, resources packaged in the classpath must reside under the JAR entry name META-INF/resources/<resourceIdentifier> <resourceIdentifier> consists of several segments, specified as follows. [localePrefix/][libraryName/][libraryVersion/]resourceName[/resourceVersion] The HTML Editor supports OpenOn only for the resources which are placed in WEB_ROOT/resources/[libraryName/]resourceName . There is no support for: 1. JAR files 2. Locale 3. Library version 4. Resource version The support should be added. Also see: JBIDE-5382. -- 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

14 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-873) Code assist does not work for style attribute of jsf tag

by Adrian Mitev (JIRA)

Code assist does not work for style attribute of jsf tag -------------------------------------------------------- Key: JBIDE-873 URL: http://jira.jboss.com/jira/browse/JBIDE-873 Project: JBoss Tools Issue Type: Bug Environment: rhds beta 1, jdk 1.5_0.12, windows xp Reporter: Adrian Mitev Priority: Minor In style attribute of normal html tags code assist works, in jsf tags it doesn't. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

6
12
0 / 0

[JBoss JIRA] Created: (JBIDE-5921) Template Support in CA

by Maxim Areshkau (JIRA)

Template Support in CA ---------------------- Key: JBIDE-5921 URL: https://jira.jboss.org/jira/browse/JBIDE-5921 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: jsp/jsf/xml source editing Affects Versions: 3.1.0.CR1 Reporter: Maxim Areshkau Assignee: Maxim Areshkau Fix For: 3.2.next Attachments: CA_for_INSERT_ATTRIBUTE.png #1 import http://download.jboss.com/jboss-richfaces/richfaces-demo-4.0.0.ALPHA1-tom... #2 open welcome.xhtml #3 put cursor on <ui:define name="|""> ASSERT body should showed as CA proposal -- 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

14 years, 6 months

3
6
0 / 0

[JBoss JIRA] Created: (TOOLSDOC-70) Option to specify the project(s) name in the "Seam Web project" wizard

by Svetlana mukhina (JIRA)

Option to specify the project(s) name in the "Seam Web project" wizard ---------------------------------------------------------------------- Key: TOOLSDOC-70 URL: https://jira.jboss.org/jira/browse/TOOLSDOC-70 Project: Documentation for JBoss Tools/Developer Studio Issue Type: Task Security Level: Public (Everyone can see) Components: GettingStartedGuide, Seam Affects Versions: 3.0.0.GA Reporter: Svetlana mukhina Assignee: Svetlana mukhina Fix For: 3.0.1.GA Update screenshots and add the description -- 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

14 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-3795) Hibernate Config view cannot create JPA based configuration with @GeneratedValue using a @GenericGenerator

by Bob Thule (JIRA)

Hibernate Config view cannot create JPA based configuration with @GeneratedValue using a @GenericGenerator ---------------------------------------------------------------------------------------------------------- Key: JBIDE-3795 URL: https://jira.jboss.org/jira/browse/JBIDE-3795 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.0.0.CR2 Environment: Hibernate Tools 3.2.4.GA-N200902101801, Java Persistence API Tools 2.1.0.v200812180210 Reporter: Bob Thule This may be related to issue JBIDE-3636. https://jira.jboss.org/jira/browse/JBIDE-3636 With a @GenericGenerator declared as: @GenericGenerator(name = "SeqBase",... ) //either in package-info.java or on the class and used with: @GeneratedValue(generator = "SeqBase") private Long id; when in the "Hibernate Config" view and the hibernate configuration is trying to be displayed or rebuilt, Eclipse gives the following exception: org.hibernate.console.HibernateConsoleRuntimeException: Could not create JPA based Configuration Could not create JPA based Configuration <No message> java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException: <no message> java.lang.reflect.InvocationTargetException javax.persistence.PersistenceException: org.hibernate.AnnotationException: Unknown Id.generator: SeqBase org.hibernate.AnnotationException: Unknown Id.generator: SeqBase org.hibernate.AnnotationException: Unknown Id.generator: SeqBase Unknown Id.generator: SeqBase -- 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

14 years, 6 months

4
21
0 / 0

[JBoss JIRA] Created: (JBDS-1239) 3rd party cert: PMD

by Max Rydahl Andersen (JIRA)

3rd party cert: PMD ------------------- Key: JBDS-1239 URL: https://jira.jboss.org/browse/JBDS-1239 Project: Developer Studio (JBoss Developer Studio) Issue Type: Sub-task Reporter: Max Rydahl Andersen -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

4
13
0 / 0

[JBoss JIRA] Created: (JBDS-1235) 3rd party certification

by Max Rydahl Andersen (JIRA)

3rd party certification ----------------------- Key: JBDS-1235 URL: https://jira.jboss.org/browse/JBDS-1235 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: Requirements Reporter: Max Rydahl Andersen Priority: Blocker Fix For: 4.0.0.GA We should define what kind of certifications we want and then certify 3rd party plugins with JBDS Certifiaction could for example be for Groovy Plugin we know it installs, but beyond that there aren't any guarantees. For m2eclipse it would be the same with respect to installation but that we support the maven integration plugins and provide fixes for that - but not m2eclipse it self. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

4
13
0 / 0

[JBoss JIRA] Created: (JBDS-838) Find a better home for nightly and archiving of JBDS builds

by Max Rydahl Andersen (JIRA)

Find a better home for nightly and archiving of JBDS builds ----------------------------------------------------------- Key: JBDS-838 URL: https://jira.jboss.org/jira/browse/JBDS-838 Project: JBoss Developer Studio Issue Type: Task Components: Build Affects Versions: 3.0.0.M4 Reporter: Max Rydahl Andersen Assignee: Max Rydahl Andersen Priority: Critical For a while we have been archiving at an QA server located in ATL which is now in PHO but it only gives about 40 kb/s download from europe. Moving it to porkchop would help here since the main site has 80 kb/s and can be mirrored to Brno giving 120 kb/s. End result: 10-24hrs download times gets reduced to 1-2 hrs download for European devs. -- 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

14 years, 6 months

5
28
0 / 0

[JBoss JIRA] Created: (JBIDE-6537) Helios support for JBT v3.1.1

by Darryl Miles (JIRA)

Helios support for JBT v3.1.1 ----------------------------- Key: JBIDE-6537 URL: https://jira.jboss.org/browse/JBIDE-6537 Project: Tools (JBoss Tools) Issue Type: Task Components: Hibernate, Seam Affects Versions: 3.1.1 Reporter: Darryl Miles Assignee: Max Rydahl Andersen Both the "Hibernate Tools" and "Seam Tools" for JBT v3.1.1 have too narrow version requirements for com.ibm.icu to be compatible with Helios. Helios comes with com.ibm.icu v4.2.1 Currently the version requirements are set to [3.4.4,4.1.0) so this should be changed at a minimum to [3.4.4,4.3.0) to allow both these JBT components to install on top of Helios. However you should consider using an even wider version width of [3.4.4,5) since it is accepted practise that minor version increments are backwardly compatible and a major version change is potentially API breaking. This means that generally JBT should (and is expected to) work on all future versions of com.ibm.icu up until version 5 is released. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

4
7
0 / 0

[JBoss JIRA] Created: (JBIDE-5284) Warning related to incorrect Seam project name don't appear

by Aliaksey Nis (JIRA)

Warning related to incorrect Seam project name don't appear ----------------------------------------------------------- Key: JBIDE-5284 URL: https://jira.jboss.org/jira/browse/JBIDE-5284 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.1.0.CR1 Environment: WindowsXP SP2 JBoss Tools Version: 3.1.0.CR1 eclipse-SDK-3.5RC3-win32.zip Build id: JBossTools-Update-3.1.0.v200911251807N-H130-RC1 JRE 1.6 Reporter: Aliaksey Nis Priority: Optional Attachments: NoWarningSeam.JPG Related to JBIDE-5223 EXECUTE: New Seam project. EXECUTE: Input name "blahblah+". EXECUTE: Press next few times. ASSERT: At step "Web module" button Next is in disable state, due to incorrect project name. FAILURE: No warning appears. It appears only if you press Back, then Next again. Screenshot attached. -- 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

14 years, 7 months

7
10
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 August 2010