[JBoss JIRA] Created: (JBIDE-8374) First expansion of Hibernate CC node is often unsuccessful
by Jiri Peterka (JIRA)
First expansion of Hibernate CC node is often unsuccessful
----------------------------------------------------------
Key: JBIDE-8374
URL: https://issues.jboss.org/browse/JBIDE-8374
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Hibernate
Affects Versions: 3.2.0.CR2 (tentative)
Environment: JBDS 4.0.0.CR3 H162, Linux 64
Reporter: Jiri Peterka
It's quite often experience that first expansion of Hibernate CC tree is often unsuccessful (nothing is expanded or empty tree)
Steps to replicate this can be various and it's not 100% reproducible because it happens only from time to tome.
For me it's often happenings with new workspace and first hibernate console and with newly started JBT/JBDS.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 11 months
[JBoss JIRA] Created: (JBIDE-8275) Composite components should be recognized in jar-files inside META-INF/resources/
by Viacheslav Kabanovich (JIRA)
Composite components should be recognized in jar-files inside META-INF/resources/
---------------------------------------------------------------------------------
Key: JBIDE-8275
URL: https://issues.jboss.org/browse/JBIDE-8275
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JSF
Affects Versions: 3.2.0.CR1
Reporter: Viacheslav Kabanovich
Assignee: Viacheslav Kabanovich
Fix For: 3.3.0.M1
Within project, composite components are located in folder %Web-root%/resources. - That is supported by JBoss Tools.
But besides, composite components may be located in used by the project external jars in folder META-INF/resources. - That should be implemented.
See http://community.jboss.org/message/583919#583919
JavaServerTM Faces Specification
2.6.1.2 Packaging Resources into the Classpath
For the default implementation, resources packaged in the classpath must reside under the JAR entry name:
META-INF/resources/<resourceIdentifier>
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 11 months
[JBoss JIRA] Created: (JBIDE-8623) Dynamic feature loading
by Jiri Peterka (JIRA)
Dynamic feature loading
-----------------------
Key: JBIDE-8623
URL: https://issues.jboss.org/browse/JBIDE-8623
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: core
Affects Versions: 3.2.0.Final
Reporter: Jiri Peterka
Goal is to make JBT/JBDS more modular and user friendly via dynamic features loading when they are really used. Not to have current state when unused features are present and loaded and some extra features needs to be installed via update site manually.
Expected state could look like:
* Present menu items for all provided actions (like New <any-type-of> Project)
* if selected for the first time, feature will be downloaded (if needed), installed and loaded without any special user interaction
* wizard (or any other action) will continue after that in situation
I see several related issues:
1. Seamless feature loading (currently after feature installation eclipse restart is usually needed which is not very usable for this)
2. Architecture (it could be quite challenging to implement dummy plug-in with some extensions like menus triggering feature post-loading)
3. Installation speed (currently all p2 operation are quite slow so I'm not sure if it is feasible)
Note: take this feature request as an early proposal. I guess many people would appreciate this kind of architecture and JBT/JBDS would become more agile for the future. Everyone developer requires only specific set of IDE features. This is how they could be satisfied.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 11 months