[
https://issues.jboss.org/browse/JBIDE-3113?page=com.atlassian.jira.plugin...
]
Mickael Istria commented on JBIDE-3113:
---------------------------------------
Such plugins could define a dependency to the JBoss Tools plugin defining the category,
and put the preference under this category. The JBT plugin defining category would simply
have to be declared in target-platform.
I think it's already easily possible for Hibernate or jBPM which already have JBoss
Tools in their target-platform. Drools could simply add the latest version of JBoss Tools
to their target-platform.
Consolidation/clean up of preference pages
------------------------------------------
Key: JBIDE-3113
URL:
https://issues.jboss.org/browse/JBIDE-3113
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common/jst/core, drools, jbpm
Affects Versions: 3.0.0.cr1
Environment: JBossTools-3.0.0.CR1-N200811050757-ALL-linux-gtk
Reporter: John Graham
Assignee: Kris Verlaenen
Priority: Critical
Labels: usability
Fix For: LATER
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
JBT currently has three preference page categories:
1. Drools
2. JBoss jBPM
3. JBoss Tools
The first two should be listed as subsections of the JBoss Tools category. Alternatively,
I suggest that the top level category should just be JBoss:
- JBoss
-- Drools
-- jBPM
Also, the JBoss Tools and JBoss jBPM top level pages in each of these categories do not
expose preferences, but rather the default buttons or simply a label ("JBoss
Tools"). These top level pages should show overall JBT preferences. See the Java
preferences or other examples in the Eclipse platform for this idea. (Also note that the
DTP 1.6.x way of doing this is wrong... ;) )
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira