Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Forward ported the mapper from 2.0 release (as deprecated) #6

Closed
wants to merge 2 commits into from

Conversation

aborg0
Copy link

@aborg0 aborg0 commented Oct 22, 2014

From https://github.com/netplex/json-smart-v2/tree/f5260dc716e14a89d9a9549722558b74fa70fc25
deprecated the classes. (Hopefully that was the released version of
this project.)

https://github.com/netplex/json-smart-v2/tree/f5260dc716e14a89d9a9549722558b74fa70fc25
and deprecated the classes. (Hopefully that was the released version of
this project.)
@aborg0 aborg0 changed the title Backported the mapper form Backported the mapper from 2.0 release Oct 23, 2014
@aborg0 aborg0 changed the title Backported the mapper from 2.0 release Forward ported the mapper from 2.0 release (as deprecated) Oct 27, 2014
The new packages were not exported through OSGi.
@UrielCh
Copy link
Contributor

UrielCh commented Nov 5, 2014

can you help me to fill the json-smart-backport package ?

witch project use net.minidev.json-mapper package ?

@aborg0
Copy link
Author

aborg0 commented Nov 5, 2014

It seems from the maven central only the json-path project uses it. (The other https://github.com/btrplace/scheduler/tree/master/json/src seems to be using only the json parser.)
I have no idea how to get information about usage besides Maven central. (We plan to use it within KNIME (which is not on maven central), but because of these problems we will most probably use our snapshot of 2.0 with the 1.1.0 of json-path unless both projects release a new version fixing all OSGi related problems or we have a workaround for them.)
The currently unreleased version of json-path using the released 2.1 version of json-smart (so it seems to made the change and not using the deleted package anymore), which is currently not usable using OSGi because of the missed exported package (the writer). Json-path's currently released version (1.1.0) is supposed to be usable with the released 2.1 version of json-smart (assuming semantic versioning), but it is not because of the deleted package.
Thanks for the support.

May I ask what is the problem with just deprecating the old packages? I think the commit aborg0@366df66 contains all classes that were removed, but previously were exported.

@UrielCh UrielCh changed the base branch from master to v2.3 September 24, 2016 16:46
@UrielCh UrielCh changed the base branch from v2.3 to v2.2.2 March 25, 2017 16:33
@UrielCh UrielCh closed this Mar 25, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants