[jira] [Created] (SUREFIRE-1871) Usage of invalid XML tags

["Andrea Stedile (Jira)" <ji...@apache.org>]

Andrea Stedile created SUREFIRE-1871:
----------------------------------------

             Summary: Usage of invalid XML tags
                 Key: SUREFIRE-1871
                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1871
             Project: Maven Surefire
          Issue Type: Bug
          Components: Maven Failsafe Plugin
    Affects Versions: 3.0.0-M5
            Reporter: Andrea Stedile


To understand this issue, please, read my stackoverflow answer.
 [https://stackoverflow.com/a/65572096/14751136]

This issue is related to Maven Surefire's example:
 [https://maven.apache.org/surefire/maven-failsafe-plugin/usage.html]]:

Also, see the related issue, where I propose an update of jetty-maven-plugin to 11.

I think it should not be necessary to set *_daemon_* to true.
 In facts, I do not see a reference to it in Jetty 9's programming guide.
[https://www.eclipse.org/jetty/documentation/jetty-9/index.html]
 Search for a paragraph containing the following text:
 _For example, you can configure the plugin to start your webapp at the beginning of your unit tests and stop at the end. To do this, you need to set up a couple of execution scenarios for the Jetty plugin. You use the pre-integration-test and post-integration-test Maven build phases to trigger the execution and termination of Jetty:_
 The paragraph is the followed by the required code, which doesn't mention _daemon_.

===> It is not even mentioned in Jetty 11, for which I proposed an update in a related issue.
[https://www.eclipse.org/jetty/documentation/jetty-11/programming_guide.php]
 

If we update to Jetty 11, _scanIntervalSeconds_ should be replaced with *_scan_*.
 In Jetty 11 (latest) documentation:
 [https://www.eclipse.org/jetty/documentation/jetty-11/programming_guide.php]
 Search for a paragraph containing the following text:
 _Here is an example, which turns on scanning for changes every ten seconds, and sets the webapp context path to /test_
 And also for this one:
 _Here’s an example of using the pre-integration-test and post-integration-test Maven build phases to trigger the execution and termination of Jetty:_
 You will see that, in both paragraphs, instead of using _scanIntervalSeconds_, _*scan*_ is used.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)