[LANG-101] Multi-module reactors Created: 02/Jul/20 Updated: 02/Oct/20 Resolved: 02/Oct/20 |
|
| Status: | Closed |
| Project: | Language Bundles |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Maxime Michel | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Epic Link: | M6 translations |
| Description |
|
The approach currently being implemented is likely to produce problems when running on multi-module projects such as UI. Those problems need to be identified and solved. A solution that showed up in discussions is to treat every submodule as a standalone project, using the following Maven command: mvn exec:exec -Dexec.executable="pwd" #-Dexec.workingdir="/tmp" -Dexec.args="-X myproject:dist" |
| Comments |
| Comment by Maxime Michel [ 02/Oct/20 ] |
|
This was solved by the way we're using the CLI. Lokalise will keep track of the full paths of the files. Inside the tool, we can then create tasks to target files by looking for the name of the submodule inside their file names. |