[jbosstools-issues] [JBoss JIRA] (JBIDE-12472) Use JDF stacks to manage different archetype/runtime versions

Fred Bricon (JIRA) jira-events at lists.jboss.org
Fri Sep 21 10:18:35 EDT 2012


     [ https://issues.jboss.org/browse/JBIDE-12472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fred Bricon resolved JBIDE-12472.
---------------------------------

    Resolution: Done


Fixed in trunk. 

If in project-example-XXX.xml, a project example defines the <stacksId> property, we try to get the related JDF Stacks informations, if no stacksId, then fall back on the legacy project example descriptions.

The stack.yaml url is read from the stacks client jar embedded in org.jboss.tools.maven.project.examples.
This url can be overridden using the system property : -Dorg.jboss.examples.stacks.url=xxx

We use the Eclipse Communication Framework to download the stacks.yml from that url, instead of the stock stacks-client connection. 
If the file can not be downloaded or parsed properly, we fall back on using the default stacks provided by the stacks client (which either connects successfully to the stacks url or uses it's internal cache file).

If the wtp requirement is not met for that project example, we clicking on the "download and install" button will display a download dialog, listing all the runtimes (if theree are more than one) compatible with the selected archetype.

For EAP runtimes, which don't have a downloadable url but a human url, a clickable link is displayed.
 

                
> Use JDF stacks to manage different archetype/runtime versions
> -------------------------------------------------------------
>
>                 Key: JBIDE-12472
>                 URL: https://issues.jboss.org/browse/JBIDE-12472
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: central, maven, project-examples
>    Affects Versions: 3.3.1
>            Reporter: Fred Bricon
>            Assignee: Fred Bricon
>             Fix For: 4.0.0.Alpha2
>
>
> [~maxandersen] and I got our heads together and walked through usecase scenarios from JBT/JBDS in context of stacks.yml.
> For now we've put our notes together with questions at http://ether-man.rhcloud.com/p/stacks-jbosstools

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jbosstools-issues mailing list