repository

When is the implementation for repositories generated by Spring Data? At compile time or runtime? Can I see the implementation repository implementation generated by Spring Data? tl;dr No, for a very simple reason: there's no code generation going on. The implementation is based on proxies and a method interceptor delegating the call executions to the right places. Details Effectively, a method execution can be backed by 3 types of code: The store specific implementation of CrudRepository . Have a look for types named Simple(Jpa|Mongo|Neo4|…)Repository (see the JPA specific one here ). They

Quite often I'm sitting in the middle of a subversion working copy, and I want to do a quick svn status to find out what changes I have made since the last checkin. However svn status only works on the current folder and it's children. (Similarly for svn up too) I'd like a quick way to change to the root folder of the subversion working copy so I can run a svn status and see all files that have changed, maybe a checkin or a update, and then get back to work where I was before. Here's my first go at an answer: I wrote a little bash script called svnbase : #!/bin/bash -u # this command outputs

I'm one of many trying to understand the concept of aggregate roots, and I think that I've got it! However, when I started modeling this sample project, I quickly ran into a dilemma. I have the two entities ProcessType and Process . A Process cannot exist without a ProcessType , and a ProcessType has many Process es. So a process holds a reference to a type, and cannot exist without it. So should ProcessType be an aggregate root? New processes would be created by calling processType.AddProcess(new Process()) ; However, I have other entities that only holds a reference to the Process , and

I have multiple repositories in my application. Where should I put the ObjectContext? Right now, I have a reference like ObjectContext ctx; in every repository. What is the smartest and safest way to go about this? A design with multiple ObjectContext instances is only acceptable if your Repository methods commit the transaction. Otherwise, it is possible that external calls to commit the transaction may not persist everything you intend, because you will hold references to different instances of the ObjectContext . If you want to restrict the ObjectContext to a single instance, then you can

I want to extend on another question I had: Merge two Git repositories and keep the master history I have succeeded in merging 2 different repo's into one repo. I needed a rebase to do this successfully. The master is correct, but I also want to keep the merge history . Is this possible? I have 2 repositories: https://github.com/DimitriDewaele/RepoA https://github.com/DimitriDewaele/RepoB This is the result after rebasing. The times of the top repo are the rebase-time. The original date is lost! https://github.com/DimitriDewaele/RepoMerged This is how I did it: # Assume the current directory

I'd like to have a way in which 'mvn install' puts files in a repository folder under my source (checkout) root, while using 3rd party dependencies from ~/.m2/repository. So after 'mvn install', the layout is: /work/project/ repository com/example/foo-1.0.jar com/example/bar-1.0.jar foo src/main/java bar src/main/java ~/.m2/repository log4j/log4j/1.2/log4j-1.2.jar (In particular, /work/project/repository does not contain log4j) In essense, I'm looking for a way of creating a composite repository that references other repositories My intention is to be able to have multiple checkouts of the

Using Chris's answer on another question I could prepend a snapshot-history to my git repository. Since one of the files is not part of my history but only in the snapshots, the first original commit now also contains the deletion of this file. How can I undo that? At first I thought this was the opposite of How do I remove sensitive files from git’s history , but actually I don't want to insert a file into history but just remove the deletion from history. git checkout <commit> <filename> Tobias Kienzler I got it: git tag originalHead # just in case git rebase -i <id of the parent of the

As we know, we can periodically run git gc to pack objects under .git/objects . In the case of a remote central Git repository (bare or not), though, after many pushes, there many files under myproj.git/objects ; each commit seems to create a new file there. How can I pack that many files? (I mean the ones on the remote central bare repository, not on local clone repository.) The remote repo should be configured to run gc as needed after a commit is made. See the documentation of gc.auto in git-gc and git-config man pages. However, a remote repo shouldn't need all that much garbage collection,

This command works to get the files and compile them: git clone a-valid-git-url for example: git clone git://cfdem.git.sourceforge.net/gitroot/cfdem/liggghts However, git status (or any other git command) then gives the above fatal: Not a git repository (or any of the parent directories) error. What am I doing wrong? You have to actually cd into the directory first: $ git clone git://cfdem.git.sourceforge.net/gitroot/cfdem/liggghts Cloning into 'liggghts'... remote: Counting objects: 3005, done. remote: Compressing objects: 100% (2141/2141), done. remote: Total 3005 (delta 1052), reused 2714