[magnolia-dev] [JIRA] (NPMCLI-100) Existing magnolia.zip lets jumpstart ignore -m and -e option

2017-04-11 Thread JIRA (on behalf of Robert Kowalski) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Robert Kowalski updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-100  
 
 
  Existing magnolia.zip lets jumpstart ignore -m and -e option   
 

  
 
 
 
 

 
Change By: 
 Robert Kowalski  
 
 
Assignee: 
 Robert Kowalski  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (NPMCLI-100) Existing magnolia.zip lets jumpstart ignore -m and -e option

2017-03-06 Thread JIRA (on behalf of Robert Kowalski) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Robert Kowalski updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-100  
 
 
  Existing magnolia.zip lets jumpstart ignore -m and -e option   
 

  
 
 
 
 

 
Change By: 
 Robert Kowalski  
 
 
Assignee: 
 Robert Kowalski  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (NPMCLI-100) Existing magnolia.zip lets jumpstart ignore -m and -e option

2017-02-24 Thread JIRA (on behalf of Christopher Zimmermann) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-100  
 
 
  Existing magnolia.zip lets jumpstart ignore -m and -e option   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 
 
Labels: 
 to-specify  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (NPMCLI-100) Existing magnolia.zip lets jumpstart ignore -m and -e option

2017-02-20 Thread JIRA (on behalf of Christoph Meier) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Meier updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-100  
 
 
  Existing magnolia.zip lets jumpstart ignore -m and -e option   
 

  
 
 
 
 

 
Change By: 
 Christoph Meier  
 
 
Affects Version/s: 
 1.0.7  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (NPMCLI-100) Existing magnolia.zip lets jumpstart ignore -m and -e option

2017-02-10 Thread JIRA (on behalf of Christoph Meier) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Meier created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-100  
 
 
  Existing magnolia.zip lets jumpstart ignore -m and -e option   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 2.0.0-snapshot-167  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 10/Feb/17 10:51 AM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Christoph Meier  
 

  
 
 
 
 

 
 When running the jumpstart command,and if there is already magnolia.zip - no bundle artifact downloaded. Fair enough. However, in consequence neither the -e nor -m option have any influence.  It just takes the version which was chosen the last time when it had to download. The "easiest" fix seems to be to delete the zip file after successful installation.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment