I thought all of the Maven2 projects used "org.apache.maven" as their groupId. We're doing it here, too (though I'm not very far along as of yet--we don't have an internal repository set up to deploy to).
..David.. -----Original Message----- From: Paul Spencer [mailto:[EMAIL PROTECTED] Sent: Friday, November 18, 2005 3:09 PM To: Maven Users List Subject: [m2] "mvn deploy" hangs if groupId contains a dot. Version............. Maven 2.0 Client.............. Windows XP Repository Server... Windows 2000 with cygwin for ssh. I found when the groupId contains a "." the goal deploy will hang after outputting the line during the second and subsequent deploys: [INFO] Retrieving previous build number from remote-repo As an example, set the the groupId to "com.foo". The first deploy will succeed. Note the deploy will create a directory "com" and sub directory "foo" instead of "com.foo". The second deploy will hang. According to the naming convention I found via a Google search ( http://maven.apache.org/reference/conventions.html ), the groupId and artifactId "should be comprised of lowercase letters, digits, and hyphens only". So my questions: 1) Should the convention be mentioned on the POM reference page where the groupId and artifactId are described ? http://maven.apache.org/maven-model/maven.html 2) Is their a bug somewhere in the deploy goal that incorrectly generates the directory structure when the groupId contains a "."? 3) If a "." in the groupId or artifactId is invalid, should this not be reported as an error? Paul Spencer --------------------------------------------------------------------- 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]
