Changes for page Building XWiki from sources

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-xwiki:XWiki.VincentMassol
	1	+xwiki:XWiki.ThomasMortagne

Content

...	...	@@ -4,7 +4,7 @@
4	4
5	5	{{error}}
6	6	* Use Java 8 (Java 9+ is not supported yet)
7		-* Make sure you install a Maven version >= 3.5.0. Note that our [[CI>>http://ci.xwiki.org]] builds XWiki using Maven 3.6.0 and thus this is our recommended version.
	7	+* Make sure you install a Maven version >= 3.5.0. Note that our [[CI>>http://ci.xwiki.org]] builds XWiki using Maven 3.6.2 and thus this is our recommended version.
8	8	* Windows users have several choices for getting past the [[long paths issue>>https://github.com/msysgit/git/pull/122]] (255 char limitation on Windows) and building XWiki:
9	9	** Use either [[GitHub Desktop>>https://desktop.github.com/]] or [[Git for Windows>>https://git-for-windows.github.io/]] and set ##core.longpaths## to ##True##: {{code}}git config --global core.longpaths true{{/code}}.
10	10	** Use [[Cygwin>>https://www.cygwin.com/]] which works out of the box.
...	...	@@ -211,7 +211,9 @@
211	211	*** [[xwiki-commons pitest job >>http://ci.xwiki.org/job/xwiki-commons_pitest/]]
212	212	*** [[xwiki-rendering pitest job >>http://ci.xwiki.org/job/xwiki-rendering_pitest/]]
213	213	*** [[xwiki-platform pitest job >>http://ci.xwiki.org/job/xwiki-platform_pitest/]]
214		-* Verify that JUnit tests don't output content to stdout or stderr. Tests are supposed to either configure the code to not output anything or if it's expected then they're supposed to [[catch the logs and assert them>>dev:Community.Testing.JavaUnitTesting.WebHome#HCapturingandAssertingLogs]]. Note that this check is also executing for JUnit5 tests executed in your IDE (if the ##pom.xml## file in the current directory doesn't have the ##xwiki.surefire.captureconsole.skip## Maven property set to true).
	214	+* Verify Test output
	215	+** Verify that JUnit tests don't output content to stdout or stderr. Tests are supposed to either configure the code to not output anything or if it's expected then they're supposed to [[catch the logs and assert them>>dev:Community.Testing.JavaUnitTesting.WebHome#HCapturingandAssertingLogs]]. Note that this check is also executing for JUnit5 tests executed in your IDE (if the ##pom.xml## file in the current directory doesn't have the ##xwiki.surefire.captureconsole.skip## Maven property set to true).
	216	+** Verify that functional tests don't contain errors or warnings when they execute. See [[Docker Tests>>Community.Testing.DockerTesting.WebHome||anchor="HStdout2Fstderrvalidationerrors"]] (for JUnit5) and [[Selenium2 Tests>>Community.Testing.WebHome||anchor="HBestpractices"]] (for JUnit4).
215	215
216	216	= Tips =
217	217