[jbosstools-issues] [JBoss JIRA] (JBIDE-10053) Move current JavaEE 6 archetypes in Maven Central to the create Project section

[Max Rydahl Andersen (Commented) (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-10053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641832#comment-12641832 ] 

Max Rydahl Andersen commented on JBIDE-10053:
---------------------------------------------

>> Snejzana - that the archetypes are handled by project examples shouldn't dictate how we layout jboss central.

>Project examples can be declaratively added to the Project Examples section, but actions (wizards) to the Create Projects ?>section are being programatically added .

Yes, which is fine.

>> 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.

>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).

That would be great.

>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. 

Yes. if can done as Wizards even better, but otherwise yes this would work.


>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.

For now the "Create section" doesn't have to be dynamic - unless there is something I'm missing on how it works ?


>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.
<cut example>
>This project example would be visible only if there is JBoss AS 7.0.x.

This doesn't solve the problem and actually makes it impossible to use the feature of being able to download the right runtime.


>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.

Yes, which is not what we want. Lets take discussion about handling multiple versions of the same quickstart at JBIDE-10120; not in here.
                
> Move current JavaEE 6 archetypes in Maven Central to the create Project section
> -------------------------------------------------------------------------------
>
>                 Key: JBIDE-10053
>                 URL: https://issues.jboss.org/browse/JBIDE-10053
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: central
>    Affects Versions: 3.3.0.M4
>            Reporter: Pete Muir
>            Assignee: Fred Bricon
>             Fix For: 3.3.0.Beta1
>
>         Attachments: jboss_central.tiff
>
>
> They are called "JBoss AS 7 Archetypes" Not "Java EE 6 Quickstarts"

--
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