[NPMCLI-190] jumpstart can not handle CE artifacts from the "magnolia.public.maintenance.releases" repo Created: 19/Jul/18 Updated: 03/Dec/20 |
|
| Status: | Open |
| Project: | Magnolia CLI |
| Component/s: | None |
| Affects Version/s: | 3.0.1 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Christoph Meier | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Date of First Response: |
| Description |
|
Summary:
When running this command mgnl jumpstart -m 5.4.17 CLI fails with: The artifact magnolia-community-demo-webapp-5.4.17.war resides in the repo magnolia.public.maintenance.releases. I assume: CLI asks for credentials only, if I choose an EE (or cloud) webapp. I currently can "trick" CLI if I manually download magnolia-community-demo-webapp-5.4.17.war and move it to my local __mgnl-artifacts-store, that's where my CLI stores downloaded artifacts. (See downloadsFolder, property downloadsFolder). In the case of my example, CLI should ask me as the user for credentials, if the requested artifact is available but in a non-public repository. |