tankilo commented on issue #2045: Mave moudle has wrong compile order, sharding-sql-test should be compiled before sharding-core URL: https://github.com/apache/incubator-shardingsphere/issues/2045#issuecomment-473659647 > Can you explain the reason for close this issue? In fact, yesterday night, i did ran into error when i try to compile the code. But this morning, after i post this issue , i can't reproduce this problem again (clean related jars in local maven repo and compile). Though `sharding-sql-test` is the last one in the `<modules>` element of the parent pom.xml, it's still compiled before some modules of `sharding-core`. ``` [INFO] Reactor Build Order: [INFO] [INFO] sharding-sphere [INFO] sharding-core [INFO] sharding-core-api [INFO] sharding-core-common [INFO] sharding-core-parse [INFO] sharding-core-parse-spi [INFO] sharding-sql-test [INFO] sharding-core-parse-common [INFO] sharding-core-parse-mysql [INFO] sharding-core-parse-postgresql [INFO] sharding-core-parse-oracle [INFO] sharding-core-parse-sqlserver ``` Before, i think module building order is just the same as what we define in <modules> element of the parent pom.xml. And after Googling, maven is smarter than I thought. https://stackoverflow.com/questions/18629897/maven-build-order-multiple-modules http://maven.apache.org/guides/mini/guide-multiple-modules.html > Reactor Sorting >Because modules within a multi-module build can depend on each other, it is important that the reactor sorts all the projects in a way that guarantees any project is built before it is required. > > The following relationships are honoured when sorting projects: > > a project dependency on another module in the build a plugin declaration where the plugin is another module in the build a plugin dependency on another module in the build a build extension declaration on another module in the build the order declared in the <modules> element (if no other rule applies)
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
