There will be confusion no matter what we do and the current name is the most specific, might as well leave it. Dropping back to 1.0.0 is good since it's really a new thing. It will add to the group to help distinguish that its new. +1 to leaving the artifactId +1 to the 1.0.0 version.
-----Original Message----- From: Jason van Zyl [mailto:[EMAIL PROTECTED] Sent: Sunday, August 12, 2007 2:47 PM To: Maven Developers List Subject: Maven Artifact I have separated out maven-artifact into its own module here: https://svn.apache.org/repos/asf/maven/maven-artifact I will attempt to use it in trunk mid week, and right now I have change the groupId to org.apache.maven.artifact. Do we need to change the name of the artifactId to prevent confusion? The groupId should prevent any dependency clashes, but the name being the same may cause some confusion. I was also going to drop the version back to 1.0.0-SNAPSHOT (start using major, minor, micro). Thanks, Jason ---------------------------------------------------------- Jason van Zyl Founder and PMC Chair, Apache Maven jason at sonatype dot com ---------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
