Feature #7180
create a centralized manager for the conversion list and per-file/project status and logging
0%
Related issues
History
#1 Updated by Greg Shah about 1 year ago
- Related to Feature #7169: drive conversion order using user-specified dependencies added
#2 Updated by Greg Shah about 1 year ago
- Related to Feature #7179: rework the conversion process to ensure that it can finish an entire run even when there are failures after parsing added
#3 Updated by Greg Shah about 1 year ago
We will externalize the conversion list and use it to drive both the front end and the TRPL processing. It will be available via an API. That API will also include the ability to report status back and log various details. All of that will be associated with the specific file and can be viewed/rendered by reading the data from the API. This will facilitate a range of the features we need to build, including things like IDE support and dependency management. We won't do logging or any output to the console directly.
One feature that is needed is to be able to dynamically add or remove files from the conversion list. #7179 will need to remove files when failures occur. The dependency management in #7169 will need the ability to add and remove files.
#4 Updated by Greg Shah about 1 year ago
- Related to Bug #5703: rationalize, standardize and simplify the client-side log file name configuration added
#5 Updated by Galya B about 1 year ago
Interface is p2j.convert.ConversionStatus
. Applicable for packages (refs #5703#note-133):
src/com/goldencode/p2j/convert/ src/com/goldencode/p2j/e4gl/ src/com/goldencode/p2j/pattern/ src/com/goldencode/p2j/preproc/ src/com/goldencode/p2j/report/ src/com/goldencode/p2j/uast/ src/com/goldencode/p2j/schema/