[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-6927) Integrate Savara plugins into JBoss Tools

[Gary Brown (JIRA)]

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

Gary Brown commented on JBIDE-6927:
-----------------------------------

As per Max's email, I have created a branch for pi4soa and Savara.

https://pi4soa.svn.sourceforge.net/svnroot/pi4soa/branches/pi4soa-3.1.x

https://svn.jboss.org/repos/savara/branches/1.1.x

I wasn't sure what to do regarding the hudson jobs - I could just copy the existing jobs, but not sure how the result gets aggregated to the particular release, so wanted to check what I should do first.

The existing jobs (savara and jbosstools-pi4soa) are pointing to trunk, so I guess they should still point at trunk, but need to publish their results somewhere else?

Once I know what changes need to be made to the current trunk jobs, then I can create savara-1.1.x and jbosstools-pi4soa-3.1.x jobs as duplicates of the current jobs.

One final point - a minor change that is not urgent, but in case you have time - I have made the pi4soa core and scribble protocol features dependencies on the Savara feature, so they get pulled in automatically. Currently the pi4soa feature is only in the All category, so was wondering whether it would actually be better for the Scribble protocol feature to also just be in the All category rather than SOA development?


> Integrate Savara plugins into JBoss Tools
> -----------------------------------------
>
>                 Key: JBIDE-6927
>                 URL: https://jira.jboss.org/browse/JBIDE-6927
>             Project: Tools (JBoss Tools)
>          Issue Type: Task
>            Reporter: Gary Brown
>            Assignee: Nick Boldt
>             Fix For: 3.2.0.Beta
>
>         Attachments: Screenshot-JBDS4M2-with-teiid-and-savara-installed-from-trunk.png
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> The requested information is:
> a) where Savara's build job is located (URL)
> Savara-1.0.x is the currently released version, which was not built using Tycho - so this version should not be integrated.
> Savara-1.1.0 (which is currently trunk) hudson job is here: http://hudson.qa.jboss.com/hudson/job/savara/
> The tools part is located in a 'tools' sub-folder, within trunk.
> b) where Savara's update site is published (URL)
> Originally was publishing using the publish.sh script as part of jboss tools, but a change was made that causes it to fail, I think due to the fact that the Eclipse plugins/features/site are within a sub-folder, and not at the root of the build job. So currently the hudson job just provides the link to the latest built artifacts, which include the update site zip.
> The hudson job also builds a runtime distribution for Savara.
> c) the category name / label / description for the aggregate update site
> (chunk of XML)
> Savara / Savara / Tooling support for the Savara "Testable Architecture" capabilities.
> d) any other categories in which the Savara stuff needs to be included
> (chunk(s) of XML)
> e) the full list of Savara feature names to be included (plain text, as
> pulled from your feature.xml's ID field(s))
> org.jboss.savara.tools.feature
> org.jboss.savara.experimental.feature
> org.scribble.protocol.feature

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira