[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=12552973#action_12552973 ] 

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

Created new savara job: http://hudson.qa.jboss.com/hudson/view/SAVARA/job/savara-1.1.x/

Updated the SVN URLs to point to savara-1.1.x branch and jbosstools-3.2.0.Beta1 branch.

Not sure what to do about Beta2 aggregate job at the moment, as once Beta1 is released, Beta2 aggregate job should point to this savara hudson job. So for now either Beta2 should not include Savara, or it could point to trunk, but then potentially new feature work in savara trunk may briefly end up in Beta2 build, before Beta2 is switched to the savara-1.1.x job. 

Don't know if this is much of an issue for a week?

After Beta1 is out, not sure what should happen with the savara hudson job? Currently I have removed the link to the aggregate project, and commented out the publish, as because it references the jbosstools trunk, it means that it would publish the Savara trunk artifacts to the Beta2 publish site - which would not be correct (as Savara trunk will be for new development).

The only other way would be to create tags for beta1 and beta2, and separate hudson jobs, but this would be overkill as there is unlikely to be any changes over the following week until beta1 is released. So possibly best to leave Savara hudson job detached for now, and then when JBT3.3.x builds start, then aggregate it again.

(will see about pi4soa next)

> 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: Gary Brown
>             Fix For: 3.2.0.Beta1
>
>         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