[jbosstools-issues] [JBoss JIRA] (JBTIS-192) add update site to jbosstools-integration-stack-tests repo and publish site onto dl.jb.org

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBTIS-192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12824078#comment-12824078 ] 

Nick Boldt commented on JBTIS-192:
----------------------------------

Looks good but I notice a bug in my html template (for sites which have no features, the features/ and site.properties link should be removed) - JBIDE-15760

Also notice that both master and 4.1.kepler are called Beta1. Surely the master branch would be Alpha1?
                
> add update site to jbosstools-integration-stack-tests repo and publish site onto dl.jb.org
> ------------------------------------------------------------------------------------------
>
>                 Key: JBTIS-192
>                 URL: https://issues.jboss.org/browse/JBTIS-192
>             Project: JBoss Tools Integration Stack
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: distribution, QE, releng, testing
>    Affects Versions: 4.1.3.Beta5
>            Reporter: Nick Boldt
>            Assignee: Andrej Podhradsky
>             Fix For: 4.1.3.Beta5
>
>
> In the past, we had this site:
> http://download.jboss.org/jbosstools/updates/nightly/soatests/trunk/
> Which was built from here:
> https://github.com/jbosstools/jbosstools-build-sites/tree/master/aggregate/soa-site/site
> In the future, we should have a similar site build for the contents of the new https://github.com/jbosstools/jbosstools-integration-stack-tests/tree/master/ repo (note that features are not needed -- your category.xml can include <bundle> instead of <feature> and the plugins will therefore be accessible from the site).
> Then you can publish this site to here:
> http://download.jboss.org/jbosstools/updates/integration/kepler/integration-stack/tests/ (or similar URL)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira