mike-mcgann commented on PR #919: URL: https://github.com/apache/daffodil/pull/919#issuecomment-1402045003
> Is there a way for a scala script to insist on a particular scala version, and error out if not the right one? If the refactor goes well these scripts can be thrown out so I'm not sure if this is the place to address the issue. I think the larger problem is that all of us ran this in different environments and got different results. Ubuntu installed 2.11 for you and Fedora 37 installed 2.13 for me. There is [pyenv](https://github.com/pyenv/pyenv) for Python which can help manage environments and there are similar tools for Node.js, Ruby, and even Terraform. I see there is a [scalaenv](https://github.com/scalaenv/scalaenv) which may be helpful for this but I'm new to the Scala world and don't know if this is a good package. We could even create a docker image for development that has exactly everything that is needed. > I think we should start planning for when to merge this. We need to give people a chance to settle any large changes that modify numerous files. (I have one sort of like that in flight that I want to think about. ) Outstanding issues: - Finalize package names for daffodil-runtime1-layers and daffodil-runtime1-unparser. We need to come up with a decision on this. - ratCheck needs to pass cleanly. I could use some help with those files getting flagged as binaries - lint-split-packages needs polish. This is the script that will traverse the source and look for these issues in the future. I'll work on this next. - Now is a good time to bundle in any other adminstative tasks like this. There was some talk of incorporating an auto-formatter for the source code. Since that would probably change most source files now would be a great time to do this -- 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]
