You are right. The version controller we are using is internal to our organization. details: When a user creates a view of the code base, the files are not directly copied.Instead symlinks of the files are created in the directory structure. The symlinks point to the backend repository.When a user has to modify a file, he checks it out, and the symlink is replaced with a actual copy. However the hidden symlinked foler will still exist in each of the directories, which point to the corresponding backend directory. The issue is happening because maven is building the current directory (with symlinked files) and then entering the symlinked folder( backend repo) and building the same files again, and hence erroring out as duplicate class.
Thanks and Regards -- rajaram On Thu, Oct 6,2011 at 1:22 AM, Ansgar Konermann < ansgar.konerm...@googlemail.com> wrote: > Am 05.10.2011 20:39, schrieb rajaram shetty: > > I cant remove the symlinks. it is a part of my version controller. > What is the name of the version controller product (version control > system) you are using? > > > All the files are actually symlinks to the backend repo. and each folder > has > > a sym linked folder in the backend. > Most version control systems I know of have a concept of a "working > copy", that is, a local copy of the source code where the compiler works > with. > > Please tell us a little bit more about your version control system. It > seems it is not so common. Maybe there is no out-of-the-box support for > it in Maven yet. > > Best regards > > Ansgar > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > -- rajaram
