[ http://jira.codehaus.org/browse/MAVEN-1704?page=comments#action_71523 ] Arnaud Heritier commented on MAVEN-1704: ----------------------------------------
If groupId isn't defined, groupId=artifactId thus the behaviour described seems normal. The parent and the child projects will have a different groupId. The solution could be to force users to define groupId/artifactId if id isn't defined. Otherwise we fail the build. Will it broke so many projects ? I don't think. > artifactId is used as groupId when the latest is not defined > ------------------------------------------------------------ > > Key: MAVEN-1704 > URL: http://jira.codehaus.org/browse/MAVEN-1704 > Project: Maven > Issue Type: Bug > Components: inheritance > Affects Versions: 1.1-beta-2 > Reporter: Carlos Sanchez > Fix For: 1.1-rc1 > > > artifactId is used as groupId when the latest is not defined (using extends > at least), both in 1.0.2 and 1.1b2, which I believe it's a problem, maven > should complain. > Which is really a problem is that if pom a extends pom b, and no groupId is > defined in any of both, in 1.0.2 the artifactId of a is chosen as groupId, > while in 1.1 artifactId of b is the chosen one. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
