mattcasters opened a new pull request, #9090:
URL: https://github.com/apache/hop/pull/9090

   A new Hop configuration now gets a `local` pipeline run configuration and a 
`local` workflow run configuration.
   
   `hop setup` copies the install default-project template into the new default 
project. That copy only took the top level, so `project-config.json` arrived 
and `metadata/` was created empty. The standard `local` run configurations live 
under `metadata/` and were left behind. The copy now includes nested metadata. 
When the template does not already contain those configurations, setup writes 
them, together with the local execution info location and data profile they 
use. An existing default project that already has `project-config.json` is left 
unchanged.
   
   fixes #9089
   
   ------------------------
   
   Thank you for your contribution! Follow this checklist to help us 
incorporate your contribution quickly and easily:
   - [ ] Run `mvn clean install apache-rat:check` to make sure basic checks 
pass. A more thorough check will be performed on your pull request 
automatically.
   - [x] If you have a group of commits related to the same change, please 
squash your commits into one and force push your branch using `git rebase -i`.
   - [x] Mention the appropriate issue in your description (for example: 
`addresses #123`), if applicable.
   
   To make clear that you license your contribution under the [Apache License 
Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
   you have to acknowledge this by using the following check-box.
   
   - [x] I hereby declare this contribution to be licensed under the [Apache 
License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
   - [ ] In any other case, please file an [Apache Individual Contributor 
License Agreement](https://www.apache.org/licenses/icla.pdf).
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to