This usually means that part of the functionality has been replaced by another implementation, the use of which is preferable to the old one, and such a question simply means that OP is too lazy for Google documents. This is especially true in the case of Java libraries, which take backward compatibility very seriously (to the point where it becomes a pain for some). In this regard, the Scala ecosystem is not so strict, and updating to a newer version of the language means that you can get a different API or even binary incompatibilities . See Also Scala: binary incompatibility between releases . This is not a comment on Scala. There are good reasons why these incompatibilities exist.
However, I must admit that the documentation for scala.util.parsing.json does not contain any information about the recommended replacement for this function at all. It took me quite a while to dig out something that hardly seems like a clear description of what is recommended for replacement.
There seemed to be a lot of discussion in the community about the nature and consequences of this condemnation. I recommend reading this thread in the scala -users group if you're interested.
The most cited reasons for this deviation appear to be due to poor performance and thread safety.
The failure was executed as part of this Jira problem , and the use of different parsers is recommended in the comment to close this related task, which was not completed due to obsolescence .
Alternatives include:
To answer your question. This is a warning, your code should not break until this object is deleted. However, if new errors are detected in this function, most likely they will not be fixed. Your code may also be broken if you upgrade to a new version of Scala that has actually removed these packages (version 2.11.0 and higher, according to the documentation )