[
https://issues.apache.org/jira/browse/MUSE-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Eberbach resolved MUSE-173.
----------------------------------
Resolution: Fixed
This is working now. Just need to update the docs.
> Maintain a list of files to overwrite
> -------------------------------------
>
> Key: MUSE-173
> URL: https://issues.apache.org/jira/browse/MUSE-173
> Project: Muse
> Issue Type: Improvement
> Components: Tooling - Code Generation
> Reporter: Andrew Eberbach
> Assigned To: Andrew Eberbach
> Fix For: 2.2.0
>
>
> When regenerating into a directory, extra care must be taken to not overwrite
> work. However, the current code generation only has an all-or-nothing
> approach: overwrite everything or overwrite nothing.
> This should be changed so that when generating code, a manifest of all of the
> files that will probably never have hand-written code in them should be
> created in the project directory root. Then, when regenerating there are
> three options:
> 1. Overwrite nothing
> 2. Overwrite everything
> 3. Overwrite only the files that are listen in the manifest
> This has some nice features.
> 1. By default, using the Muse-172 feature the concrete implementation classes
> would be left out of the manifest so that only the interface and the abstract
> class would be regenerated.
> 2. If there were files that the user added to the project, they would also
> not get overwritten since they are not in the list of files.
> 3. If a user doesn't want a specific file to be regenerated they can just
> edit the manifest (it's a text file with one file per line) and take out the
> file. This should also support standard # comments.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
