You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the relocate feature documented here: https://github.com/devonfw/tools-cobigen/wiki/cobigen-core_configuration#template-properties I would like to relocate generation into a different maven submodule. I also have parents imported in my workspace. In the preview, I would like to see the relocated preview in the most specific maven project (i.e. in the child project, not in the parent)
Actual behavior
The relocated target is shown in the most unspecific parent project imported in the workspace
Steps to reproduce (bug) / Use Case of feature request (enhancement)
create a multi-module maven project with at least one parent
import all (including parent) projects into workspace
relocate generation from one child module to another and select an input from one of the children
see the preview to show the file to be generated in the parent project
Related/Dependent Issues
Implementation Hints
Currently, the workspace project is searched by checking the whole destination path of a template from the drive letter on, stopping at the path, which is included as a project in the workspace. This should be done the other way around, starting at the longest file path.
The text was updated successfully, but these errors were encountered:
Expected behavior
Using the relocate feature documented here: https://github.com/devonfw/tools-cobigen/wiki/cobigen-core_configuration#template-properties I would like to relocate generation into a different maven submodule. I also have parents imported in my workspace. In the preview, I would like to see the relocated preview in the most specific maven project (i.e. in the child project, not in the parent)
Actual behavior
The relocated target is shown in the most unspecific parent project imported in the workspace
Steps to reproduce (bug) / Use Case of feature request (enhancement)
Related/Dependent Issues
Implementation Hints
Currently, the workspace project is searched by checking the whole destination path of a template from the drive letter on, stopping at the path, which is included as a project in the workspace. This should be done the other way around, starting at the longest file path.
The text was updated successfully, but these errors were encountered: