You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by ji...@codehaus.org on 2004/08/03 00:18:23 UTC

[jira] Updated: (MAVEN-1410) pom.artifactId is missing from XML schema and pom.id should be removed

The following issue has been updated:

    Updater: Dennis Lundberg (mailto:dennis.lundberg@mdh.se)
       Date: Mon, 2 Aug 2004 6:18 PM
    Comment:
1. OK, it stays in POM3.

2. To add "artifactId" and still keep "id" we should probably use a "choice" in the XML schema. See attached patch for an example of how this can be done.

3. I will start writing documentation patches for the HEAD branch, unless someone objects.
    Changes:
             Attachment changed to maven-project-3.xsd.patch
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://jira.codehaus.org/browse/MAVEN-1410?page=history

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/MAVEN-1410

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MAVEN-1410
    Summary: pom.artifactId is missing from XML schema and pom.id should be removed
       Type: Bug

     Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: maven
 Components: 
             model
   Versions:
             1.0

   Assignee: 
   Reporter: Dennis Lundberg

    Created: Fri, 30 Jul 2004 4:06 PM
    Updated: Mon, 2 Aug 2004 6:18 PM

Description:
After some discussion on the dev-list "pom.id versus pom.artifactId - which is correct?" there seems to be some inconsistencies in the 1.0 release.

The discussion resulted in the following conclusions:
1. The element project.id should be removed from the XML schema
2. The element project.artifactId should be added to the XML schema
3. Documentation needs to be updated to reflect the above issues

1 and 2 should probably be done by one of the core developers, including decisions regarding version numbers for the XML schema. I can make a patch for it if you think that's ok.

I can make patches for the xdocs to fix 3. On which branch should I create the patches?


---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org