[jbosstools-issues] [JBoss JIRA] (JBIDE-24173) rename docker tooling N&N files so they appear in JBoss Tools N&N pages

[Nick Boldt (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-24173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Boldt reassigned JBIDE-24173:
----------------------------------

    Assignee: Nick Boldt


> rename docker tooling N&N files so they appear in JBoss Tools N&N pages
> -----------------------------------------------------------------------
>
>                 Key: JBIDE-24173
>                 URL: https://issues.jboss.org/browse/JBIDE-24173
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: docker, website
>    Affects Versions: 4.4.4.AM2
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>             Fix For: 4.4.4.AM2
>
>
> Noticed today thanks to [~jjohnstn] that there is no Docker Tooling N&N after JBoss Tools 4.3.1.
> I suspect this is due to the fact that the filenames are named thus:
> {code}
> docker-news-1.0.0.Mars0.adoc
> docker-news-1.1.0-jbt-4.3.0.Final.adoc
> docker-news-1.1.0.Mars1.adoc
> docker-news-1.2.0.Mars2.adoc
> docker-news-2.0.0.Neon0.adoc
> docker-news-2.0.0.NeonM7.adoc
> docker-news-2.1.0.Neon1.sprint118.adoc
> docker-news-2.1.0.Neon1.sprint119.adoc
> {code}
> And the latest N&N for Docker is this page:
> http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.1.Final.html#docker
> Whereas for Forge, which DOES have N&N showing up, we see filenames like this:
> {code}
> forge-news-4.4.2.AM2.adoc
> forge-news-4.4.2.AM3.adoc
> forge-news-4.4.2.Final.adoc
> forge-news-4.4.3.Final.adoc
> forge-news-4.4.4.AM1.adoc
> {code}
> And therefore we see Forge N&N:
> http://tools.jboss.org/documentation/whatsnew/jbosstools/4.4.4.AM1.html#forge
> http://tools.jboss.org/documentation/whatsnew/jbosstools/4.4.3.Final.html#forge
> http://tools.jboss.org/documentation/whatsnew/jbosstools/4.4.2.Final.html#forge
> [~xcoulon] Is this a correct interpretation? I can rename the files is so.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)