+1 from me, with one minor suggestion I like the test-suite-XXX suggestion. Only one suggestion is changing test-suite-std to test-suite-layout. This subproject is really just about testing DFDL schema project layout and not any kind of "standard" tests.
I think Mike also suggested splitting the backends into a schema-compiler part and a lib part. So grammar specific changes are in one subproject and runtime specific things are in another. If we do decide there's value in that, it might be worth doing as part of the phase 2. As far as when to do this, we might want to wait until all the main changes are in for daffodil 3.0. This rename is probably going to make merging pull requests a bit of a pain so best to do it when we don't expect many more prs. - Steve On 10/7/20 9:08 AM, Interrante, John A (GE Research, US) wrote: > I've created an issue (https://issues.apache.org/jira/browse/DAFFODIL-2406) > to rename Daffodil subprojects for better clarity. I'd like to ask devs if > the issue has everyone's consensus and ask for a volunteer to perform the > renaming since I'm going to be refactoring classes and changing code in my > own pull request (daffodil-2202-runtime2) for at least the next few days. > > Does this proposal look acceptable to everyone? > Phase 1 > > * containers > * daf-backend-c-generator (ignore - not in main yet, but will be later) > * daf-backend-scala-parser > * daf-backend-scala -unparser > * daf-cli > * daf-io > * daf-lib > * daf-macro-lib > * daf-propgen > * daf-sapi > * daf-schema-compiler (was daffodil-core) > * daf-tdml-lib > * daf-tdml-processor > * project > * test-suite-daf > * test-suite-ibm > * test-suite-std > * tutorials > Phase 2 > Merge daf-backend-scala-parser and daf-backend-scala-unparser together into > daf-backend-scala. >
