On Thu, 2003-11-13 at 21:08, Ben Walding wrote: > +1 to fixing that > > However what are the exact details of how it is to be fixed? > > <groupId> / <id> -1
> <groupId> / <artifactId> or <id> (with weird : and + notation) -1 > <groupId> / <artifactId> or <id> (with : notation shorthand) -1 The <id/> has to go away because this is something we will define internally and the fugly notation was just a bad idea from the start. > <groupId> / <artifactId> +10 > 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] -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
