[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[jgit-dev] API Communication around "Replace deprecated Tag, Commit usage with RevTag, RevCommit"
|
On commit aa1733a1b61ee86340206b02f5c090eacb8c4a0b (in EGit land)...
"Replace deprecated Tag, Commit usage with RevTag, RevCommit
JGit is changing its API to no longer make Tag and Commit classes
accessible for reading purposes. The only thing they will support
is the creation of new objects, and even then their APIs are moving
to a simpler and more consistent usage style.
Replace relevant uses of tags and commits with their RevWalk based
variants, fixing any build breakages caused by this JGit change."
So are you saying that clients aren't suppose to reference Tags at
all? Regardless what, our documentation (javadoc included) should be
updated properly. Just looking for some clarification around API
intentions. I would probably also suggest we use PDE API Tools to
annotate some of our classes with information like (@noreference,
@noinstantiate etc...) to help us as we develop.
--
Cheers,
Chris Aniszczyk
http://aniszczyk.org
+1 860 839 2465
