maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lukas Theussl (JIRA)" <j...@codehaus.org>
Subject [jira] Updated: (MAVEN-1704) artifactId is used as groupId when the latest is not defined
Date Fri, 18 Aug 2006 17:18:48 GMT
     [ http://jira.codehaus.org/browse/MAVEN-1704?page=all ]

Lukas Theussl updated MAVEN-1704:
---------------------------------

    Attachment: MAVEN-1704.tar.gz

This is not what's happening in 11rc1: both parent and child projects have the *same* groupId
(the parent's) if no groupId is defined in either of them. They were different in m1.0, so
it's a problem. See attached test project.

> 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
>
>         Attachments: MAVEN-1704.tar.gz
>
>
> 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

        

Mime
View raw message