[ https://issues.jboss.org/browse/JBIDE-12248?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-12248: ---------------------------------- Attachment: (was: org.jboss.tools.usage.patch) -- 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

[ https://issues.jboss.org/browse/JBIDE-12248?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-12248: ------------------------------------ So, instead of this in the [^org.jboss.tools.usage.patch] {code} +CompatibilityCheckerDialogMessage=Text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text (<a>info</a>) +DoNotShowAgain=Do not show this dialog again +CheckingJob=Checking Eclipse/WTP version +ExplanationPageURL=http://jboss.org/tools {code} you want something else, like this? {code} +CompatibilityCheckerDialogMessage=Your current version of the Eclipse and Web Tools platforms are not compatible with this version of JBoss Tools. Please upgrade your installation to Eclipse 3.7.2, and Web Tools 3.3.2 (<a href="%%ExplanationPageURL%%">more info</a>). +DoNotShowAgain=Do not show this dialog again +CheckingJob=Checking Eclipse and WTP versions +ExplanationPageURL=https://www.jboss.org/tools/download/installation/update_3_3 {code} -- 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

[ https://issues.jboss.org/browse/JBIDE-12248?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-12248 at 7/3/12 4:58 PM: ------------------------------------------------------------ So, instead of this in the [^org.jboss.tools.usage.patch] {code:title=src/org/jboss/tools/usage/installation/messages.properties} +CompatibilityCheckerDialogMessage=Text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text (<a>info</a>) +DoNotShowAgain=Do not show this dialog again +CheckingJob=Checking Eclipse/WTP version +ExplanationPageURL=http://jboss.org/tools {code} you want something else, like this? {code:title=src/org/jboss/tools/usage/installation/messages.properties} +CompatibilityCheckerDialogMessage=Your current version of Eclipse and Web Tools are not compatible with this version of JBoss Tools. Please upgrade your installation to Eclipse 3.7.2 and Web Tools 3.3.2 (<a href="%%ExplanationPageURL%%">more info</a>). You could alternatively install a fresh <a href="http://www.eclipse.org/downloads/packages/eclipse-ide-java-ee-... Indigo SR2</a> bundle, then install JBoss Tools. +DoNotShowAgain=Do not show this dialog again +CheckingJob=Checking Eclipse and WTP versions +ExplanationPageURL=https://www.jboss.org/tools/download/installation/update_3_3 {code} Can I embed the URL in ExplanationPageURL within the property for CompatibilityCheckerDialogMessage? Also, if the point of the message is to present a problem/warning to the user, should it be called "CompatibilityCheckerDialogWarningMessage" ? Or do you want text to ask the user to PERFORM the compatibility check? was (Author: nickboldt): So, instead of this in the [^org.jboss.tools.usage.patch] {code} +CompatibilityCheckerDialogMessage=Text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text (<a>info</a>) +DoNotShowAgain=Do not show this dialog again +CheckingJob=Checking Eclipse/WTP version +ExplanationPageURL=http://jboss.org/tools {code} you want something else, like this? {code} +CompatibilityCheckerDialogMessage=Your current version of Eclipse and Web Tools are not compatible with this version of JBoss Tools. Please upgrade your installation to Eclipse 3.7.2 and Web Tools 3.3.2 (<a href="%%ExplanationPageURL%%">more info</a>). You could alternatively install a fresh <a href="http://www.eclipse.org/downloads/packages/eclipse-ide-java-ee-... Indigo SR2</a> bundle, then install JBoss Tools. +DoNotShowAgain=Do not show this dialog again +CheckingJob=Checking Eclipse and WTP versions +ExplanationPageURL=https://www.jboss.org/tools/download/installation/update_3_3 {code} Can I embed the URL in ExplanationPageURL within the property for CompatibilityCheckerDialogMessage? Also, if the point of the message is to present a problem/warning to the user, should it be called "CompatibilityCheckerDialogWarningMessage" ? Or do you want text to ask the user to PERFORM the compatibility check? -- 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

[ https://issues.jboss.org/browse/JBIDE-12248?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-12248: ----------------------------------- Attachment: org.jboss.tools.usage-NEW.patch Nick, thank yor for the text! -- 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

[ https://issues.jboss.org/browse/JBIDE-12248?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-12248: -------------------------------------- Assignee: Denis Golovin (was: Nick Boldt) -- 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

[ https://issues.jboss.org/browse/JBIDE-12248?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-12248: ------------------------------------ Alexey: when in doubt, if you need my comments on something and you're not getting a quick enough response via JIRA, assign it to me so I'll get an email, or ping me in IRC. As to the "more info" link, I'd use this page since it details how to install. https://www.jboss.org/tools/download/installation/update_3_3 Or do we need to draft some doc about WHY we're not compatible w/ 3.7.0/3.3.0? If so, point me at the information and I'll write something up for you. Or do we want to just link to https://issues.jboss.org/browse/JBIDE-12248?focusedCommentId=12703217&... ? -- 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

[ https://issues.jboss.org/browse/JBIDE-12248?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-12248: ---------------------------------------- Thank you Nick! Denis, what do you think about those links? -- 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

[ https://issues.jboss.org/browse/JBIDE-12248?page=com.atlassian.jira.plugi... ] Denis Golovin reassigned JBIDE-12248: ------------------------------------- Assignee: Nick Boldt (was: Denis Golovin) -- 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

[ https://issues.jboss.org/browse/JBIDE-12248?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-12248: ---------------------------------- Attachment: 370-final.patch [^370-final.patch] contains all fixes for review: 1. Updated dependencies versions and features requirements to let install on 3.7.0 + 2. Warning dialog 3. Fixes for all compilation problems we have against E3.7.0 and WTP 3.2.0 4. Incremented patch versions for all affected plugins When installed on 3.7.0/3.7.1 without updating to 3.7.2 there are known issues: * JBIDE-10668 M5 marketplace installation has a problem with jcsh dependency missing required com.jcraft.jsch 0.1.44, but it is 0.1.41 in Indigo 3.7.0 * JBIDE-10490 do not store server passwords in plain text -- 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

[ https://issues.jboss.org/browse/JBIDE-12248?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-12248: ---------------------------------- Attachment: (was: org.jboss.tools.usage-NEW.patch) -- 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

[ https://issues.jboss.org/browse/JBIDE-12248?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-12248: -------------------------------------- Assignee: Nick Boldt (was: Alexey Kazakov) Looks good. Nick, could you review the patch too? -- 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

[ https://issues.jboss.org/browse/JBIDE-12248?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-12248: ---------------------------------- Assignee: Alexey Kazakov (was: Nick Boldt) -- 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

[ https://issues.jboss.org/browse/JBIDE-12248?page=com.atlassian.jira.plugi... ] Denis Golovin edited comment on JBIDE-12248 at 7/5/12 6:23 AM: --------------------------------------------------------------- Fixed in 3.3.x branch was (Author: dgolovin): Fixed in trunk -- 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

[ https://issues.jboss.org/browse/JBIDE-12248?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-12248: --------------------------------------- as component build is still not ready, it is still 2.3.0 on stage site, but it was changed to 2.3.1 yesterday -- 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

[ https://issues.jboss.org/browse/JBIDE-12248?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-12248: --------------------------------------- as build #139 is fine, waiting for aggregation build -- 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

[ https://issues.jboss.org/browse/JBIDE-12248?page=com.atlassian.jira.plugi... ] Isaac Rooskov updated JBIDE-12248: ---------------------------------- Release Notes Docs Status: Not Required Writer: irooskov Setting release note status as it is not required for this issue -- 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

[ https://issues.jboss.org/browse/JBIDE-12248?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-12248. ------------------------------ Closing - will be fixed when we drop 3.3.1 to the Stable site and Eclipse Marketplace sees the new bits. -- 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

[ https://issues.jboss.org/browse/JBIDE-12248?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-12248: ------------------------------- Attachment: jbide12248-install-jbt331-into-eclipse-java-sr0-remove-openshift-and-egit-then-update-eclipse-to-juno2.png After seeing the above message, I attempted to Help > Search for Updates to get updated to the latest Eclipse 3.7.2. I was told that was impossible due to conflicts. So I removed egit and openshift, and then was able to update. I expected to have Eclipse 3.7.2 (EPP 1.4.2). Instead I was updated to Eclipse 4.2.0 (EPP 1.5.0). !jbide12248-install-jbt331-into-eclipse-java-sr0-remove-openshift-and-egit-then-update-eclipse-to-juno2.png! -- 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

[ https://issues.jboss.org/browse/JBIDE-12248?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-12248 at 7/17/12 12:26 AM: -------------------------------------------------------------- When I then attempted to install the two missing features: {code} JBoss OpenShift Tools 2.3.1.v20120715-0255-H145-Final JBoss Tools EGit Integration (Experimental) 2.3.1.v20120715-0255-H145-Final {code} !jbide12248-install-jbt331-into-eclipse-java-sr0-reinstall-openshift-and-egit.png! I was told that was impossible due to conflict: {code} Cannot satisfy dependency: From: Eclipse IDE for Java Developers 1.5.0.20120614-1633 (epp.package.java 1.5.0.20120614-1633) To: org.eclipse.epp.package.java.feature.feature.group [1.5.0.20120614-1633] Cannot satisfy dependency: From: EGit Import 2.0.0.201206130900-r (org.eclipse.egit.import 2.0.0.201206130900-r) To: package org.eclipse.egit.ui 2.0.0 AND Cannot satisfy dependency: From: JBoss OpenShift Tools 2.3.1.v20120715-0255-H145-Final (org.jboss.tools.openshift.express.feature.feature.group 2.3.1.v20120715-0255-H145-Final) To: org.jboss.tools.openshift.express.ui [2.3.1.v20120715-0255-H145-Final] Cannot satisfy dependency: From: OpenShift UI 2.3.1.v20120715-0255-H145-Final (org.jboss.tools.openshift.express.ui 2.3.1.v20120715-0255-H145-Final) To: bundle org.eclipse.egit.ui [1.0.0,2.0.0) {code} Have opened JBIDE-12338 to capture the request to have openshift work with egit 2.0 and therefore be installable into Juno. was (Author: nickboldt): When I then attempted to install the two missing features: {code} JBoss OpenShift Tools 2.3.1.v20120715-0255-H145-Final JBoss Tools EGit Integration (Experimental) 2.3.1.v20120715-0255-H145-Final {code} !jbide12248-install-jbt331-into-eclipse-java-sr0-reinstall-openshift-and-egit.png! I was told that was impossible due to conflict: {code} Cannot satisfy dependency: From: Eclipse IDE for Java Developers 1.5.0.20120614-1633 (epp.package.java 1.5.0.20120614-1633) To: org.eclipse.epp.package.java.feature.feature.group [1.5.0.20120614-1633] Cannot satisfy dependency: From: EGit Import 2.0.0.201206130900-r (org.eclipse.egit.import 2.0.0.201206130900-r) To: package org.eclipse.egit.ui 2.0.0 AND Cannot satisfy dependency: From: JBoss OpenShift Tools 2.3.1.v20120715-0255-H145-Final (org.jboss.tools.openshift.express.feature.feature.group 2.3.1.v20120715-0255-H145-Final) To: org.jboss.tools.openshift.express.ui [2.3.1.v20120715-0255-H145-Final] Cannot satisfy dependency: From: OpenShift UI 2.3.1.v20120715-0255-H145-Final (org.jboss.tools.openshift.express.ui 2.3.1.v20120715-0255-H145-Final) To: bundle org.eclipse.egit.ui [1.0.0,2.0.0) {code} -- 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

[ https://issues.jboss.org/browse/JBIDE-12248?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-12248 at 7/17/12 12:34 AM: -------------------------------------------------------------- Most of the JBoss Central connectors can be installed into the Eclipse 3.7.0-updated-to-4.2.0 workspace: !jbide12248-install-jbt331-into-eclipse-java-sr0-central-connectors-OK.png! However, three cannot be installed: 1. maven-gwt 2. mylyn-git 3. gwt !jbide12248-install-jbt331-into-eclipse-java-sr0-central-connectors-NOT-OK.png! was (Author: nickboldt): Most of the JBoss Central connectors can be installed into the Eclipse 3.7.0-updated-to-4.2.0 workspace: !jbide12248-install-jbt331-into-eclipse-java-sr0-central-connectors-OK.png! However, three cannot be installed: mylyn-gwt mylyn-git gwt !jbide12248-install-jbt331-into-eclipse-java-sr0-central-connectors-NOT-OK.png! -- 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

[ https://issues.jboss.org/browse/JBIDE-12248?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-12248: ------------------------------- Attachment: jbide12248-install-jbt331-into-eclipse-jee-sr0-while-installing-new-update-sites-available.png Trying the workflow again: 0. unpack Eclipse JEE SR0 linux 64 bundle. 1. run eclipse 2. Help > Eclipse Marketplace 3. search for "jboss tools indigo" 4. confirm installation 5. while installing, look in Window > Preferences > Install/Update > Available Software Sites and you'll see there's now a composite site for all of the marketplace, which presumably includes Helios, Indigo, and Juno versions of Eclipse and sundry: !jbide12248-install-jbt331-into-eclipse-jee-sr0-while-installing-new-update-sites-available.png! -- 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

[ https://issues.jboss.org/browse/JBIDE-12248?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-12248: ------------------------------------ Bug re: unexpectedly getting Juno 4.2 when you wanted Indigo 3.7.2: https://bugs.eclipse.org/bugs/show_bug.cgi?id=385334 -- 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

[ https://issues.jboss.org/browse/JBIDE-12248?page=com.atlassian.jira.plugi... ] Denis Golovin resolved JBIDE-12248. ----------------------------------- Resolution: Done This issue is about installing JBT out of Eclipse Market place on Eclipse 3.7.0 and up. Current amount of errors is more than three times less than it was before. Closing it and going to open separate related issues for Nick's comments. -- 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