[ https://issues.jboss.org/browse/JBIDE-10053?page=com.atlassian.jira.plugi... ] Pete Muir updated JBIDE-10053: ------------------------------ Attachment: jboss_central.tiff -- 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-10053?page=com.atlassian.jira.plugi... ] Pete Muir updated JBIDE-10053: ------------------------------ Component/s: central -- 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-10053?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-10053: ------------------------------------- The EE6 Quickstart category sole purpose here is to provide a visual separation for the 4 (currently 2) archetypes we want to promote, from the other AS 7 quickstarts. So the name is not definitive. They may even appear in a separate location in the future. -- 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-10053?page=com.atlassian.jira.plugi... ] Burr Sutter commented on JBIDE-10053: ------------------------------------- I believe the resolution is to move the "archetypes" into the Create Project section of JBoss Central. Create Project would then contain: - Java EE6 WAR - Java EE6 EAR - HTML5 Project - SpringMVC - Dynamic Web Project - potentially EE6 with RichFaces Project and "Java EE6 Quickstarts" would disappear as a category under Project Examples. The key thing for me is that the archetypes are not quickstarts which is a very specific name for a very specific feature of EAP & SOA-P. -- 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-10053?page=com.atlassian.jira.plugi... ] Burr Sutter commented on JBIDE-10053: ------------------------------------- Great point, I did not think about the icons. There may be some that can be reused but yes, please do work with the design team on appropriate icons. -- 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-10053?page=com.atlassian.jira.plugi... ] Burr Sutter commented on JBIDE-10053: ------------------------------------- Max did mention to me that the current "Create Projects" section was about new project Wizards. From the end-user perspective, we want them to primarily use the 4 main new archetypes (5 if you count the RichFaces one). Some things need to be removed from "Create Projects" - Seam 2 - Maven Project - this is one is very confusing because the end-user tends to pick the wrong archetypes - type "jboss" and you will see what I mean. - Project Examples- as that is basically the same thing as repeated in the section below as "Project Examples" That leaves only Dynamic Web Project, unless we add in the key 4 new archetypes. -- 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-10053?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-10053: --------------------------------------- The Project Examples entry in the Create Projects section is the Project Examples wizard (Help>Project Examples). It includes all project examples. The Project Examples section in the JBoss Central editor includes only those project examples that provide a quick start guide to JBoss Tools/JBDS. It is possible to set any ordering you want, but it isn't easy to move some project example (the Java EE6 Quickstarts category, for instance) to the Create Projects section that contains Eclipse wizards. You can see that the Create Projects section doesn't include categories. If we want to move some project example to this section, we will have to change the code. Yes. They are project examples. The kitchensink quickstart is the same as the Java EE 6 Web Application archetype. However, the kitchensink quickstart explains the complete application and Java EE 6 Web Application just creates a project. Currently, there aren't archetypes for the helloworld, numberguess and login project example. These examples guide users gradually in developing a web application. It isn't necessary to create a cheatsheet for the Java EE 6 Web Application archetype because this application is the same as the kitcensink quickstart that already includes a cheatsheet. We also don't have to remove the Java EE 6 Web Application archetype because it enables the user familiar with the JBoss AS7 quickstarts to quickly create a new project. Cheatsheets for other archetypes can be added. -- 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-10053?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-10053: --------------------------------------------- Snejzana - that the archetypes are handled by project examples shouldn't dictate how we layout jboss central. We got requirements early on that the main "create project" items should be front and center and optimally also available via File > New > * This is part of that. The question is if this is impossible to do in the time for B1 where we also need to have the software/update page in place. About quickstarts then the ones we got now are only targeting community dependencies, there will be new ones for EAP and possible more for other platforms thus we need to find a way to handle the "duplication" - that specific issue is covered over at https://issues.jboss.org/browse/JBIDE-10120 -- 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-10053?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-10053: --------------------------------------- Project examples can be declaratively added to the Project Examples section, but actions (wizards) to the Create Projects section are being programatically added . If some project examples (archetypes) have to be added via File>New, we would have to create separate Eclipse wizards for every such a project example. Then they could be easily added to the Create Projects section (by adding just the wizard's id). Another way would be to add actions to the Create Projects section that would call a certain project example. Those actions wouldn't be in File>New This can be done for B1 if we need to add only existing archetypes. If it is necessary to add a possibility of adding wizards and project examples declaratively to the Create Projects section, that would take me a bit more time, but probably can be done for Beta1. We could change the tutorials extension point and add the visible tag. If the tag exists, a project example will be visible only if there is some runtime listed in visible. For example: <tutorial id="org.jboss.tools.central.jbossas.quickstart.kitchensink" categoryId="org.jboss.tools.central.jbossas.quickstart" name="Kitchensink quickstart" type="projectExample" priority="4" icon="icons/jbossas7.png" reference="JBoss AS 7 Quickstarts::kitchensink"/ visible="org.jboss.ide.eclipse.as.runtime.70"> This project example would be visible only if there is JBoss AS 7.0.x. If this has to be implemented in the Project Examples wizard (Help>Project Examples), a similar tag would have to be added to the project example xml file. The org.jboss.tools.central.tutorials ext. point shouldn't be changed in this case. The consequence would be that the user wouldn't be able to see some project examples until he installs the appropriate runtime. -- 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-10053?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-10053: -------------------------------- Summary: Move current JavaEE 6 archetypes in JBoss Central to the create Project section (was: Move current JavaEE 6 archetypes in Maven Central to the create Project section) -- 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-10053?page=com.atlassian.jira.plugi... ] Burr Sutter commented on JBIDE-10053: ------------------------------------- That is pretty good. One thing that I mentioned on another Jira, for the sake of consistency - use "Project" after all everything but "OpenShift Express Application". And, we can drop "Express" - just call it "OpenShift Application". Dynamic Web Project OpenShift Application Java EE Web Project Java EE Enterprise Project (or EAR Project if we need the space) HTML5 Project Spring MVC Project RichFaces Project (note: capital "F") I also dropped the version numbers - we will have EE7 one day :-) -- 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-10053?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-10053: --------------------------------------------- Yes, please do not remove Express from it. There is way too much confusion about what kind of support the various openshift offerings do so until they actually merge we should be clear in UI and docs that OpenShift Express is what we support. -- 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-10053?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-10053. --------------------------------- Resolution: Done Fixed in trunk. The "Create Project" section uses a hardcoded Tutorial collection. The related links are loaded via the Project Example loading job, so they can appear with a 1 to 2 sec delay in the Create Project section. They're cached and not reloaded if the Project Examples section is refreshed. Once JBIDE-10264 is fixed, we'll be able to remove that weird loading strategy (hopefully) as we'll directly reference actual wizards. -- 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-10053?page=com.atlassian.jira.plugi... ] Burr Sutter commented on JBIDE-10053: ------------------------------------- Can I update to "trunk" to see the changes? I am currently pointing at http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ Not sure if that is the right one? -- 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-10053?page=com.atlassian.jira.plugi... ] Burr Sutter commented on JBIDE-10053: ------------------------------------- Just came in with my last update! -- 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