Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-6927

Integrate Savara plugins into JBoss Tools

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Major
    • 3.2.0.Beta1
    • None
    • None
    • None

    Description

      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

      Attachments

        Activity

          People

            nickboldt Nick Boldt
            gary@brownuk.com Gary Brown
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: