[jbosstools-issues] [JBoss JIRA] (JBDS-3273) JBoss Central: Automatic upstream quickstart integration
Paul Robinson (JIRA)
issues at jboss.org
Fri Feb 20 05:10:49 EST 2015
[ https://issues.jboss.org/browse/JBDS-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13042288#comment-13042288 ]
Paul Robinson commented on JBDS-3273:
-------------------------------------
[~fbricon]:
FYI, here's a search that returns all the data held in the DCP for 2 quickstarts. Notice that I replaced all the 'field=' params with 'field=_source', this gives us back the source document for each result.
http://dcp.jboss.org/v1/rest/search?field=_source&query=sys_tags%3A(%22JAX-RS%22)+AND+sys_type%3A(jbossdeveloper_quickstart)+AND+experimental%3Afalse&size=2&content_provider=jboss-developer&content_provider=rht
I agree, you don't seem to be able to figure out which commit we are indexing from these results. Notice on here http://www.jboss.org//quickstarts/eap/jax-rs-client/index.html that there is a link to https://github.com/jboss-developer/jboss-eap-quickstarts/tree/6.3.0.GA. This is the tag that was indexed. Unfortunately, this data is not yet present in the DCP data. However, we could add it, I'm sure.
How about we add:
quickstart_id: the directory name of the qs (e.g. 'jax-rs-client')
commit_id: 9c2b50a2b68a9d1f9f4fba22d0799964990add9c
Would this give you what you need?
> JBoss Central: Automatic upstream quickstart integration
> ---------------------------------------------------------
>
> Key: JBDS-3273
> URL: https://issues.jboss.org/browse/JBDS-3273
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: central, requirements
> Reporter: Burr Sutter
> Assignee: Fred Bricon
> Fix For: 9.0.0.Alpha2
>
>
> Support a more dynamic JBoss Central with direct access to the upstream quickstarts - no longer requiring a fork and tweak to the current quickstarts. We will need some form of 'search UI' as the total list of quickstarts has grown dramatically.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
More information about the jbosstools-issues
mailing list