Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-9368 Dashboard(s) for easy news aggregation, twitter and easy additional/3rd party plugin installation and project template/creation
  3. JBIDE-9774

Plug-in the project template creation to the new JBoss Archetypes

        Details

        • Type: Sub-task
        • Status: Resolved (View Workflow)
        • Priority: Major
        • Resolution: Done
        • Affects Version/s: 3.3.0.M3
        • Fix Version/s: 3.3.0.M5
        • Component/s: maven
        • Labels:
          None

          Gliffy Diagrams

          1. central.png
            22 kB
          2. jbcentral15.png
            3 kB
          3. projectExamples.png
            3 kB

            Activity

            Ascending order - Click to sort in descending order
            Hide
            Permalink
            fbricon Fred Bricon added a comment -

            Added a Java EE 6 category and 2 maven archetypes to the JBoss Central dashboard :

            Show
            fbricon Fred Bricon added a comment - Added a Java EE 6 category and 2 maven archetypes to the JBoss Central dashboard :
            Hide
            Permalink
            fbricon Fred Bricon added a comment -

            Current archetypes are :

            The multi-javaee6-archetype is destined to be replaced by Pete Muir's take on a Full EE6 archetype.

            Show
            fbricon Fred Bricon added a comment - Current archetypes are : Java EE 6 Web Application = org.jboss.spec.archetypes:jboss-javaee6-webapp:7.0.0.Final from http://repository.jboss.org/nexus/content/groups/public/ Java EE 6 Enterprise Application = org.openarchetypes:multi-javaee6-archetype:0.0.1-SNAPSHOT from http://open-archetypes.github.com/maven-repo/snapshots/ The multi-javaee6-archetype is destined to be replaced by Pete Muir's take on a Full EE6 archetype.
            Hide
            Permalink
            snjeza Snjezana Peco added a comment -

            This jira has introduced several issues.

            Now there are two project examples with the same name in the Project Examples wizard.

            There are only one archetype in the JBoss Central editor.

            The error log is showing the following error:

            !ENTRY org.jboss.tools.central 4 0 2011-10-18 19:19:32.625
            !MESSAGE Invalid Project example:org.jboss.tools.central.jbossas.quickstart.jbossJavaee6Webapp

            The JBoss AS 7 Quickstarts::jboss-javaee6-webapp project example has been moved to the Java EE 6 Quickstarts category what is causing the "Creating your own application" action in the kitchensink cheatsheet to not work.

            Since the JBoss AS 7 Quickstarts category contains project examples with cheatsheets, it needs to be listed first. The "Helloworld quickstart" project example will probably be the first project example a new user will want to start.
            The Java EE 6 Quickstarts category just creates projects and doesn't contain cheatsheets that would explain, deploy, run ... projects. Java EE 6 Maven Archetypes is a better name for this category.

            Show
            snjeza Snjezana Peco added a comment - This jira has introduced several issues. Now there are two project examples with the same name in the Project Examples wizard. There are only one archetype in the JBoss Central editor. The error log is showing the following error: !ENTRY org.jboss.tools.central 4 0 2011-10-18 19:19:32.625 !MESSAGE Invalid Project example:org.jboss.tools.central.jbossas.quickstart.jbossJavaee6Webapp The JBoss AS 7 Quickstarts::jboss-javaee6-webapp project example has been moved to the Java EE 6 Quickstarts category what is causing the "Creating your own application" action in the kitchensink cheatsheet to not work. Since the JBoss AS 7 Quickstarts category contains project examples with cheatsheets, it needs to be listed first. The "Helloworld quickstart" project example will probably be the first project example a new user will want to start. The Java EE 6 Quickstarts category just creates projects and doesn't contain cheatsheets that would explain, deploy, run ... projects. Java EE 6 Maven Archetypes is a better name for this category.
            Hide
            Permalink
            fbricon Fred Bricon added a comment -
            • The 1st 2 screw-ups were already fixed, but I missed the cheatsheet issue, sorry.
            • Concerning the order of the categories, I don't have a very strong opinion about it, it's just that my understanding is we really want to highlight the EE6 quickstarts, putting them first makes sense in that case.
            • Concerning the name, I would tend to disagree (again I have no strong opinion here), as the category names represent what the user is gonna achieve, not the means he uses (we could rename JBoss AS 7 Quickstarts to JBoss AS 7 Maven Quickstarts)

            Let's hear Max's or Burr's feedback before rolling back changes.

            Show
            fbricon Fred Bricon added a comment - The 1st 2 screw-ups were already fixed, but I missed the cheatsheet issue, sorry. Concerning the order of the categories, I don't have a very strong opinion about it, it's just that my understanding is we really want to highlight the EE6 quickstarts, putting them first makes sense in that case. Concerning the name, I would tend to disagree (again I have no strong opinion here), as the category names represent what the user is gonna achieve, not the means he uses (we could rename JBoss AS 7 Quickstarts to JBoss AS 7 Maven Quickstarts) Let's hear Max's or Burr's feedback before rolling back changes.
            Hide
            Permalink
            maxandersen Max Rydahl Andersen added a comment -

            Why not have all of these listed under one category called "JavaEE 6" ?

            Show
            maxandersen Max Rydahl Andersen added a comment - Why not have all of these listed under one category called "JavaEE 6" ?
            Hide
            Permalink
            maxandersen Max Rydahl Andersen added a comment -

            and yes, wether the example uses maven archetypes or not shouldn't be reflected in the name.

            Show
            maxandersen Max Rydahl Andersen added a comment - and yes, wether the example uses maven archetypes or not shouldn't be reflected in the name.
            Hide
            Permalink
            fbricon Fred Bricon added a comment -

            Max : I can see 2 reasons why we might want to keep separate categories :
            1 - It's an easy way to promote Burr's quickstarts (although we might choose another name)
            2 - I'm afraid current AS7 archetypes really are too bound to AS7 (that would defeat the purpose of EE6 portability right)? I really really hope I'm wrong and if the projects generated via these examples can run on other EE6 containers OOTB, then putting them under EE6 is the way to go.

            Show
            fbricon Fred Bricon added a comment - Max : I can see 2 reasons why we might want to keep separate categories : 1 - It's an easy way to promote Burr's quickstarts (although we might choose another name) 2 - I'm afraid current AS7 archetypes really are too bound to AS7 (that would defeat the purpose of EE6 portability right)? I really really hope I'm wrong and if the projects generated via these examples can run on other EE6 containers OOTB, then putting them under EE6 is the way to go.
            Hide
            Permalink
            maxandersen Max Rydahl Andersen added a comment -

            ok - so for M4, keep it as it is. Java EE 6 Quickstarts and JBoss AS 7 Quickstarts. Then we can get feedback on that and get verified what those examples can/will target.

            btw. which server types do we set as requirement for the Java EE 6 ?

            Show
            maxandersen Max Rydahl Andersen added a comment - ok - so for M4, keep it as it is. Java EE 6 Quickstarts and JBoss AS 7 Quickstarts. Then we can get feedback on that and get verified what those examples can/will target. btw. which server types do we set as requirement for the Java EE 6 ?
            Hide
            Permalink
            fbricon Fred Bricon added a comment -

            From http://svn.jboss.org/repos/jbosstools/trunk/download.jboss.org/jbosstools/examples/project-examples-maven-3.3.xml, so far we have :

            • jboss-javaee6-webapp : <property name="allowed-types">org.jboss.ide.eclipse.as.runtime.70</property>
            • multi-javaee6-archetype : <property name="allowed-types">org.jboss.ide.eclipse.as.runtime.60, org.jboss.ide.eclipse.as.runtime.70, org.jboss.ide.eclipse.as.runtime.eap.60</property>

            I'll check with jboss-javaee6-webapp with EAP6

            Show
            fbricon Fred Bricon added a comment - From http://svn.jboss.org/repos/jbosstools/trunk/download.jboss.org/jbosstools/examples/project-examples-maven-3.3.xml , so far we have : jboss-javaee6-webapp : <property name="allowed-types">org.jboss.ide.eclipse.as.runtime.70</property> multi-javaee6-archetype : <property name="allowed-types">org.jboss.ide.eclipse.as.runtime.60, org.jboss.ide.eclipse.as.runtime.70, org.jboss.ide.eclipse.as.runtime.eap.60</property> I'll check with jboss-javaee6-webapp with EAP6
            Hide
            Permalink
            snjeza Snjezana Peco added a comment -

            > Max : I can see 2 reasons why we might want to keep separate categories :
            > 1 - It's an easy way to promote Burr's quickstarts (although we might choose another name)
            > 2 - I'm afraid current AS7 archetypes really are too bound to AS7 (that would defeat the purpose of EE6 portability right)?

            The Java EE 6 Quickstarts:Java EE 6 Web Application and JBoss AS 7 Quickstarts:kitchensink create the same project. Try to run them and you will see what the difference is.

            Show
            snjeza Snjezana Peco added a comment - > Max : I can see 2 reasons why we might want to keep separate categories : > 1 - It's an easy way to promote Burr's quickstarts (although we might choose another name) > 2 - I'm afraid current AS7 archetypes really are too bound to AS7 (that would defeat the purpose of EE6 portability right)? The Java EE 6 Quickstarts:Java EE 6 Web Application and JBoss AS 7 Quickstarts:kitchensink create the same project. Try to run them and you will see what the difference is.
            Hide
            Permalink
            maxandersen Max Rydahl Andersen added a comment -

            Fred, this issue is done for M4 or pushing to Beta1 ?

            Show
            maxandersen Max Rydahl Andersen added a comment - Fred, this issue is done for M4 or pushing to Beta1 ?
            Hide
            Permalink
            fbricon Fred Bricon added a comment -

            Moving to 3.3.0 Beta 1 since we only have half the archetypes ready and included in JBoss Central

            Show
            fbricon Fred Bricon added a comment - Moving to 3.3.0 Beta 1 since we only have half the archetypes ready and included in JBoss Central
            Hide
            Permalink
            fbricon Fred Bricon added a comment -

            fixed in trunk

            Show
            fbricon Fred Bricon added a comment - fixed in trunk

              People

              • Assignee:
                fbricon Fred Bricon
                Reporter:
                fbricon Fred Bricon
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Development