adoroszlai commented on pull request #2998: URL: https://github.com/apache/ozone/pull/2998#issuecomment-1016665667
> Suppose genesis is a useful tool. We probably need to move the genesis code to a different maven module or even a different repo. By default, genesis won't be included with Ozone release. It will be available somewhere. Then, we may download it on demand. This is similar to the jmh-core jar in the ozone script. I think we should move Genesis to a separate repo with different license. (I'm not sure if Apache allows such license, nor about the mechanics of a license change.) Separate project is also recommended by JMH, too: "The recommended way to run a JMH benchmark is to use Maven to setup a standalone project that depends on the jar files of your application." > The current genesis doc and scripts may be still useful. So, how about we fix them separately? `ozone genesis` won't work because `Genesis.java` is being removed. I think leaving the script around would be confusing. I'm OK with fixing it separately, though. Please let me know if I should work on that part. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
