I don't see why removing this restriction compromises project guidelines, it just allows for more flexibility when setting those guidelines.
Stan -----Original Message----- From: Rafal Krzewski [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 04, 2004 11:00 AM To: Maven Users List Subject: Re: / /OREF:CPT95AB9 Project>Dependecies Newbie question [EMAIL PROTECTED] wrote: > I actually consider this an unnecessary restriction. You should be > able to specify dependencies without forcing a naming convention > where version numbers are applied. You can use the .properties files > to get round this but you lose the inheritance benefits , I believe > (is this changing in later versions) Flexibility is important. Maven project is about setting guidelines for project development. A project that conforms to those guidelines is easy to comprehend and maintain. The Maven build tool is an important secondary pupropse. It helps to develop projects that conform to the guidelines. If you don't want to use the guidelines, but still use the build tool - you are on your own. R. --------------------------------------------------------------------- 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]
