On Wed, Jun 4, 2008 at 10:27 AM, Shawn O. Pearce <spearce@xxxxxxxxxxx> wrote: > Imran M Yousuf <imyousuf@xxxxxxxxx> wrote: >> The first version I mavenized JGit I moved the source code, but I >>... >> welcomed or not. > > [please don't top-post on this list] Sorry, but I thought that I was proposing something new and thus top-posted :) > > I'd rather us moving the code into a subdirectory than require > a symlink. For Eclipse this is easy to change the directory that > the code is in, we just have to edit the .classpath to move the > source folder lower in the tree. > > But this shows one reason why I don't use Maven I think. The > fact that we need a "java" directory to hold our java code. > What if another build system wants a different name? Grumble. I am sorry for my ignorance, I thought that maven was the most widely accepted java build tool, but what you said is a possibility. > > For the most part git-merge-recursive can handle a merge through > this sort of rename. But we'd like to do this sort of thing at > some relatively stable point in time to try and minimize the impact > it has. When I was working with the moved source code git detected the renames and propagated the changes, but I had to scrape it because of my stupidity my mavenized jgit was in jgit folder that clashed with the jgit shell script :). I would say once the move is done it would be safe to continue. > > -- > Shawn. > -- Imran M Yousuf Entrepreneur & Software Engineer Smart IT Engineering Dhaka, Bangladesh Email: imran@xxxxxxxxxxxxxxxxxxxxxx Blog: http://imyousuf-tech.blogs.smartitengineering.com/ Mobile: +880-1711402557 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
