You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@daffodil.apache.org by GitBox <gi...@apache.org> on 2018/12/10 16:06:40 UTC

[GitHub] stevedlawrence commented on issue #145: Bump SBT version to 1.2.7

stevedlawrence commented on issue #145: Bump SBT version to 1.2.7
URL: https://github.com/apache/incubator-daffodil/pull/145#issuecomment-445870131
 
 
   Do you mean how all the different DFDL schemas also need to include an sbt and scala version number? I don't think there is a great way around that. The sbt version number definiately can't be centralized, since the build.properties file has a very simple format and is parsed very earily in the sbt startup process.
   
   The scala version can be a little more dynamic, but I don't think there is a way to query the scala version that Daffodil uses. The best we could probably do is create an SBT plugin that the DFDL Schema projects use, and that plugin could be manually updated to match the Daffodil version. Then it just becomes a matter of updating that plugin. But that's kindof odd behavior for a plugin. It doesn't really do anything, just sets a bunch of default parameters. And it still requires people to update the plugin version to get the new settings. So still a somewhat manual process.
   
   I'm not sure there's a great solution to that problem. When probably just need to remember to update scala and sbt versions when we update the daffodil dependency.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services