repository

I have been using Bzr for version control of my project over the last few months. I am the sole developer, and currently I just have everything in a single local project directory, to which I commit and which I sync to DriveHQ. I now have some large-scale experiments in mind which would likely break this main line, so I've been looking into the concepts of branches and shared repositories. So my question is, basically: how should I go about creating a new, shared repository from this already-version-controlled base? I am familiar with the SVN project structure of trunk, branches and tags, and

I am in the process is designing a website in ASP.NET MVC and am perhaps a little confused as to the exact nature of a repository. Following the NerdDinner example, my site should have one repository which serves up the entities as I need them. However, I have also heard that you should have different repositorys that deal with specific sets of related entities....? In the case of my site, there will be a number of entities (around 15 tables) yet the majority are all related. Is it ok / advisable to have one repository that contains all the methods that I'll need for pulling / updating /

I'm trying to save entity in repository but it does not work at all. Repository is Autowired and in runtime I use saveAndFlush to save entity. I'm using PostgreSQL. Above test methods I added comments with explanation what is going on. I expected that method saveAndFlush should work but it did not. I can not find why. @Transactional public class TestClass{ @Autowired private MyRepository repository; @Autowired private EntityManager entityManager; // Working version public void writingToRepositoryWorking() { entityManager.getTransaction().begin(); entityManager.persist(new MyData(99));

In the repo browser when I enter the svn root ( http://servername/svn ) directory I get this message "Repository moved permanently to 'http//....' please relocate There are several projects in this repository and I can access/checkout/update each project but I can't even access the root. How can I fix this? I'm assuming that you're not the server admin and that you're relatively new to svn... You'll need to tell your working copies that the remote repo has moved (see the svn book for info on how to do this ). You'll also need to use the new root for your remote repo browsing. I got the same

I am trying to extract a folder (call it Project1 ) from an existing Mercurial Repo (call in MainRepo ) using the Convert extension for Mercurial to Mercurial conversion. I have followed the methods described by Mercurial developers (and elsewhere on the web) under Windows XP: C:\MainRepo>echo include Project1 > ~myfilemap C:\MainRepo>echo rename Project1 . >> ~myfilemap C:\MainRepo>hg convert --filemap ~myfilemap . C:\Project1Repo C:\MainRepo>cd \Project1Repo C:\Project1Repo>hg update This creates the new repo (Project1Repo) with the Mercurial folder/files in place. But it does not: 1) Carry

I have a directory structure like so: composer.json < Main packages/ balunker/ testpackage/ composer.json < Package src/ TestPackage.php The main composer.json looks like this: { "name": "vagrant/composer-test", "repositories": [ { "type": "path", "url": "packages/*/*" } ], "require": { "balunker/testpackage": "*" } } While the package composer.json looks like so: { "name": "balunker/testpackage", "autoload": { "psr-4": { "Balunker\\": "src/" } } } On composer update I simple get a message that the package could not be resolved. No symlinks are created and no package is installed. I have