Bug #4372
No way of archiving artifacts
Status:
New
Priority:
Low
Assignee:
-
Target version:
-
Start date:
10/28/2019
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
reviewer:
production:
No
env_name:
topics:
History
#1 Updated by Roger Borrello over 6 years ago
If you are working on a very large project, it might be beneficial to having a way to archive the front-end artifacts. I just wanted to get feedback on whether or not a dependency such as the below, would be of any benefit. It would be a type of "un-clean".
<target name="archive" description="Archive all generated files from the conversion process." >
<delete file="${appname}_artifacts.zip"/>
<zip destfile="${appname}_artifacts.zip" basedir="${basedir}" filesonly="true"
excludes="${app.4gl.src}/skeleton/*
${app.4gl.src}/possenet/*"
includes="ui_strings.txt
orphan-frames.dat
schema-triggers.xml
internal_procedures.xml
name_map.cache
file_sys.xml
name_map.xml
function_return_types.xml
duplicate_function_return_types.xml
cfg/registry.xml
adm_windows.json
embedded/src/resources/adm_windows.json
**/*.pphints
**/*.cache
**/*.lexer
**/*.parser
**/*.ast
**/*.ast.original
**/*.jast
**/*.dict
**/*.p2o
**/*.schema
**/*.log"
/>
</target>