Re: [VOTE] Make groupId mandatory for POM version 4?

[Ben Walding]

+1 to fixing that

However what are the exact details of how it is to be fixed?

<groupId> / <id>

<groupId> / <artifactId> or <id> (with weird : and + notation)

<groupId> / <artifactId> or <id> (with : notation shorthand)

<groupId> / <artifactId>

Whatever the solution, i'd prefer that the dependency definition and the 
POM definition were equivalent.

What kind of deprecation period were you planning?

Cheers,

Ben

Vincent Massol wrote:
Hi,

I'd like to make <groupId> a mandatory element in POM version 4. What do
you think? The reason is that I don't what the default can be if it's
not specified and if we want to have plugins that start using the
id/groupId/type elements, there must be a groupId defined.
Here's my +1

Thanks
-Vincent
---------------------------------------------------------------------
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]