repository

What I want to do now is to initialize a private repository on my production server in to app's www folder (ex: /var/www/app.com/web/) and then clone it as a staging repository to my testing site (ex: /var/www/test.com/web/app.com/) and finaly clone from staging to local to work with the code. Am I planning it the right way? I am following these tutorials to learn more about setting the "git server" and initialize private repositories: http://progit.org/book/ch4-4.html https://moocode.com/posts/6-code-your-own-multi-user-private-git-server-in-5-minutes http://www.layeredthoughts.com/git

I want to upload my artifacts to a remote Nexus repo. Therefore I have configured a snaphot and a release repo in Nexus. Deployment to both works. Now I want to configure my build so I can decide in which repo I want to deploy: gradle uploadArchives should deploy to my snapshots repo gradle release uploadArchives should deploy to my release repo This was my try: apply plugin: 'war' apply plugin: 'maven' group = 'testgroup' version = '2.0.0' def release = false repositories { mavenCentral() mavenLocal() } dependencies{ providedCompile 'javax:javaee-api:6.0' } task release <<{ release = true;

In general, I know that there are 3 big types of design pattern Creational Pattern (Factory, Singleton, etc) Structural Pattern (Composite, Adapter, Proxy, etc) Behavioral Pattern (Specification, Command, etc) But I dont know which type I can put the Repository pattern in. Is Repository pattern in one of three above type? Or is it kind of in the middle of (2) and (3) pattern? Repository can be viewed as a special kind of Façade (structural) but also as a special kind of Factory (creational). Also, as the Repository often expose collection-like interface, then it might be a special application

I have a many-to-many assocition between an Employee and a Team. Foreach entity I have a repository. Now I use ASP.NET MVC and I created a EmployeeController. I also created a View to edit an Employee. For this view I need a DropDownList with all Teams. The problem is that my EmployeeController only has got EmployeeRepository. So how can I get all Teams? My solution now is to use two repositories. But is this a good solution? Could I instead create TeamController and write a method returning all Teams (how would I do that)? Yes, it's perfectly acceptable for a controller to have references to

I'm trying to use Simple Injector to create my repository and use it in the Business logic layer ( also i want to use PerWebRequest method ) . In the DAL layer i have : public interface IRepository<T> where T : class { void Add(T entity); void Delete(T entity); void Delete(int id); void Update(T entity); T GetById(int Id); IQueryable<T> All(); IEnumerable<T> Find(Func<T, bool> predicate); } and : public class EFRepository<T> : IRepository<T>, IDisposable where T : class { #region Members protected DbContext Context { get; set; } protected DbSet<T> DbSet { get; set; } #endregion #region