I mean to say, If I wants to use maven then I have to use in this way, I have to maintain version, but for my project maintaing of version is not a problem. and Management won't like Idea to have directory for each module. So if Maven is enough flexible then adoptation in any project becomes very easy.
I was using maven 1.0 in my past project and was quite comfertable and because of this as a System designer I propose to use Maven in my current project. But with Maven 2.0 I'm trying to fit all my requirements from past 1 week but not suceed. now I'm very much frustrated. Wayne Fay wrote: > > He means "the Maven dev group is pushing a particular agenda which my > organization disagrees with." > > Wayne > > On 7/3/07, Thorsten Heit <[EMAIL PROTECTED]> wrote: >> > I don't like directory structure which is just over burden for >> maintaince. >> > As of now we do not have any problems to maintain version of our jars. >> > But because maven thinks that we have problems in maintaing versions so >> we >> > should adopt maven directory structure is stupid idea. >> >> Sorry, but I don't understand what you mean by "Maven thinks that we have >> problems...". Can you explain that? >> >> >> Regards >> >> Thorsten >> >> --------------------------------------------------------------------- >> 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] > > > -- View this message in context: http://www.nabble.com/how-to-configure-Default-Repository-Layout-for-local-repository-tf4018468s177.html#a11416350 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
