Generalization of oasp_constants templates

[maybeec]

We should discuss further generalizations of the oasp_constants tempaltes as currently the project architect of an oasp project has to modify the context.xml to indicate the root package of the target application to be generated, see context.xml - line 49 & 54.

I would rather love a solution, which does not depend on further modifications by the user.

[maybeec]

We might want to exclude configurable values like the rootPackage into an external properties file to ensure save template and configuration upgrades.

[jdiazgon]

OASP has been deprecated, closing this issue.

[maybeec]

This holds also for devonfw. There is the same increment for devonfw generating the permission constants. ;)

[github-actions[bot]]

Stale topic. Please negotiate closing or discussing the relevance of this ticket.