ID is an identifier for use in the store, it has been used all over the place to refer to a particular project
Name is the actual name of the project used for display purposes only, name can be free form. artifactId, groupId, and version are maven conventions used for referencing in dependencies (among a host of other things), basically allowing you to refer to pretty much any java artifact with the trinity of (groupId, artifactId, version) There is another thread on here about deprecating the use of ID throughout the api in favor of using a String based KEY (with content restrictions like no spaces, etc) effectively retiring the ID to be internal to the store and allow name to be strictly enforced as solely a presentation element...less of an issue right now with projects then project groups. I am hoping to get to work on that within a week or so over some vacation time. I just warn you since that will have repercussions across the rpc code as well...I think I'll probably work on this with rahul and we'll try and clean up the rpc and web integration at the same time. jesse On 12/12/06, Brad Harper <[EMAIL PROTECTED]> wrote:
Hello: I'm implementing a java client for RPC-XML that will be installed as a svn post-commit hook. In looking at the continuum model, as described by https://svn.apache.org/repos/asf/maven/continuum/trunk/continuum-model/src/main/mdo/continuum.xml Can anyone explain the Project.id field (which is required) and how it differs from fields Project.name and {Project.artifactId, Project.groupId, Project.version}? Thanks. Brad
-- jesse mcconnell [EMAIL PROTECTED]
