We could consider splitting Python up into the four things it runs: all tests with Cython, all tests without Cython, docs, and checkstyle. However, I never use Maven when developing the python portions.
On Thu, May 18, 2017 at 6:35 PM, Thomas Groh <[email protected]> wrote: > Generally I pass "-am -amd -pl sdks/java/core" to my maven invocation. -pl > is the module to build, -am indicates to also make all modules my target > depends upon, and -amd indicates to also make all of the dependencies; so > if you're only modifying java, that should hit everything. If you're making > another module, you can specify that as the -pl target, and if you > 'install' instead of 'verify' you can resume arbitrarily. > > On Thu, May 18, 2017 at 4:29 PM, Eugene Kirpichov < > [email protected]> wrote: > >> I've noticed that when I run "mvn verify", most of the time when I look at >> the screen it's running Python tests. >> >> Indeed, the Reactor Summary says: >> ... >> [INFO] Apache Beam :: SDKs :: Python ...................... SUCCESS [11:56 >> min] >> ... >> [INFO] Total time: 12:03 min (Wall Clock) >> >> i.e. it's clearly on the critical path. The longest other project is >> 02:17min (Runners::Spark). >> >> Are our .pom files customizable with an option to run only Java tests? (or, >> respectively, only Python tests) >> >> Thanks. >>
