[NPMCLI-45] mgnl-cli.json config.outputPath and magnolia.resources.dir should be the same and correspond Created: 11/Aug/16 Updated: 01/Sep/16 Resolved: 01/Sep/16 |
|
| Status: | Closed |
| Project: | Magnolia CLI |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Christoph Meier | Assignee: | Unassigned |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
When running the jumpstart, during execution the commands writes into magnolia.properties file(s), which is nice. When running the jumpstart command without the -p option, a light-modules folder is created in the current directory. All fine. When running the jumpstart command with, lets say the But running the mgnl build command copies the npm packages (with the keyword "magnolia-light-module") into the folder which is defined in mgnl-cli.json:config.outputPath. The observed directory - de facto defined in magnolia.properties and the outputPath should be the same! |
| Comments |
| Comment by Tomáš Gregovský [ 12/Aug/16 ] |
|
|
| Comment by Christoph Meier [ 01/Sep/16 ] |
|
This one was fixed by |