[MAGNOLIA-5869] Upgrade thirdParty libraries Created: 05/Aug/14  Updated: 30/Jun/15  Resolved: 30/Jun/15

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major
Reporter: Daniel Lipp Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
duplicate
duplicates MAGNOLIA-6013 Upgrading versions of third-party lib... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

5.4 is a new major release so we don't have to be 100% backwards compatible. Hence this is the chance to upgrade third party libs. We should investigate for all libs, whether there's newer versions around and whether we should use them.

Few examples:

  • commons-beanutils: 1.8.3 -> 1.9.2
  • selenium: 2.41.0 -> 2.42.2
  • htmlunit: we're using 2.8 but there's 2.12
    Because of API changes this requires adapting AbstractMagnoliaHtmlUnitTest#openPage e.g. as follows:
            final WebClientOptions webClientOptions = webClient.getOptions();
    
            webClientOptions.setRedirectEnabled(followRedirects);
    
            // we also want to test error code handling:
            webClientOptions.setThrowExceptionOnFailingStatusCode(false);
    
            webClientOptions.setCssEnabled(true);
            webClientOptions.setJavaScriptEnabled(enableJsvascript);
    
    


 Comments   
Comment by Magnolia International [ 30/Jun/15 ]

Dupes MAGNOLIA-6013

Generated at Mon Feb 12 04:09:09 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.