I've been running into this issue today while I wanted to set up an organizational POM.
Since we have internal and external developers working on a project I wanted to split up the developers into the organizational and project POM. The organizational POM shall include the internal developers who work on several projects. The external developers however shouldn't be part of the organizational POM since they only work on a project-basis. Therefore I included these developers in the relevant project POM.
I'm using Maven 2.0.9 and this issue still seems to be unfixed. Is there any chance it will be fixed soon?
Ruth Ziegler added a comment - 03/Jun/08 07:02 AM I've been running into this issue today while I wanted to set up an organizational POM.
Since we have internal and external developers working on a project I wanted to split up the developers into the organizational and project POM. The organizational POM shall include the internal developers who work on several projects. The external developers however shouldn't be part of the organizational POM since they only work on a project-basis. Therefore I included these developers in the relevant project POM.
I'm using Maven 2.0.9 and this issue still seems to be unfixed. Is there any chance it will be fixed soon?
Since we have internal and external developers working on a project I wanted to split up the developers into the organizational and project POM. The organizational POM shall include the internal developers who work on several projects. The external developers however shouldn't be part of the organizational POM since they only work on a project-basis. Therefore I included these developers in the relevant project POM.
I'm using Maven 2.0.9 and this issue still seems to be unfixed. Is there any chance it will be fixed soon?