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

[Nick Boldt (JIRA)]

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

Nick Boldt edited comment on JBIDE-6927 at 9/23/10 8:11 PM:
------------------------------------------------------------

> how the result gets aggregated

This is controlled by the aggregate build's config files: http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/site/pom.xml lists the URLs from which we suck in jars.

Thus if you publish to a new URL, I'll just have to update the pom.xml accordingly.

Feel free to copy the jobs and re-assign this to me to update the above file (or if you have write access, you can DIY in both the 3.2.0.Beta1 branch and in trunk).

> Currently the pi4soa feature is only in the All category

To move your feature(s) into different categor(ies) simply edit this file:

http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/site/site.xml

Whether or not you should be in ALL, SOA, or both is not for me to decide: ask Max.


      was (Author: nickboldt):
    > how the result gets aggregated

This is controlled by the aggregate build's config files: http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/site/pom.xml lists the URLs from which we suck in jars.

Thus if you publish to a new URL, I'll just have to update the pom.xml accordingly.

Feel free to copy the jobs and re-assign this to me to update the above file (or if you have write access, you can DIY in both the 3.2.0.Beta1 branch and in trunk).

> To move your feature(s) into different categor(ies) simply edit this file:

http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/site/site.xml

Whether or not you should be in ALL, SOA, or both is not for me to decide: ask Max.

  
> 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.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