[
https://issues.jboss.org/browse/JBIDE-22199?page=com.atlassian.jira.plugi...
]
Alexey Kazakov commented on JBIDE-22199:
----------------------------------------
{quote}Xavier said it doesn't work because there is no item in the releases yaml, but
it was suggested to try and create an empty item as a workaround. Whether or not this has
been done I don't know - I don't see any such commit in the repo.{quote}
This was done for
tools.stage.jboss.org and has been pushed to
tools.jboss.org by now.
But we need to improve this aggregation mechanism. Why just not to trigger aggregation
when any .Final.adoc is available? Something to look at for next releases.
N&N for Betas are not aggregated into 4.3.1.Final
-------------------------------------------------
Key: JBIDE-22199
URL:
https://issues.jboss.org/browse/JBIDE-22199
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: website
Affects Versions: 4.3.1.Final
Reporter: Martin Malina
Assignee: Xavier Coulon
Fix For: 4.4.x
As discussed yesterday on hipchat, this doesn't work as expected.
http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.1.Final.html
should contain new features for cr1/final as well as relevant features from Beta1 and
Beta2:
http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.1.Beta1.html
http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.1.Beta2.html
Xavier said it doesn't work because there is no item in the releases yaml, but it was
suggested to try and create an empty item as a workaround. Whether or not this has been
done I don't know - I don't see any such commit in the repo.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)