[MAGNOLIA-2526] Update json dependencies ? Created: 23/Dec/08  Updated: 20/Feb/15  Resolved: 04/Nov/10

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

Type: Task Priority: Major
Reporter: Magnolia International Assignee: Ondrej Chytil
Resolution: Fixed Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLIMG-74 Update json dependency Closed
is related to MGNLPUR-47 Update json dependency Closed
is related to MGNLDATA-111 Update json dependency Closed
is related to MAGNOLIA-2769 Misplaced json dependencies Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

We have a couple of dependencies to json, in the main project and in modules (dms, data, ...) - maybe its time for an update - along with refreshing the exclusions that go with the current version.



 Comments   
Comment by Will Scheidegger [ 09/Apr/10 ]

I've replaced json-lib 0.9 with json-lib 2.3 (jdk15) and have not yet encountered any misbehavior... still testing though.

Comment by Kimmo Björnsson [ 11/Oct/10 ]

Noticed my application broke because of json-lib 0.9 dependency, where I noticed it was in magnolia-module-store-client, I could have excluded it in my pom.xml on that dependency, but I choosed to remove magnolia-module-store-client. Please upgrade to json-lib 2.3

Comment by Tobias Mattsson [ 27/Oct/10 ]

json-lib 0.9 is also used in magnolia-module-public-user-registration, should be updated there aswell

Comment by Magnolia International [ 27/Oct/10 ]

One of the concerns I had with this issue is that m-m-data and m-m-dms use net.sf:json-lib and com.metaparadigm:json-rpc respectively.

Turns out that, unless i haven't looked deeply enough (this is a call for a double-checking), neither of these dependencies are actually used and thus could be removed.

However, to avoid issues with other modules or third parties, I'd still be in favor of only update the dependency in 4.4+

ps: imaging also has a dependency on this; currently unused (for the still-to-be-revived crop control)

Comment by Philipp Bärfuss [ 28/Oct/10 ]

The changes were revered on the 4.3 branch.

Comment by Tobias Mattsson [ 30/Nov/10 ]

The version should not be respecified in store-client/pom.xml it should only be specified in dependencyManagement in the parent.

Generated at Mon Feb 12 03:37:34 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.