[
https://issues.jboss.org/browse/JBDS-2030?page=com.atlassian.jira.plugin....
]
Snjezana Peco commented on JBDS-2030:
-------------------------------------
eh? if that is the case the plugins are truly bad if they don't
listen to preferences just because it is a new workspace. This would make the plugin
ignore plugin_customization.ini
That doesn't depend on us. They are the 3rd party plugins.
Not following how that relates to this ? These plugins are installed
and supposed to be used.
What is wrong with excluding startup is if the plugins startup code does more than just
asking for these settings.
For example, subclipse has separate usage plugin
(org.tigris.subversion.subclipse.tools.usage). If we exclude the startup ext. point, we
have also excluded this plugin. The plugin doesn't work anything else, but is always
started.
Disabled modal usage dialogs from extras plugins by default
-----------------------------------------------------------
Key: JBDS-2030
URL:
https://issues.jboss.org/browse/JBDS-2030
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Build, updatesite
Affects Versions: 5.0.0.M5
Environment: JBDS 5.0.0.M5
Reporter: Jiri Peterka
Assignee: Snjezana Peco
Attachments: atlassian-connector-modal.png, subclipse-usage-modal.png
Usage analysis modal dialogs from extras plugins are quire annoying. Mainly in situations
when there is more then one and the one with focus is hidden behind the other. It would be
nice if appearing of these dialogs could be disabled by default in JBDS.
Namely these:
* subclipse usage
* atlasian connector
--
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