The compiler currently has hard-coded paths for JAR and data asset outputs. To improve this, output paths should be configurable via package.json, allowing profiles to direct outputs to custom folders or remote locations like S3. This would support workflows where assets need to be automatically uploaded or stored in specific directories based on the environment.
The compiler currently has hard-coded paths for JAR and data asset outputs. To improve this, output paths should be configurable via package.json, allowing profiles to direct outputs to custom folders or remote locations like S3. This would support workflows where assets need to be automatically uploaded or stored in specific directories based on the environment.