Use SNAPSHOTs. Then occasionally deploy a VERSION of your project/code and then go back to working from SNAPSHOTs.
It sounds like every one of your developers has their own pom.xml -- this makes zero sense. The correct approach is one shared pom.xml per project/module. Wayne On 2/12/07, Rahamim, Zvi (Zvi) <[EMAIL PROTECTED]> wrote:
Hi, We are a group of developers that work on a project. I would like that whenever I add/remove a dependency for that project, the other developers could see it with the minimal effort. I thought of having a parent pom.xml file in my repository, where each developer has its own pom.xml (that only points to that parent pom.xml). In this way if the parent pom.xml is updated (but its version remains the same) everybody will see that change without an effort, ...but there is a problem with overwriting the same version of the parent pom.xml file (because in case I created version 1.0.0 of my project that use a specific version of parent pom.xml file and now I change the parent pom.xml file to have a different information...) Do you have a solution? Thanks! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
