2
I Use This!
Activity Not Available

Commits : Listings

Analyzed over 1 year ago. based on code collected over 4 years ago.
Jul 19, 2020 — Jul 19, 2021
Commit Message Contributor Files Modified Lines Added Lines Removed Code Location Date
make index dabase visible so the index state can be queried
groldan
as Gabriel Roldan
More... about 14 years ago
use a property for bxml version
groldan
as Gabriel Roldan
More... about 14 years ago
enable packaging of test-jar
groldan
as Gabriel Roldan
More... about 14 years ago
let client code check whether ggit is using the default CommitStateResolver before overriding it
groldan
as Gabriel Roldan
More... about 14 years ago
overload getRootTreeChild method
groldan
as Gabriel Roldan
More... about 14 years ago
Changed AuthenticationResolver by CommitStateResolver
groldan
as Gabriel Roldan
More... about 14 years ago
auth resolver
groldan
as Gabriel Roldan
More... about 14 years ago
temporarily allow no-crs bounds
groldan
as Gabriel Roldan
More... about 14 years ago
ObjectId.valueOf(String)
groldan
as Gabriel Roldan
More... about 14 years ago
make WorkingTree.insert use call the iterator version of Index.inserted, otherwise it's too resource consuming for large datasets
groldan
as Gabriel Roldan
More... about 14 years ago
move objects from the index databse to the repository one at Index.writeTree, not just copy them
groldan
as Gabriel Roldan
More... about 14 years ago
Re-Implemented Index using an object database as storage for the staged and unstaged changes instead of an in-memory data structure. > This allows for really large operations not to eat up too much heap, and also works better and allows for easier implementation of operations that need to manipulate the index. > The index now operates against its own database, which is a composite of its own ObjectDatabase and the repository's. Object look ups against the index first search > on the index db, and if not found defer to the repository object db. The index holds references to two trees of its own, one for the staged changes and one for the unstaged ones. > Modifications to the working tree shall update the Index unstaged changes tree. Staging changes adds missing references to the staged tree. What changes are unstaged is a matter of diff'ing the staged and unstaged trees. What changes are staged is a matter of diff'ing the (or a) reposiroty root tree and the staged changes tree.
groldan
as Gabriel Roldan
More... about 14 years ago
allow to initialize an empty subtree, as it signals the presence of a feature type, even if it's empty. Beware it needs testing though, specially cause the Index is setting the ref as a BLOB instead of a TREE
groldan
as Gabriel Roldan
More... about 14 years ago
minimized transitive dependencies
groldan
as Gabriel Roldan
More... about 14 years ago
made RevTree immutable and created MutableTree subinterface
groldan
as Gabriel Roldan
More... about 14 years ago
add attach source config to maven source plugin
groldan
as Gabriel Roldan
More... about 14 years ago
initial import
groldan
as Gabriel Roldan
More... about 14 years ago