https://issues.apache.org/bugzilla/show_bug.cgi?id=50324
--- Comment #5 from Sebb <[email protected]> 2012-01-17 23:51:07 UTC --- [Recording some extra info for completeness] Any Maven implementation would need to allow for the following: 1) Documentation is in XML, which is processed using Velocity to create the website. A separate build using different template/macros is used to generate the help files included in the binary archive. Two of those files (functions.html and component_reference.html) are used to provide help within the application itself; this requires correlation of text anchors in the HTML with the test element names. 2) JMeter assumes that all jars are in lib/ and user.classpath or lib/ext and search_paths. The former is used for support classes only; the latter is used for JMeter plugins. 3) The release build updates the version displayed by the application to include the SVN revision. 4) Some of the test classes require a lot of setup to ensure that the classpath is correct. This is normally done by the class org.apache.jorphan.test.AllTests which finds and runs all the tests. Some tests can be run stand-alone, but many cannot at present. 5) The tar.gz and zip archives use EOL=LF and EOL=CRLF for eol=native files. Some source files need to be LF and some need to be CRLF regardless of archive type. 6) The binary release contains all the dependencies, and so requires different NOTICE and LICENSE files from the source release. 7) The tests need to be runnable with headless=true for Gump and Jenkins and other CI systems 8) As well as the unit tests, there are several script tests. One script is run both stand-alone (non-GUI) and in client-server mode, which requires starting an instance of JMeter server in parallel. Other scripts are run as necessary to test bug fixes that cannot easily be unit-tested. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
