[
https://jira.jboss.org/browse/JBDS-1338?page=com.atlassian.jira.plugin.sy...
]
Andre Dietisheim commented on JBDS-1338:
----------------------------------------
I personally have the impression that we should have done that with fragments.
To meet the requirements discussed with Max I implemented it in the following way:
'Branding' (the different texts, Google Analytics accounts, kill-switch location,
etc.) is provided by a service. The usage bundle supplies a default service that provides
the JBoss Tools branding. It has a service.ranking of -1 as is the default branding.
There now is an additional branding-service that gets provided by the branding bundle for
JBDS. It has a higher service.ranking and takes priority over the default service.
usage reporting: remove hack and implement in a proper manner: JBDS
report differently from JBoss tools
-------------------------------------------------------------------------------------------------------
Key: JBDS-1338
URL:
https://jira.jboss.org/browse/JBDS-1338
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Affects Versions: 4.0.0.Beta1
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 4.0.0.Beta2
JBDS-1321 set the requirements for reporting in JBDS differently than in JBoss Tools.
1) Use a different url (possibly different GA account) to separate the collection.
2) Different kill switch location (
devstudio.jboss.com/usage/usage.properties ?)
3) different texts in dialog and preferences
4) different link to usage reporting documentation ('please-allow'-dialog)
These requirements were implemented but implemented with a hack to that we could meet the
deadline. This hack must be corrected now.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira