I've attached a patch that adds support for <groupId> element for project description and dependencies.
The implementation for dependencies is not completely correspond to the user guide (http://jakarta.apache.org/turbine/maven/reference/user-guide.html#Namin g Conventions). It uses <id> instead of proposed <artifactId>. The main idea behind this decision is backward compatibility. This patch doesn't change existing behaviour, it just extends. If there is no <groupId> element specified for the project description the project id will be used instead, as usually. If there is no <groupId> element specified for the dependency the package id will be used instead, as usually. Best regards, -- Alexei Barantsev, ISP RAS E-mail: [EMAIL PROTECTED] ICQ : 3959207 -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
