Description Francisco Gortázar 2011-04-22 18:02:41 EDT

I had a project with several modules with groupId:

es.sidelab.pascaline

Modules had a POM like this one:

<parent>
  <artifactId>parent</artifactId>
  <groupId>es.sidelab.pascaline</groupId>
  <version>1.0.1-SNAPSHOT</version>
  <relativePath>../es.sidelab.pascaline.parent</relativePath>
</parent>

<groupId>es.sidelab.pascaline</groupId>	
<artifactId>net.sf.pascaline.cdtinterface</artifactId>
<packaging>eclipse-plugin</packaging>

I made a rename refactor to change the groupId to es.sidelab.pascaline.ide.

The parent project was updated perfectly, but child modules were only updated partialy. This is the POM I ended up with in my child modules:

<parent>
  <artifactId>parent</artifactId>
  <groupId>es.sidelab.pascaline.ide</groupId>
  <version>1.0.1-SNAPSHOT</version>
  <relativePath>../es.sidelab.pascaline.parent</relativePath>
</parent>
	
<groupId>es.sidelab.pascaline</groupId>	
<artifactId>net.sf.pascaline.cdtinterface</artifactId>
<packaging>eclipse-plugin</packaging>


The groupId within the parent section was updated, but the groupId outside this section remained the same. I decided not to list the groupId in child POMs, and let Maven resolve the groupId from the parent definition. However, I think the plugin should change child modules groupId declarations if the groupId matches the groupId of parent project.

I'm using m2e version 0.12.1.