[jbosstools-issues] [JBoss JIRA] (JBIDE-19345) allow NN to be filtered/redefined for NN

[Alexey Kazakov (JIRA)]

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

Alexey Kazakov updated JBIDE-19345:
-----------------------------------
    Fix Version/s: 4.2.3.Final
                       (was: 4.2.3.CR1)


> allow NN to be filtered/redefined for NN
> ----------------------------------------
>
>                 Key: JBIDE-19345
>                 URL: https://issues.jboss.org/browse/JBIDE-19345
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: website
>            Reporter: Max Rydahl Andersen
>            Assignee: Xavier Coulon
>            Priority: Critical
>             Fix For: 4.2.3.Final, 4.3.0.CR1
>
>
> there been examples of auto aggregation of NN be a hit or miss for how much it makes sense in the release.
> For example:
> Beta1: Added a few components to the Ionic Palette: <c1> <c2> <c3>
> Beta2: Added a few components to the Ionic: <c4> <c5>
> Alexey Kazakov: But in the final verision I would like to have: Added new components: <c1>,...<c5>.
> One suggestion been to have ability to rewrite the full NN version at final but I just know that will kill us becase it is going to be a pain to copy/paste right.
> Alternative suggestion is:
> A) during rendering of the "final" aggregation set a asciidoc variable (i.e. "finalnn") allowing us to use asciidoc conditionals like 
> {code}
> ifndef::finalnn[]
> This piece of news was only relevant for Beta1
> endif::finalnn[]
> {code}
> See: http://mrhaki.blogspot.ch/2014/08/awesome-asciidoc-using-conditional.html
> B) allow to add a .Final newnoteworthy adoc to use as place to write the aggregated news ..note, these should still be merged with the former NN's. so you only need to write the sections that are actually different. 



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)