[JBoss JIRA] (JBIDE-23624) clean up skipTests / swtbot.tests.skip references in integration tests
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23624?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23624:
-------------------------------
Fix Version/s: 4.4.3.AM1
> clean up skipTests / swtbot.tests.skip references in integration tests
> ----------------------------------------------------------------------
>
> Key: JBIDE-23624
> URL: https://issues.jboss.org/browse/JBIDE-23624
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Affects Versions: 4.4.2.Final
> Reporter: Nick Boldt
> Fix For: 4.4.3.AM1
>
>
> Rob said:
> {quote}
> swtbot.test.skip is old and shouldnt exist anymore {quote}
> {code}
> $➔ find.sh . "pom.xml" swtbot.test.skip
> ** [1] ./tests/org.jboss.tools.easymport.ui.bot.test/pom.xml **
> 14- <packaging>eclipse-test-plugin</packaging>
> 15- <properties>
> 16: <swtbot.test.skip>false</swtbot.test.skip>
> 17- <usage_reporting_enabled>false</usage_reporting_enabled>
> 18- <maven.test.failure.ignore>true</maven.test.failure.ignore>
> {code}
> Andre said:
> {quote}
> this seems to make no sense at all. These are tests. Why would you want to skip them by default?{quote}
> {code}
> ** [1] ./tests/org.jboss.tools.ui.bot.ext.test/pom.xml **
> 13-
> 14- <properties>
> 15: <skipTests>true</skipTests>
> 16- </properties>
> 17-</project>
> ** [2] ./tests/pom.xml **
> 22- <junitExtensionsProperties>-Dreddeer.close.shells=${reddeer.close.shells} -Dreddeer.close.welcome.screen=${reddeer.close.welcome.screen} -Dreddeer.disable.maven.download.repo.index.on.startup=${reddeer.disable.maven.download.repo.index.on.startup}</junitExtensionsProperties>
> 23- <integrationTestsSystemProperties>-Dswt.bot.test.record.screencast=${swt.bot.test.record.screencast} -Dorg.eclipse.swtbot.screenshots.dir=${project.build.directory}/screenshots -Dusage_reporting_enabled=false -Dcom.atlassian.connector.eclipse.monitor.usage.first.time=false -Dcom.atlassian.connector.eclipse.monitor.usage.enabled=false ${junitExtensionsProperties}</integrationTestsSystemProperties>
> 24: <skipTests>true</skipTests>
> 25- <test.installPath.OSX></test.installPath.OSX>
> 26- <devstudio.repository>https://devstudio.redhat.com/10.0/snapshots/updates/</devstudio.repository>
> {code}
> There are also three examples of hardcoding skipTests to false, for no obvious reason:
> {code}
> $➔ find.sh . "pom.xml" \<skipTests\>false
> ** [1] ./tests/org.jboss.ide.eclipse.as.ui.bot.test/pom.xml **
> 19- -->
> 20- <properties>
> 21: <skipTests>false</skipTests>
> 22- <usage_reporting_enabled>false</usage_reporting_enabled>
> 23- <!-- Maven configuration -->
> ** [2] ./tests/org.jboss.tools.arquillian.ui.bot.test/pom.xml **
> 14- <packaging>eclipse-test-plugin</packaging>
> 15- <properties>
> 16: <skipTests>false</skipTests>
> 17- <usage_reporting_enabled>false</usage_reporting_enabled>
> 18- <maven.test.failure.ignore>true</maven.test.failure.ignore>
> ** [3] ./tests/org.jboss.tools.examples.ui.bot.test/pom.xml **
> 30- <jbosstools.test.jboss-eap-7.x.url>http://download.eng.brq.redhat.com/released/JBEAP-7/7.0.0/jboss-eap-7.0.0...</jbosstools.test.jboss-eap-7.x.url>
> 31- <surefire.timeout>18000</surefire.timeout>
> 32: <skipTests>false</skipTests>
> 33- <deployOnServer>true</deployOnServer>
> 34- </properties>
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 7 months
[JBoss JIRA] (JBIDE-23624) clean up skipTests / swtbot.tests.skip references in integration tests
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23624?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-23624:
----------------------------------
Assignee: Nick Boldt
> clean up skipTests / swtbot.tests.skip references in integration tests
> ----------------------------------------------------------------------
>
> Key: JBIDE-23624
> URL: https://issues.jboss.org/browse/JBIDE-23624
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Affects Versions: 4.4.2.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.3.AM1
>
>
> Rob said:
> {quote}
> swtbot.test.skip is old and shouldnt exist anymore {quote}
> {code}
> $➔ find.sh . "pom.xml" swtbot.test.skip
> ** [1] ./tests/org.jboss.tools.easymport.ui.bot.test/pom.xml **
> 14- <packaging>eclipse-test-plugin</packaging>
> 15- <properties>
> 16: <swtbot.test.skip>false</swtbot.test.skip>
> 17- <usage_reporting_enabled>false</usage_reporting_enabled>
> 18- <maven.test.failure.ignore>true</maven.test.failure.ignore>
> {code}
> Andre said:
> {quote}
> this seems to make no sense at all. These are tests. Why would you want to skip them by default?{quote}
> {code}
> ** [1] ./tests/org.jboss.tools.ui.bot.ext.test/pom.xml **
> 13-
> 14- <properties>
> 15: <skipTests>true</skipTests>
> 16- </properties>
> 17-</project>
> ** [2] ./tests/pom.xml **
> 22- <junitExtensionsProperties>-Dreddeer.close.shells=${reddeer.close.shells} -Dreddeer.close.welcome.screen=${reddeer.close.welcome.screen} -Dreddeer.disable.maven.download.repo.index.on.startup=${reddeer.disable.maven.download.repo.index.on.startup}</junitExtensionsProperties>
> 23- <integrationTestsSystemProperties>-Dswt.bot.test.record.screencast=${swt.bot.test.record.screencast} -Dorg.eclipse.swtbot.screenshots.dir=${project.build.directory}/screenshots -Dusage_reporting_enabled=false -Dcom.atlassian.connector.eclipse.monitor.usage.first.time=false -Dcom.atlassian.connector.eclipse.monitor.usage.enabled=false ${junitExtensionsProperties}</integrationTestsSystemProperties>
> 24: <skipTests>true</skipTests>
> 25- <test.installPath.OSX></test.installPath.OSX>
> 26- <devstudio.repository>https://devstudio.redhat.com/10.0/snapshots/updates/</devstudio.repository>
> {code}
> There are also three examples of hardcoding skipTests to false, for no obvious reason:
> {code}
> $➔ find.sh . "pom.xml" \<skipTests\>false
> ** [1] ./tests/org.jboss.ide.eclipse.as.ui.bot.test/pom.xml **
> 19- -->
> 20- <properties>
> 21: <skipTests>false</skipTests>
> 22- <usage_reporting_enabled>false</usage_reporting_enabled>
> 23- <!-- Maven configuration -->
> ** [2] ./tests/org.jboss.tools.arquillian.ui.bot.test/pom.xml **
> 14- <packaging>eclipse-test-plugin</packaging>
> 15- <properties>
> 16: <skipTests>false</skipTests>
> 17- <usage_reporting_enabled>false</usage_reporting_enabled>
> 18- <maven.test.failure.ignore>true</maven.test.failure.ignore>
> ** [3] ./tests/org.jboss.tools.examples.ui.bot.test/pom.xml **
> 30- <jbosstools.test.jboss-eap-7.x.url>http://download.eng.brq.redhat.com/released/JBEAP-7/7.0.0/jboss-eap-7.0.0...</jbosstools.test.jboss-eap-7.x.url>
> 31- <surefire.timeout>18000</surefire.timeout>
> 32: <skipTests>false</skipTests>
> 33- <deployOnServer>true</deployOnServer>
> 34- </properties>
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 7 months
[JBoss JIRA] (JBIDE-23624) clean up skipTests / swtbot.tests.skip references in integration tests
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23624?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23624:
-------------------------------
Affects Version/s: 4.4.2.Final
> clean up skipTests / swtbot.tests.skip references in integration tests
> ----------------------------------------------------------------------
>
> Key: JBIDE-23624
> URL: https://issues.jboss.org/browse/JBIDE-23624
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Affects Versions: 4.4.2.Final
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Fix For: 4.4.3.AM1
>
>
> Rob said:
> {quote}
> swtbot.test.skip is old and shouldnt exist anymore {quote}
> {code}
> $➔ find.sh . "pom.xml" swtbot.test.skip
> ** [1] ./tests/org.jboss.tools.easymport.ui.bot.test/pom.xml **
> 14- <packaging>eclipse-test-plugin</packaging>
> 15- <properties>
> 16: <swtbot.test.skip>false</swtbot.test.skip>
> 17- <usage_reporting_enabled>false</usage_reporting_enabled>
> 18- <maven.test.failure.ignore>true</maven.test.failure.ignore>
> {code}
> Andre said:
> {quote}
> this seems to make no sense at all. These are tests. Why would you want to skip them by default?{quote}
> {code}
> ** [1] ./tests/org.jboss.tools.ui.bot.ext.test/pom.xml **
> 13-
> 14- <properties>
> 15: <skipTests>true</skipTests>
> 16- </properties>
> 17-</project>
> ** [2] ./tests/pom.xml **
> 22- <junitExtensionsProperties>-Dreddeer.close.shells=${reddeer.close.shells} -Dreddeer.close.welcome.screen=${reddeer.close.welcome.screen} -Dreddeer.disable.maven.download.repo.index.on.startup=${reddeer.disable.maven.download.repo.index.on.startup}</junitExtensionsProperties>
> 23- <integrationTestsSystemProperties>-Dswt.bot.test.record.screencast=${swt.bot.test.record.screencast} -Dorg.eclipse.swtbot.screenshots.dir=${project.build.directory}/screenshots -Dusage_reporting_enabled=false -Dcom.atlassian.connector.eclipse.monitor.usage.first.time=false -Dcom.atlassian.connector.eclipse.monitor.usage.enabled=false ${junitExtensionsProperties}</integrationTestsSystemProperties>
> 24: <skipTests>true</skipTests>
> 25- <test.installPath.OSX></test.installPath.OSX>
> 26- <devstudio.repository>https://devstudio.redhat.com/10.0/snapshots/updates/</devstudio.repository>
> {code}
> There are also three examples of hardcoding skipTests to false, for no obvious reason:
> {code}
> $➔ find.sh . "pom.xml" \<skipTests\>false
> ** [1] ./tests/org.jboss.ide.eclipse.as.ui.bot.test/pom.xml **
> 19- -->
> 20- <properties>
> 21: <skipTests>false</skipTests>
> 22- <usage_reporting_enabled>false</usage_reporting_enabled>
> 23- <!-- Maven configuration -->
> ** [2] ./tests/org.jboss.tools.arquillian.ui.bot.test/pom.xml **
> 14- <packaging>eclipse-test-plugin</packaging>
> 15- <properties>
> 16: <skipTests>false</skipTests>
> 17- <usage_reporting_enabled>false</usage_reporting_enabled>
> 18- <maven.test.failure.ignore>true</maven.test.failure.ignore>
> ** [3] ./tests/org.jboss.tools.examples.ui.bot.test/pom.xml **
> 30- <jbosstools.test.jboss-eap-7.x.url>http://download.eng.brq.redhat.com/released/JBEAP-7/7.0.0/jboss-eap-7.0.0...</jbosstools.test.jboss-eap-7.x.url>
> 31- <surefire.timeout>18000</surefire.timeout>
> 32: <skipTests>false</skipTests>
> 33- <deployOnServer>true</deployOnServer>
> 34- </properties>
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 7 months
[JBoss JIRA] (JBIDE-23624) clean up skipTests / swtbot.tests.skip references in integration tests
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23624?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-23624:
----------------------------------
Assignee: Rob Stryker (was: Nick Boldt)
> clean up skipTests / swtbot.tests.skip references in integration tests
> ----------------------------------------------------------------------
>
> Key: JBIDE-23624
> URL: https://issues.jboss.org/browse/JBIDE-23624
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Affects Versions: 4.4.2.Final
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Fix For: 4.4.3.AM1
>
>
> Rob said:
> {quote}
> swtbot.test.skip is old and shouldnt exist anymore {quote}
> {code}
> $➔ find.sh . "pom.xml" swtbot.test.skip
> ** [1] ./tests/org.jboss.tools.easymport.ui.bot.test/pom.xml **
> 14- <packaging>eclipse-test-plugin</packaging>
> 15- <properties>
> 16: <swtbot.test.skip>false</swtbot.test.skip>
> 17- <usage_reporting_enabled>false</usage_reporting_enabled>
> 18- <maven.test.failure.ignore>true</maven.test.failure.ignore>
> {code}
> Andre said:
> {quote}
> this seems to make no sense at all. These are tests. Why would you want to skip them by default?{quote}
> {code}
> ** [1] ./tests/org.jboss.tools.ui.bot.ext.test/pom.xml **
> 13-
> 14- <properties>
> 15: <skipTests>true</skipTests>
> 16- </properties>
> 17-</project>
> ** [2] ./tests/pom.xml **
> 22- <junitExtensionsProperties>-Dreddeer.close.shells=${reddeer.close.shells} -Dreddeer.close.welcome.screen=${reddeer.close.welcome.screen} -Dreddeer.disable.maven.download.repo.index.on.startup=${reddeer.disable.maven.download.repo.index.on.startup}</junitExtensionsProperties>
> 23- <integrationTestsSystemProperties>-Dswt.bot.test.record.screencast=${swt.bot.test.record.screencast} -Dorg.eclipse.swtbot.screenshots.dir=${project.build.directory}/screenshots -Dusage_reporting_enabled=false -Dcom.atlassian.connector.eclipse.monitor.usage.first.time=false -Dcom.atlassian.connector.eclipse.monitor.usage.enabled=false ${junitExtensionsProperties}</integrationTestsSystemProperties>
> 24: <skipTests>true</skipTests>
> 25- <test.installPath.OSX></test.installPath.OSX>
> 26- <devstudio.repository>https://devstudio.redhat.com/10.0/snapshots/updates/</devstudio.repository>
> {code}
> There are also three examples of hardcoding skipTests to false, for no obvious reason:
> {code}
> $➔ find.sh . "pom.xml" \<skipTests\>false
> ** [1] ./tests/org.jboss.ide.eclipse.as.ui.bot.test/pom.xml **
> 19- -->
> 20- <properties>
> 21: <skipTests>false</skipTests>
> 22- <usage_reporting_enabled>false</usage_reporting_enabled>
> 23- <!-- Maven configuration -->
> ** [2] ./tests/org.jboss.tools.arquillian.ui.bot.test/pom.xml **
> 14- <packaging>eclipse-test-plugin</packaging>
> 15- <properties>
> 16: <skipTests>false</skipTests>
> 17- <usage_reporting_enabled>false</usage_reporting_enabled>
> 18- <maven.test.failure.ignore>true</maven.test.failure.ignore>
> ** [3] ./tests/org.jboss.tools.examples.ui.bot.test/pom.xml **
> 30- <jbosstools.test.jboss-eap-7.x.url>http://download.eng.brq.redhat.com/released/JBEAP-7/7.0.0/jboss-eap-7.0.0...</jbosstools.test.jboss-eap-7.x.url>
> 31- <surefire.timeout>18000</surefire.timeout>
> 32: <skipTests>false</skipTests>
> 33- <deployOnServer>true</deployOnServer>
> 34- </properties>
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 7 months
[JBoss JIRA] (JBIDE-23624) clean up skipTests / swtbot.tests.skip references in integration tests
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-23624:
----------------------------------
Summary: clean up skipTests / swtbot.tests.skip references in integration tests
Key: JBIDE-23624
URL: https://issues.jboss.org/browse/JBIDE-23624
Project: Tools (JBoss Tools)
Issue Type: Bug
Reporter: Nick Boldt
Rob said:
{quote}
swtbot.test.skip is old and shouldnt exist anymore {quote}
{code}
$➔ find.sh . "pom.xml" swtbot.test.skip
** [1] ./tests/org.jboss.tools.easymport.ui.bot.test/pom.xml **
14- <packaging>eclipse-test-plugin</packaging>
15- <properties>
16: <swtbot.test.skip>false</swtbot.test.skip>
17- <usage_reporting_enabled>false</usage_reporting_enabled>
18- <maven.test.failure.ignore>true</maven.test.failure.ignore>
{code}
Andre said:
{quote}
this seems to make no sense at all. These are tests. Why would you want to skip them by default?{quote}
{code}
** [1] ./tests/org.jboss.tools.ui.bot.ext.test/pom.xml **
13-
14- <properties>
15: <skipTests>true</skipTests>
16- </properties>
17-</project>
** [2] ./tests/pom.xml **
22- <junitExtensionsProperties>-Dreddeer.close.shells=${reddeer.close.shells} -Dreddeer.close.welcome.screen=${reddeer.close.welcome.screen} -Dreddeer.disable.maven.download.repo.index.on.startup=${reddeer.disable.maven.download.repo.index.on.startup}</junitExtensionsProperties>
23- <integrationTestsSystemProperties>-Dswt.bot.test.record.screencast=${swt.bot.test.record.screencast} -Dorg.eclipse.swtbot.screenshots.dir=${project.build.directory}/screenshots -Dusage_reporting_enabled=false -Dcom.atlassian.connector.eclipse.monitor.usage.first.time=false -Dcom.atlassian.connector.eclipse.monitor.usage.enabled=false ${junitExtensionsProperties}</integrationTestsSystemProperties>
24: <skipTests>true</skipTests>
25- <test.installPath.OSX></test.installPath.OSX>
26- <devstudio.repository>https://devstudio.redhat.com/10.0/snapshots/updates/</devstudio.repository>
{code}
There are also three examples of hardcoding skipTests to false, for no obvious reason:
{code}
$➔ find.sh . "pom.xml" \<skipTests\>false
** [1] ./tests/org.jboss.ide.eclipse.as.ui.bot.test/pom.xml **
19- -->
20- <properties>
21: <skipTests>false</skipTests>
22- <usage_reporting_enabled>false</usage_reporting_enabled>
23- <!-- Maven configuration -->
** [2] ./tests/org.jboss.tools.arquillian.ui.bot.test/pom.xml **
14- <packaging>eclipse-test-plugin</packaging>
15- <properties>
16: <skipTests>false</skipTests>
17- <usage_reporting_enabled>false</usage_reporting_enabled>
18- <maven.test.failure.ignore>true</maven.test.failure.ignore>
** [3] ./tests/org.jboss.tools.examples.ui.bot.test/pom.xml **
30- <jbosstools.test.jboss-eap-7.x.url>http://download.eng.brq.redhat.com/released/JBEAP-7/7.0.0/jboss-eap-7.0.0...</jbosstools.test.jboss-eap-7.x.url>
31- <surefire.timeout>18000</surefire.timeout>
32: <skipTests>false</skipTests>
33- <deployOnServer>true</deployOnServer>
34- </properties>
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 7 months
[JBoss JIRA] (JBIDE-23471) Cannot launch central after devstudio install - unable to open jbosstools-central-webpage.zip
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23471?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-23471:
-------------------------------------
I have no idea what would cause this. but can you try the following to reproduce the error:
- stop jbds
- delete /Users/rasp/jbossqa/JBDS/10.0.0/workspace-10.2.0.AM3-6372/.metadata/.plugins/org.jboss.tools.central/
- go offline
- open jbds / central
> Cannot launch central after devstudio install - unable to open jbosstools-central-webpage.zip
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-23471
> URL: https://issues.jboss.org/browse/JBIDE-23471
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.4.2.AM3
> Reporter: Martin Malina
> Assignee: Fred Bricon
> Attachments: central-error.png
>
>
> I just installed devstudio 10.2.0.AM3 [1] and launched it and I saw this error pop up immediately:
> {code}
> Unable to open /Users/rasp/jbossqa/JBDS/10.0.0/devstudio-10.2.0.AM3-6372/studio/devstudio.app/Contents/Eclipse/plugins/org.jboss.tools.central_2.1.2.v20160922-1945/resources/jbosstools-central-webpage.zip
> /Users/rasp/jbossqa/JBDS/10.0.0/workspace-10.2.0.AM3-6372/.metadata/.plugins/org.jboss.tools.central/central/dff8cd5/index.html can not be found
> {code}
> !central-error.png!
> JBoss Central page could not be loaded.
> Unfortunately I seem to be the only one seeing this. Radim and Ondrej both said it works for them. Rasto said he saw something similar in Error Log last week.
> [1] devstudio-10.2.0.AM3-v20161104-1659-B6372-installer-eap.jar
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 7 months
[JBoss JIRA] (JBIDE-23550) Central New and Noteworthy for 4.4.2.Final
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23550?page=com.atlassian.jira.plugi... ]
Fred Bricon closed JBIDE-23550.
-------------------------------
Resolution: Rejected
nothing new here
> Central New and Noteworthy for 4.4.2.Final
> -----------------------------------------------------
>
> Key: JBIDE-23550
> URL: https://issues.jboss.org/browse/JBIDE-23550
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central, maven, project-examples
> Reporter: Jeff MAURY
> Assignee: Fred Bricon
> Priority: Critical
>
> Search for your component's New and Noteworthy issues:
> Queries:
> * [Completed Central JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...]
> * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...]
> * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...]
> * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...]
> If no N&N issues are found for Central, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them.
> Document the ones relevant for Central by submitting a pull request against:
> * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio...
> If your PR's commit comment is of the form 'JBIDE-56789 #comment Create N&N for Central4.4.2.Final #close', and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied.
> If there is nothing new or noteworthy for Central for this milestone, please *reject* and *close* this issue.
> ----
> If there is nothing new or noteworthy for 4.4.2.Final since the AM3 release of Central, please *reject* and *close* this issue. The final N&N page will be aggregated from all previous N&N documents.
> If you want to _add a comment to the final document_ then submit a PR to create a separate <component>-news-4.4.2.Final.adoc file here:
> * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio...
> The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc.
> However, if you want to _replace all previous N&Ns by a *new* document_, then submit a PR to create a *new* <component>-news-4.4.2.Final.adoc file, adding: {code}page-include-previous: false{code}.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 7 months