[jbosstools-issues] [JBoss JIRA] (TOOLSDOC-304) no JBT 4.0.x docs on docs.jboss.org/tools/!

[Nick Boldt (JIRA)]

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

Nick Boldt edited comment on TOOLSDOC-304 at 4/9/13 12:36 PM:
--------------------------------------------------------------

JIRA workflow for TOOLSDOC doesn't allow me to set a PR, so here's a link:

https://github.com/jbosstools/jbosstools-documentation/pull/48

[~maxandersen] or [~mmurray], any idea how to change TOOLSDOC to support linking pull requests?

Resulting index page would look like this:

!http://snag.gy/a9QY6.jpg!
                
      was (Author: nickboldt):
    JIRA workflow for TOOLSDOC doesn't allow me to set a PR, so here's a link:

https://github.com/jbosstools/jbosstools-documentation/pull/48

[~maxandersen] or [~mmurray], any idea how to change TOOLSDOC to support linking pull requests?
                  
> no JBT 4.0.x docs on docs.jboss.org/tools/!
> -------------------------------------------
>
>                 Key: TOOLSDOC-304
>                 URL: https://issues.jboss.org/browse/TOOLSDOC-304
>             Project: Documentation for JBoss Tools and Developer Studio
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Update Guide
>    Affects Versions: 3.3.0.Final, 4.0.0.Final, 4.0.1, 4.1.0
>            Reporter: Nick Boldt
>            Assignee: Michelle Murray
>
> Realized today that we have only 1 nightly site for JBT docs, and that there are no 4.0.x docs available.
> So... here's a new job:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_6.0.juno/job/jbosstools-docs_40/
> Next, I'll attach a PR for a better index.html page to be pushed to the root of http://docs.jboss.org/tools/ so that the output from the above job can be seen on the server. We should also put back links to the 3.x docs.

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