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

[Michelle Murray (JIRA)]

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

Michelle Murray commented on TOOLSDOC-304:
------------------------------------------

I don't follow.

4.0.x docs are here :http://www.jboss.org/tools/docs/reference
These are listed as 4.0.0 as no changes were made for 4.0.1

As far as I can see, nightly builds for docs are only needed for the latest docs and these are built with:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-docs-nightly/

Any ad hoc changes to 4.0.x docs will end up being done on an ad hoc basis and so books can be built and pushed immediately. I can't see that a nightly build from the 4.0.x branch is useful. I think I've missed something.

Nick?
                
> 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/
> Which publishes here:
> http://docs.jboss.org/tools/nightly/4.0.juno/
> 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