stevedlawrence commented on code in PR #7: URL: https://github.com/apache/daffodil-schema.g8/pull/7#discussion_r1579841641
########## src/main/g8/default.properties: ########## @@ -16,5 +16,5 @@ name=format extension=dat package=com.example -namespaced=no -daffodil_version=maven(org.apache.daffodil, daffodil-tdml-processor_2.12) +namespaced=yes +daffodil_plugin_version=maven(org.apache.daffodil, sbt-daffodil) Review Comment: Note that this now initializes "sbt new" projects with the latest version of the sbt-daffodil plugin available in maven (e.g. 1.0.0 once it's released) instead of the latest version of daffodil TDML processor available in maven. This way the new project will use whatever Daffodil version that plugin defaults to (current 3.7.0). We could additionally get the latest version of daffodil and add something like `daffodilVersion := $daffodil_version$` to the build.sbt template, which would pin the project to that specific daffodil version. But I kind of like the idea that updating to the latest version of the plugin automatically gets you the latest version of Daffodil. And only if your project really depends on a specific version should you pin it by manually setting `daffodilVersion` in build.sbt. Thoughts? -- 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: dev-unsubscr...@daffodil.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
