[ https://issues.jboss.org/browse/JBIDE-9837?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen updated JBIDE-9837: --------------------------------------- Fix Version/s: 3.3.0.M4 -- 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-9837?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-9837: -------------------------------------------- I'm on the latest version that is on nightly updatesite and getting NPE's during publishing. But beyond that starting the server and the arquillian test shuoldn't just be done automatically! Especially since I don't see any UI to choose which of my now 6 servers it is going to run against and it is not at all giving me any control/knowledge about what is actually going to happen. Take helloworld example - if I have no servers it tells me to Download/install, if I have 1 or more servers it shows nothing. No options for downloading another server nor say which server it will choose. Ok - for me it still just says "This project example requires JBoss AS" and only when have zero servers. The org.jboss.tools.runtime.core.as.701 extension point is defined in the o.j.t.runtime.core plugin. I don't see that in the build from today yet. The download went in the background, I pressed run and it seemed to import/create the projects still - shouldn't it wait for the download to complete and then show a dialog about what will happen ? -- 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-9837?page=com.atlassian.jira.plugin... ] Snjezana Peco commented on JBIDE-9837: -------------------------------------- We are defining required runtimes (servers)/plugins within a project example file. For instance, as to the JBoss AS 7 helloworld example there are the following requirements (http://download.jboss.org/jbosstools/examples/project-examples-maven-3.3.xml): <fixes> <fix type="wtpruntime"> <property name="allowed-types">org.jboss.ide.eclipse.as.runtime.70</property> <property name="description">This project example requires JBoss AS 7.0</property> <property name="downloadId">org.jboss.tools.runtime.core.as.701</property> </fix> <fix type="plugin"> <property name="id">org.eclipse.m2e.core</property> <property name="versions">[1.0.0,1.1.0)</property> <property name="description">This project example requires m2e &gt;= 1.0.</property> <property name="connectorIds">org.eclipse.m2e.feature</property> </fix> <fix type="plugin"> <property name="id">org.maven.ide.eclipse.wtp</property> <property name="versions">[0.13.1,0.14.0)</property> <property name="description">This project example requires m2eclipse-wtp &gt;= 0.13.1.</property> <property name="connectorIds">org.maven.ide.eclipse.wtp</property> </fix> <fix type="plugin"> <property name="id">org.jboss.tools.maven.core</property> <property name="versions">[1.3.0,1.4.0)</property> <property name="description">This project example requires JBoss Maven Tools.</property> <property name="connectorIds">org.jboss.tools.maven.feature,org.jboss.tools.maven.cdi.feature,org.jboss.tools.maven.hibernate.feature,org.jboss.tools.maven.jaxrs.feature, org.jboss.tools.maven.portlet.feature,org.jboss.tools.maven.seam.feature</property> </fix> </fixes> The first requirement says JBoss AS 7 is required. If no any version of JBoss AS 7 is set , you will see a warning icon. !jboscentrala.png!. When you click the tutorial, you will get a message saying "This project example requires JBoss AS 7.0" !jbosscentralb.png! If you have any JBoss AS 7 downloaded, you will be able to choose the Install button that will enable you to set JBoss AS 7 you want using the Runtime detection preferences page. If you don't have any JBoss AS 7 server downloaded, you can select the Download and Install button that will download and install JBoss AS 7.0.1 (<property name="downloadId">org.jboss.tools.runtime.core.as.701</property>). We have to add the Download button to the Runtime Detection preferences page that will enable a user to download different servers. If you don't have m2e-core, m2eclipse-wtp and/or JBoss Maven Tools features, you will get additional requirements to the Project Example wizard: - This project example requires m2e >=1.0 - This project example requires m2eclipse-wtp >= 0.13.1 - This project example requires JBoss Maven Tools. You can choose the Install button that will automatically install these features using the Mylyn discovery engine or you can choose the Install New Software button that will call the P2 Install dialog. The last option is intended for advanced users. If you have m2e-core, m2eclipse-wtp, JBoss Maven Tools and some version of JBoss AS 7 server, all the requirements are satisfied and you can run the tutorial. When starting the "Run and deploy the application" action !jbosscentralc.png!, you will get the standard WTP "Run On Server" dialog !jbosscentrald.png! so that you can decide what server to use to deploy and run the application (as well as the Arquillian test). That button enables a user to download/install runtimes/plugins required for the tutorial to be run. That means that the user's environment contains all necessary requirements to run the tutorial. What project example? I couldn't find that message in any project example xml file. Could you create a screenshot? It is possible that there is a problem with layout on Mac if you use it. If there are all required servers/plugins, there is no message. If you, for instance, try to add JBoss AS 6, 5 or 4, but not JBoss AS 7, the message "This project example requires JBoss AS 7.0" will be written when starting some JBoss AS 7 Quickstarts example because they require JBoss AS 7. Currently, the user can set runtimes that are downloaded and unpacked . I haven't implemented the Download button in the Runtime Detection Preferences page. Will do it ASAP. Do you want me to remove the Run in Background button. Suppose we could leave the Cancel button because the download could take a long time. -- 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-9837?page=com.atlassian.jira.plugin... ] Snjezana Peco edited comment on JBIDE-9837 at 10/12/11 11:35 AM: ----------------------------------------------------------------- We are defining required runtimes (servers)/plugins within a project example file. For instance, as to the JBoss AS 7 helloworld example there are the following requirements (http://download.jboss.org/jbosstools/examples/project-examples-maven-3.3.xml): <fixes> <fix type="wtpruntime"> <property name="allowed-types">org.jboss.ide.eclipse.as.runtime.70</property> <property name="description">This project example requires JBoss AS 7.0</property> <property name="downloadId">org.jboss.tools.runtime.core.as.701</property> </fix> <fix type="plugin"> <property name="id">org.eclipse.m2e.core</property> <property name="versions">[1.0.0,1.1.0)</property> <property name="description">This project example requires m2e &gt;= 1.0.</property> <property name="connectorIds">org.eclipse.m2e.feature</property> </fix> <fix type="plugin"> <property name="id">org.maven.ide.eclipse.wtp</property> <property name="versions">[0.13.1,0.14.0)</property> <property name="description">This project example requires m2eclipse-wtp &gt;= 0.13.1.</property> <property name="connectorIds">org.maven.ide.eclipse.wtp</property> </fix> <fix type="plugin"> <property name="id">org.jboss.tools.maven.core</property> <property name="versions">[1.3.0,1.4.0)</property> <property name="description">This project example requires JBoss Maven Tools.</property> <property name="connectorIds">org.jboss.tools.maven.feature,org.jboss.tools.maven.cdi.feature,org.jboss.tools.maven.hibernate.feature,org.jboss.tools.maven.jaxrs.feature, org.jboss.tools.maven.portlet.feature,org.jboss.tools.maven.seam.feature</property> </fix> </fixes> The first requirement says JBoss AS 7 is required. If no any version of JBoss AS 7 is set , you will see a warning icon. !jbosscentrala.png!. When you click the tutorial, you will get a message saying "This project example requires JBoss AS 7.0" !jbosscentralb.png! If you have any JBoss AS 7 downloaded, you will be able to choose the Install button that will enable you to set JBoss AS 7 you want using the Runtime detection preferences page. If you don't have any JBoss AS 7 server downloaded, you can select the Download and Install button that will download and install JBoss AS 7.0.1 (<property name="downloadId">org.jboss.tools.runtime.core.as.701</property>). We have to add the Download button to the Runtime Detection preferences page that will enable a user to download different servers. If you don't have m2e-core, m2eclipse-wtp and/or JBoss Maven Tools features, you will get additional requirements to the Project Example wizard: - This project example requires m2e >=1.0 - This project example requires m2eclipse-wtp >= 0.13.1 - This project example requires JBoss Maven Tools. You can choose the Install button that will automatically install these features using the Mylyn discovery engine or you can choose the Install New Software button that will call the P2 Install dialog. The last option is intended for advanced users. If you have m2e-core, m2eclipse-wtp, JBoss Maven Tools and some version of JBoss AS 7 server, all the requirements are satisfied and you can run the tutorial. When starting the "Run and deploy the application" action !jbosscentralc.png!, you will get the standard WTP "Run On Server" dialog !jbosscentrald.png! so that you can decide what server to use to deploy and run the application (as well as the Arquillian test). That button enables a user to download/install runtimes/plugins required for the tutorial to be run. That means that the user's environment contains all necessary requirements to run the tutorial. What project example? I couldn't find that message in any project example xml file. Could you create a screenshot? It is possible that there is a problem with layout on Mac if you use it. If there are all required servers/plugins, there is no message. If you, for instance, try to add JBoss AS 6, 5 or 4, but not JBoss AS 7, the message "This project example requires JBoss AS 7.0" will be written when starting some JBoss AS 7 Quickstarts example because they require JBoss AS 7. Currently, the user can set runtimes that are downloaded and unpacked . I haven't implemented the Download button in the Runtime Detection Preferences page. Will do it ASAP. Do you want me to remove the Run in Background button. Suppose we could leave the Cancel button because the download could take a long time. was (Author: snjeza): We are defining required runtimes (servers)/plugins within a project example file. For instance, as to the JBoss AS 7 helloworld example there are the following requirements (http://download.jboss.org/jbosstools/examples/project-examples-maven-3.3.xml): <fixes> <fix type="wtpruntime"> <property name="allowed-types">org.jboss.ide.eclipse.as.runtime.70</property> <property name="description">This project example requires JBoss AS 7.0</property> <property name="downloadId">org.jboss.tools.runtime.core.as.701</property> </fix> <fix type="plugin"> <property name="id">org.eclipse.m2e.core</property> <property name="versions">[1.0.0,1.1.0)</property> <property name="description">This project example requires m2e &gt;= 1.0.</property> <property name="connectorIds">org.eclipse.m2e.feature</property> </fix> <fix type="plugin"> <property name="id">org.maven.ide.eclipse.wtp</property> <property name="versions">[0.13.1,0.14.0)</property> <property name="description">This project example requires m2eclipse-wtp &gt;= 0.13.1.</property> <property name="connectorIds">org.maven.ide.eclipse.wtp</property> </fix> <fix type="plugin"> <property name="id">org.jboss.tools.maven.core</property> <property name="versions">[1.3.0,1.4.0)</property> <property name="description">This project example requires JBoss Maven Tools.</property> <property name="connectorIds">org.jboss.tools.maven.feature,org.jboss.tools.maven.cdi.feature,org.jboss.tools.maven.hibernate.feature,org.jboss.tools.maven.jaxrs.feature, org.jboss.tools.maven.portlet.feature,org.jboss.tools.maven.seam.feature</property> </fix> </fixes> The first requirement says JBoss AS 7 is required. If no any version of JBoss AS 7 is set , you will see a warning icon. !jbosscentrala.png!. When you click the tutorial, you will get a message saying "This project example requires JBoss AS 7.0" !jbosscentralb.png! If you have any JBoss AS 7 downloaded, you will be able to choose the Install button that will enable you to set JBoss AS 7 you want using the Runtime detection preferences page. If you don't have any JBoss AS 7 server downloaded, you can select the Download and Install button that will download and install JBoss AS 7.0.1 (<property name="downloadId">org.jboss.tools.runtime.core.as.701</property>). We have to add the Download button to the Runtime Detection preferences page that will enable a user to download different servers. If you don't have m2e-core, m2eclipse-wtp and/or JBoss Maven Tools features, you will get additional requirements to the Project Example wizard: - This project example requires m2e >=1.0 - This project example requires m2eclipse-wtp >= 0.13.1 - This project example requires JBoss Maven Tools. You can choose the Install button that will automatically install these features using the Mylyn discovery engine or you can choose the Install New Software button that will call the P2 Install dialog. The last option is intended for advanced users. If you have m2e-core, m2eclipse-wtp, JBoss Maven Tools and some version of JBoss AS 7 server, all the requirements are satisfied and you can run the tutorial. When starting the "Run and deploy the application" action !jbosscentralc.png!, you will get the standard WTP "Run On Server" dialog !jbosscentrald.png! so that you can decide what server to use to deploy and run the application (as well as the Arquillian test). That button enables a user to download/install runtimes/plugins required for the tutorial to be run. That means that the user's environment contains all necessary requirements to run the tutorial. What project example? I couldn't find that message in any project example xml file. Could you create a screenshot? It is possible that there is a problem with layout on Mac if you use it. If there are all required servers/plugins, there is no message. If you, for instance, try to add JBoss AS 6, 5 or 4, but not JBoss AS 7, the message "This project example requires JBoss AS 7.0" will be written when starting some JBoss AS 7 Quickstarts example because they require JBoss AS 7. Currently, the user can set runtimes that are downloaded and unpacked . I haven't implemented the Download button in the Runtime Detection Preferences page. Will do it ASAP. Do you want me to remove the Run in Background button. Suppose we could leave the Cancel button because the download could take a long time. -- 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-9837?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen updated JBIDE-9837: --------------------------------------- Attachment: screenshot0.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-9837?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-9837: -------------------------------------------- I get this - so what happens when there are multiple allowed server types? will it provide an install button for all? and here - what happens if multiple options ? for this to work these would need to be listed in the mylyn discovery sites, correct ? For M4 we don't have these so better to disable that for now I assume ? Except when you deleted the server - then there is the runtime left and there is nothing to actually deploy to. !screenshot0.png! it only seem to check for runtime existence, not server existence. yeah - even if I got a server type configured as AS7 I would still like to easily be able to download these runtimes without having to delete all servers. It's okey - I now understand that "Run" doesn't mean run but "Start" :) I would say if the requirement is still not downloaded and configured clicking Start should show a dialog asking something like: "<list of requirements> which is required for this example is still downloading. Do you still want to start the example ? Yes|No" -- 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-9837?page=com.atlassian.jira.plugin... ] Pavol Srna commented on JBIDE-9837: ----------------------------------- Verified on jbosstools-3.3_stable_branch.aggregate-Update-2011-10-27_16-13-53-H37. -- 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