[jbosstools-issues] [JBoss JIRA] (JBIDE-9837) Requirements weirdness for project examples
Snjezana Peco (Commented) (JIRA)
jira-events at lists.jboss.org
Wed Oct 12 11:29:16 EDT 2011
[ https://issues.jboss.org/browse/JBIDE-9837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634221#comment-12634221 ]
Snjezana Peco 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.
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 >= 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 >= 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).
> Take helloworld example - if I have no servers it tells me to Download/install,
That button enables a user to download/install runtimes/plugins required for the tutorial to be run.
> if I have 1 or more servers it shows nothing. No options for downloading another server nor say which server it will choose.
That means that the user's environment contains all necessary requirements to run the tutorial.
> ><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>
> Ok - for me it still just says "This project example requires JBoss AS"
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.
> and only when have zero servers.
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.
> The org.jboss.tools.runtime.core.as.701 extension point is defined in the o.j.t.runtime.core plugin.
> >He can also call the Runtime Detection Preferences page and install whatever runtime he wants (JBoss AS 7.0.0, 7.0.1 or 7.0.2).
> I don't see that in the build from today yet.
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.
> 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 ?
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.
> Requirements weirdness for project examples
> -------------------------------------------
>
> Key: JBIDE-9837
> URL: https://issues.jboss.org/browse/JBIDE-9837
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, project-examples
> Reporter: Max Rydahl Andersen
> Assignee: Snjezana Peco
> Priority: Critical
> Fix For: 3.3.0.M4
>
> Attachments: jbosscentrala.png, jbosscentralb.png, jbosscentralc.png, jbosscentrald.png
>
>
> The new ui for project examples with respect to "install"/download and install and requirements is behaving weird:
> 1) The requirement section is empty if the requirements exist - so users can't actually see what it will use
> 2) it says "This example needs JBoss AS" but doesn't say anything about version or where it will get the server from when asking for installation dir.
> Should at least say which version is needed, what it is downloading.
> 3) Pressing download & Install, answering all the questions a dialog box comes up showing download, which I then can put in backgroun (nice) - but now the Run button is there, I click on it and nothing happens.
> 4) If I got all requirements and press "Run" it still doesn't do anything.
--
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
More information about the jbosstools-issues
mailing list