[ https://jira.jboss.org/browse/JBDS-1373?page=com.atlassian.jira.plugin.sy... ] Max Andersen updated JBDS-1373: ------------------------------- Component/s: updatesite -- 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

[ https://jira.jboss.org/browse/JBDS-1373?page=com.atlassian.jira.plugin.sy... ] Dominik Pospisil commented on JBDS-1373: ---------------------------------------- OK, so what it is? :) Anyway, if that is expected, please close this one. Thanks! -- 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

[ https://jira.jboss.org/browse/JBDS-1373?page=com.atlassian.jira.plugin.sy... ] Andre Dietisheim edited comment on JBDS-1373 at 11/3/10 9:09 AM: ----------------------------------------------------------------- downloaded eclipse 3.6.1 jee and updated it by using our update zip (install new software -> add -> archive -> install). What you then get is an Eclipse instance that runs JBoss Tools. This is also reflected by the fact that your eclipse does not show the JBDS spash but the default eclipse splash screen. I'd therefore pretend: Reporting an Eclipse instance perfectly matches what should be expected. Technically speaking JBDS is a product. The product launches the eclipse instances and provides branding. If you use a standard eclipse and update it, you do not change its product, you just aggregate further plugins to it. Eclipse stays eclipse and does not get JBDS by an update. The usage plugin therefore detects an eclipse and not a JBDS instance. I could enhance my detection and try to detect JBDS in such a case but I guess those few cases are not worth the effort. Agree? was (Author: adietish): downloaded eclipse 3.6.1 jee and updated it by using our update zip (install new software -> add -> archive -> install). What you then get is an Eclipse instance that runs JBoss Tools, in other words: perfectly expected. Technically speaking JBDS is a product. The product launches the eclipse instances and provides branding. If you use a standard eclipse and update it, you do not change its product, you just aggregate further plugins to it. Eclipse stays eclipse and does not get JBDS by an update. The usage plugin therefore detects an eclipse instance and not a JBDS instance. I could enhance my detection and try to detect JBDS in such a case but I guess those few cases are not worth the effort. Agree? -- 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

[ https://jira.jboss.org/browse/JBDS-1373?page=com.atlassian.jira.plugin.sy... ] Dominik Pospisil closed JBDS-1373. ---------------------------------- Agreed. -- 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