[JBoss JIRA] Created: (JBIDE-7996) Hibernate Configuration File (cfg.xml) Wizard: add possibility to import existing DTP connection settings
by Vitali Yemialyanchyk (JIRA)
Hibernate Configuration File (cfg.xml) Wizard: add possibility to import existing DTP connection settings
---------------------------------------------------------------------------------------------------------
Key: JBIDE-7996
URL: https://issues.jboss.org/browse/JBIDE-7996
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Hibernate
Affects Versions: 3.2.0.Beta2
Reporter: Vitali Yemialyanchyk
Assignee: Vitali Yemialyanchyk
Priority: Minor
https://issues.jboss.org/browse/JBIDE-1420 - initial idea of this enhancement.
I see 2 ways to implement the feature:
1) add "Import DTP connection" button -> small dialog just with combobox - to select one existing DTP connection and Ok & Cancel buttons;
2) add checkbox "Import DTP connection" and combobox - to select one existing DTP connection - here to import DTP connection is necessary to check "Import DTP connection" and select connection from combobox, if the user change some config value - checkbox should become unchecked and empty valu in combobox be selected
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] Created: (JBIDE-4233) Support for fine grained pages.xml editing
by Max Rydahl Andersen (JIRA)
Support for fine grained pages.xml editing
------------------------------------------
Key: JBIDE-4233
URL: https://jira.jboss.org/jira/browse/JBIDE-4233
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Seam
Reporter: Max Rydahl Andersen
Assignee: Alexey Kazakov
Priority: Critical
Fix For: 3.1.0.M3
Add support for fine grained page.xml (now we have support for coarse grained pages.xml) in the graphical pages.xml editor.
I imagine an additonal tab or a toggle on the current tab that when enabled shows not just the pages that are in the single file, but also includes any info from other *.page.xml files.
In the first iteration we can just make this a read only mode for any external files and then double click for editing (maybe that will be too cumbersome for the users ?)
--
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
13 years, 2 months
[JBoss JIRA] (JBIDE-10312) Define a minimal target platform as opposed to the recommend one we have now for builds
by Max Rydahl Andersen (Created) (JIRA)
Define a minimal target platform as opposed to the recommend one we have now for builds
---------------------------------------------------------------------------------------
Key: JBIDE-10312
URL: https://issues.jboss.org/browse/JBIDE-10312
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Build/Releng
Reporter: Max Rydahl Andersen
Assignee: Nick Boldt
Priority: Critical
Seeing JBIDE-10311 made me realize that we actually could catch these by having a *minimal* target platform to either build or test against.
The problem here is that a plugin got a plugin dependency based on the target platform - but the target platform have the latest 3.7.1 version meaning those users running 3.7.0 would have problems installing it.
If we had a minimal target platform (.target) we could actually install/verify these issues against it.
Not necessarily every night - but like once a week run the build or install the updatesite against the minimal target platform would
reveal these dependency issues.
WDYT?
--
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
13 years, 2 months