Technically, clone() does not fit his needs.
String phrase1 = new String();String phrase2 = phrase1;String word = "Word";phrase1 = word.clone();
AFAIK, using a copy constructor, both phrase1 and phrase2 should be equal to "Word", which is not the case using clone().
Personally, I stay as far away from clone as possible. The design is somewhat... strange (the empty Cloneable interface, and a protected clone() method in Object, which a class implementing Cloneable must then declare public). Bloch advises "you are probably better off providing an alternative means of object copying", which I can only agree with.
To answer to Mr. ProgDes's question: to my knowledge, there is no such "syntactic sugar" present in Java, you'll have to define a separate method.