February 2012 - jbosstools-issues

[JBoss JIRA] Created: (TOOLSDOC-195) JBDS50_0015: Seam 3 documentation

by Isaac Rooskov (JIRA)

JBDS50_0015: Seam 3 documentation --------------------------------- Key: TOOLSDOC-195 URL: https://issues.jboss.org/browse/TOOLSDOC-195 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Task Security Level: Public (Everyone can see) Components: Seam Developer Tools Reference Guide Reporter: Isaac Rooskov Assignee: Isaac Rooskov Priority: Critical Fix For: 3.3.0.Final Tracking bug for documentation of the PRD requirement JBDS50_0015: Seam 3. Current status: Committed Description: New documentation for Seam 3 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
3
0 / 0

[JBoss JIRA] Created: (TOOLSDOC-202) JBDS50_0055: Arquillian documentation

by Isaac Rooskov (JIRA)

JBDS50_0055: Arquillian documentation ------------------------------------- Key: TOOLSDOC-202 URL: https://issues.jboss.org/browse/TOOLSDOC-202 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Task Security Level: Public (Everyone can see) Reporter: Isaac Rooskov Assignee: Isaac Rooskov Fix For: 3.3.0.Final Tracking bug for documentation of the PRD requirement JBDS50_0055: Arquillian Current status: Committed Description: New documentation for Arquillian -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (TOOLSDOC-201) JBDS50_0050: Dashboard documentation

by Isaac Rooskov (JIRA)

JBDS50_0050: Dashboard documentation ------------------------------------ Key: TOOLSDOC-201 URL: https://issues.jboss.org/browse/TOOLSDOC-201 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Task Security Level: Public (Everyone can see) Components: General documentation issues Reporter: Isaac Rooskov Assignee: Isaac Rooskov Fix For: 3.3.0.Final Tracking bug for documentation of the PRD requirement JBDS50_0050: Dashboard Current status: Committed Description: New documentation for the Dashboard -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

3
6
0 / 0

[JBoss JIRA] Created: (TOOLSDOC-198) JBDS50_0031: Hibernate 3 documentation

by Isaac Rooskov (JIRA)

JBDS50_0031: Hibernate 3 documentation -------------------------------------- Key: TOOLSDOC-198 URL: https://issues.jboss.org/browse/TOOLSDOC-198 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Task Security Level: Public (Everyone can see) Components: Hibernate Tools Reference Guide Reporter: Isaac Rooskov Assignee: Isaac Rooskov Fix For: 3.3.0.Final Tracking bug for documentation of the PRD requirement JBDS50_0031: Hibernate 3 Current status: Committed Description: New documentation for Hibernate 3 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (TOOLSDOC-197) JBDS50_0030: Hibernate 4 documentation

by Isaac Rooskov (JIRA)

JBDS50_0030: Hibernate 4 documentation -------------------------------------- Key: TOOLSDOC-197 URL: https://issues.jboss.org/browse/TOOLSDOC-197 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Task Security Level: Public (Everyone can see) Components: Hibernate Tools Reference Guide Reporter: Isaac Rooskov Assignee: Isaac Rooskov Fix For: 3.3.0.Final Tracking bug for documentation of the PRD requirement JBDS50_0030: Hibernate 4 Current status: Uncommitted Description: New documentation for Hibernate 4 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
3
0 / 0

[JBoss JIRA] (JBIDE-10531) Incorrect EL with brackets [] is dislpayed as correct

by Vlado Pakan (Created) (JIRA)

Incorrect EL with brackets [] is dislpayed as correct ----------------------------------------------------- Key: JBIDE-10531 URL: https://issues.jboss.org/browse/JBIDE-10531 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.3.0.M5 Environment: Linux 32 bit, Java Sun JDK 1.6, jbdevstudio 5.0.0.v201112150534M-H62-M Reporter: Vlado Pakan Assignee: Alexey Kazakov Fix For: 3.3.0.Beta1 Steps to reproduce: 1. Create JSF Kick Start with Facelets 2. Open inputname.xhtml page 3. Insert code <h:outputText value="#{msg['prompt'}" /> within <ui:define name="body"> with missing closing ']' Error: in Visual part of VPE is EL displayed evaluated value of EL #{msg['prompt']} i. e. 'Your Name:' Assert: it should display text #{msg['prompt'} because source code is not syntactically correct. There is warning about expected ']' but it's something what can be really easy missed and server is not displaying this page correctly. It will return error when trying to display this page. So VPE visual representation should also display this tag as not correct. -- 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

12 years, 4 months

7
20
0 / 0

[JBoss JIRA] Created: (JBIDE-8553) Generation of Arquillian @Deployment method

by Nicklas Karlsson (JIRA)

Generation of Arquillian @Deployment method ------------------------------------------- Key: JBIDE-8553 URL: https://issues.jboss.org/browse/JBIDE-8553 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Nicklas Karlsson Trying to assemble a minimal Arquillian test archive can be lots of work when the dependencies add up and you only notice the problems at deployment time. I would love to have a feature that would create the @Deployment method for you. It could (in theory) work like this: Somewhere in your test class from the context menu you could a) generate a new @Deployment method if none exist or b) add to the deployment method if it exists You could then pick one or more files to start from. The imports and references would be analyzed and a minimal set of classes would be added to the deployment archive code generated. If run again, the new tree would be merged with the existing one. Then comes the tricky part. Analyze the archives on the classpath and dig out which archives provide which classes. Further use Aether or some other maven api to find out the dependecy tree until all jars to be included are discovered. Example: Foo.java references Bar.java Bar.java references Tar.java Tar.java references Worksheet.class Foo.java is included in the generated @Deployment Bar.java is included Tar.java is included jxl.jar from the local repo is included since it is determined from the pom.xml through further investigation to provide Worksheet.class. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

5
13
0 / 0

[JBoss JIRA] Created: (JBIDE-8064) Variable initializer does not generate content for messages which use type attribute instead of element to declare the part.

by Marek Baluch (JIRA)

Variable initializer does not generate content for messages which use type attribute instead of element to declare the part. ---------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-8064 URL: https://issues.jboss.org/browse/JBIDE-8064 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.CR1 Reporter: Marek Baluch If a message is declared the following way: <message name="moderateRequestMessage"> <part name="moderateRequest" type="tns:complexType"/> </message> or <message name="simpleResponseMessage"> <part name="payload" type="xsd:string"/> </message> In the second case there's no need to generate any content. The assignment will work anyway. In these cases the variable initializer should not be triggered. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

6
17
0 / 0

[JBoss JIRA] (JBIDE-10736) Build hibernate tools with hibernate core 4.0.0.Final

by Dmitry Geraskov (JIRA)

Dmitry Geraskov created JBIDE-10736: --------------------------------------- Summary: Build hibernate tools with hibernate core 4.0.0.Final Key: JBIDE-10736 URL: https://issues.jboss.org/browse/JBIDE-10736 Project: Tools (JBoss Tools) Issue Type: Task Components: hibernate Affects Versions: 3.3.0.M5 Reporter: Dmitry Geraskov Assignee: Dmitry Geraskov Fix For: 3.3.0.Beta1 -- 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

12 years, 4 months

3
9
0 / 0

[JBoss JIRA] (JBIDE-10643) Support Hibernate3.6 in hibernate tools core

by Dmitry Geraskov (JIRA)

Dmitry Geraskov created JBIDE-10643: --------------------------------------- Summary: Support Hibernate3.6 in hibernate tools core Key: JBIDE-10643 URL: https://issues.jboss.org/browse/JBIDE-10643 Project: Tools (JBoss Tools) Issue Type: Task Components: hibernate Affects Versions: 3.3.0.M5 Reporter: Dmitry Geraskov Assignee: Dmitry Geraskov Fix For: 3.3.0.Beta1 -- 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

12 years, 4 months

3
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues February 2012