stevedlawrence commented on PR #919: URL: https://github.com/apache/daffodil/pull/919#issuecomment-1403734818
> I'm not sure what the best way is to incorporate this into the sbt build chain or in the CI if we wish to do that. One approach would be to create a new sbt task (e.g. sbt osgiCheck) and move the split package logic into the body of that task. I believe you could define the task an all logic in something like `project/OsgiCheck.scala` so it shouldn't require to much of a change. Another benefit of this approach is you can use other sbt tasks like `sources.value` to get a list of all scala and java source files--things like that might simplify the script a bit. Another option, there might even be an existing sbt plugin that already does a similar check, seems like it would be useful to a number of projects to make sure they are OSGI compliant. -- 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]
