[magnolia-dev] [JIRA] (MGNLCE-31) Tests: Maven profiles other than jetty9-standalone do not work anymore

[JIRA (on behalf of Philip Mundt)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philip Mundt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Community Edition /  MGNLCE-31 
 
 
 
  Tests: Maven profiles other than jetty9-standalone do not work anymore  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 
 
 
 
 
 
 
 Manual (and UI) test profiles are currently only executable with profile {{jetty9-standalone}}.We should try to make those profiles acutally usable again.EE build should have the same issues.h5. How to reproduceRun the following command in {{magnolia-integration-tests/tests}}:{code}mvn clean install - Ptomcat7x Ptomcat70 ,manual-tests{code}Will result in a build failure:{code}[WARNING] The requested profile "tomcat7x" could not be activated because it does not exist.[ERROR] Failed to execute goal org.codehaus.cargo:cargo-maven2-plugin:1.4.13:run (run) on project magnolia-integration-tests: Unable to parse configuration of mojo org.codehaus.cargo:cargo-maven2-plugin:1.4.13:run for parameter type: Cannot create instance of class org.codehaus.cargo.container.configuration.ConfigurationType -> [Help 1]{code}Similarly, the following command{code}mvn clean install -Pjetty6-standalone,manual-tests{code}will also result in a build failure:{code}[ERROR] Failed to execute goal org.codehaus.cargo:cargo-maven2-plugin:1.4.13:run (run) on project magnolia-integration-tests: Failed resolving artifact: Failure to find org.mortbay.jetty:jetty:zip:6.1.22 in https://nexus.magnolia-cms.com/content/groups/staff was cached in the local repository, resolution will not be reattempted until the update interval of magnolia.nexus has elapsed or updates are forced{code}h5. IssuesOne particular issue is that the {{cargo-maven2-plugin}} configuration is bound to a jetty runtime only. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 

[magnolia-dev] [JIRA] (MGNLCE-31) Tests: Maven profiles other than jetty9-standalone do not work anymore

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Community Edition /  MGNLCE-31 
 
 
 
  Tests: Maven profiles other than jetty9-standalone do not work anymore  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Priority:
 
 Neutral Major 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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] (MGNLCE-31) Tests: Maven profiles other than jetty9-standalone do not work anymore

[JIRA (on behalf of Philip Mundt)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philip Mundt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Community Edition /  MGNLCE-31 
 
 
 
  Tests: Maven profiles other than jetty9-standalone do not work anymore  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 
 
 
 
 
 
 
 Manual (and UI) test profiles are currently only executable with profile {{jetty9-standalone}}.We should try to make those profiles acutally usable again.EE build should have the same issues.h5. How to reproduceRun the following command in {{magnolia-integration-tests/tests}}:{code}mvn clean install -Ptomcat7x,manual-tests{code}Will result in a build failure:{code}[WARNING] The requested profile "tomcat7x" could not be activated because it does not exist.[ERROR] Failed to execute goal org.codehaus.cargo:cargo-maven2-plugin:1.4.13:run (run) on project magnolia-integration-tests: Unable to parse configuration of mojo org.codehaus.cargo:cargo-maven2-plugin:1.4.13:run for parameter type: Cannot create instance of class org.codehaus.cargo.container.configuration.ConfigurationType -> [Help 1]{code}Similarly, the following command{code}mvn clean install -Pjetty6-standalone,manual-tests{code}will also result in a build failure:{code}[ERROR] Failed to execute goal org.codehaus.cargo:cargo-maven2-plugin:1.4.13:run (run) on project magnolia-integration-tests: Failed resolving artifact: Failure to find org.mortbay.jetty:jetty:zip:6.1.22 in https://nexus.magnolia-cms.com/content/groups/staff was cached in the local repository, resolution will not be reattempted until the update interval of magnolia.nexus has elapsed or updates are forced{code} h5. IssuesOne particular issue is that the {{cargo-maven2-plugin}} configuration is bound to a jetty runtime only. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
   

[magnolia-dev] [JIRA] (MGNLCE-31) Tests: Maven profiles other than jetty9-standalone do not work anymore

[JIRA (on behalf of Philip Mundt)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philip Mundt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Community Edition /  MGNLCE-31 
 
 
 
  Tests: Maven profiles other than jetty9-standalone do not work anymore  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 

Summary:
 
 Tests: Maven profiles other than jetty9-standalone do not work anymore 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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: