[JBoss JIRA] Created: (JBIDE-8621) provide multi-line comments in hql-editor
by nimo stephan (JIRA)
provide multi-line comments in hql-editor
-----------------------------------------
Key: JBIDE-8621
URL: https://issues.jboss.org/browse/JBIDE-8621
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Reporter: nimo stephan
According to https://issues.jboss.org/browse/JBIDE-6974, comments are provided, but only one-line-comments via --. This is a limitation!
Especially, multi-line-comments should be provided by /*comment*/.
/* . . . */ is supported in SQL.
Especially in hql-editor, multline comments are more sensefull than one-line-comments.
Imagine, I have 20 queries, I am forced to have 20 hql-editor instances in my ide!
This does not only cost RAM, it is also not user-friendly to handle 20 different hql-editors-instances instead of only one, in which the user can comment out different queries via multi-line.
Please provide a full support for comments in hql-editor, one-line AND multi-line comments.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] Created: (JBIDE-1611) hibernate reverce engeniering
by Vitali Yemialyanchyk (JIRA)
hibernate reverce engeniering
-----------------------------
Key: JBIDE-1611
URL: http://jira.jboss.com/jira/browse/JBIDE-1611
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Reporter: Vitali Yemialyanchyk
Assigned To: Vitali Yemialyanchyk
Priority: Minor
Fix For: LATER
Attachments: dialog.jpg
GUI -> Package - as I think this should be obligatory field - so user should get some message about it.
Of cource he could firstly run it - see result - then delete -> specify the package and run one again...
reveng. strategy -> I can't get it work - so should be some more questions here.
GUI -> Main & Exporters tab -> if the dialog small enough - some buttons and controls envisible -> in this case should be scrollbars were.
Generation result -> all files in one place. Domain model classes should be in one separate package and POJO classes in other. User should get possibility to specify this.
Other during generation process - generator simply rewrite my old files - should be some message here. rewrite all or just one - should be clear.
--
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
13 years, 5 months