You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "John Interrante (Jira)" <ji...@apache.org> on 2020/10/07 13:09:00 UTC
[jira] [Created] (DAFFODIL-2406) Rename subprojects for better
clarity
John Interrante created DAFFODIL-2406:
-----------------------------------------
Summary: Rename subprojects for better clarity
Key: DAFFODIL-2406
URL: https://issues.apache.org/jira/browse/DAFFODIL-2406
Project: Daffodil
Issue Type: Improvement
Components: Clean Ups
Affects Versions: 3.0.0
Reporter: John Interrante
There has been some discussion on the dev list about renaming some Daffodil subprojects to make their contents more obvious to newcomers. The following list of new subproject names has received some consensus support, although the renaming should be performed in two phases (two separate commits) as the second phase would require more work than simply changing filenames:
*Phase 1*
* containers
* daf-backend-c-generator (ignore - not in main yet, but will be later)
* daf-backend-scala-parser (to be merged into daf-backend-scala later)
* daf-backend-scala -unparser (to be merged into daf-backend-scala later)
* 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)