JSF model/builder
-----------------
Key: JBIDE-5046
URL: https://jira.jboss.org/jira/browse/JBIDE-5046
Project: Tools (JBoss Tools)
Issue Type: Task
Components: JSF
Reporter: Alexey Kazakov
Assignee: Viacheslav Kabanovich
Fix For: LATER
We have to create JSF builder to JSF 2 artifacts into JSF model.
Such as:
- annotated manage beans
- resources
...
--
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
Ability to click through to resources specified as part of Shrinkwrap definition
--------------------------------------------------------------------------------
Key: JBIDE-6338
URL: https://jira.jboss.org/browse/JBIDE-6338
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: testing
Reporter: Pete Muir
With Shrinkwrap you can package a resource (such as web.xml) into the archive. Would be great to cmd-click on that resource and be taken to it.
--
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
Give error/warning on use of Class in a TestCase that are not found in the @Deployment
--------------------------------------------------------------------------------------
Key: JBIDE-6568
URL: https://jira.jboss.org/browse/JBIDE-6568
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: testing
Reporter: Aslak Knutsen
To help avoid trail and error of what to add to the @Deployment in Arquillian, tooling could verify that the classes used in the TestCase are in the defined @Deployment. If not found, it could be marked as a warning/error.
--
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
New Arquillian test wizard
--------------------------
Key: JBIDE-6318
URL: https://jira.jboss.org/browse/JBIDE-6318
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: testing
Reporter: Pete Muir
Create a new Arquillian test. Wizard would need to ask user to select between JUnit and TestNG (set a preffered one somewhere in prefs?), and then generate a class with boilerplate (@RunWith/extends), and a stub deployment.
--
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
View Arquillian Deployment
--------------------------
Key: JBIDE-6662
URL: https://jira.jboss.org/browse/JBIDE-6662
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: testing
Reporter: Aslak Knutsen
It should be possible to have a view that will show the exact ShrinkWrap archive Arquillian is deploying for the test given test case.
--
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
Add Arquillian Capabilities
---------------------------
Key: JBIDE-6319
URL: https://jira.jboss.org/browse/JBIDE-6319
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: testing
Reporter: Pete Muir
Ability to right click and select "Add Arquillian to project" - this should add the requisites libraries to the project
--
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
Add Maping files
----------------
Key: JBIDE-496
URL: http://jira.jboss.com/jira/browse/JBIDE-496
Project: JBoss Tools
Issue Type: Feature Request
Components: Hibernate Tools
Reporter: Krasimir Goutcev
Assigned To: Max Andersen
Possibility to add mapping lfiles as Exadel ORM Explorer
--
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
All futures that was in ORM Explorer
------------------------------------
Key: JBIDE-499
URL: http://jira.jboss.com/jira/browse/JBIDE-499
Project: JBoss Tools
Issue Type: Feature Request
Reporter: Krasimir Goutcev
- Open Mapping
- Edit Source
- Edit Mapping
- View Table
- Clear Mapping
- Remove persistent class
- rename class
--
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
EJB3 component wizards are not included in Beta3
------------------------------------------------
Key: JBIDE-911
URL: http://jira.jboss.com/jira/browse/JBIDE-911
Project: JBoss Tools
Issue Type: Feature Request
Components: ejb3
Affects Versions: 2.0.0.Beta3
Environment: all environments
Reporter: Tyronne Wickramarathne
Fix For: 2.0.0.Beta4
EJB3 component wizards are not included in Beta3 release. include EJB3 project creation from the IDE too.
--
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
Support webbeans typesafe xml schema
-------------------------------------
Key: JBIDE-3120
URL: https://jira.jboss.org/jira/browse/JBIDE-3120
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: webbeans
Reporter: Max Rydahl Andersen
Fix For: LATER
http://docs.jboss.org/webbeans/reference/1.0/en-US/html/xml.html
"The advantage of this approach is that you can write an XML schema
that prevents spelling errors in your XML document. It's even possible
for a tool to generate the XML schema automatically from the compiled
Java code. Or, an integrated development environment could perform the
same validation without the need for the explicit intermediate
generation step."
1) the RI will have a code->xsd generator for web-beans.xml; could maybe be used for validation....but requires that all classes can compile
2) we should have xml completions following the naming standard layed out by webbeans spec
--
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