Hello Rafal, Thanks for your email.
And thanks for pointing out that I am doing something wrong. Can you please point me to some study material or anything which explains me standard way of using maven. I am unable to understand how will I be able to package the release if I build each project into its own eclipse folder. Can you please tell me what is the best way to use maven.. ? I will be extremely happy if you can send me a dummy example whicb can used in large scale multip module application. Thanks Shumail On Nov 20, 2012 11:10 AM, "Rafał Krzewski" <[email protected]> wrote: > You are using Maven in completely non-standard way. Buliding two > projects into the same directory is can fail in many "interesting" ways, > and I can't even imagine the mess resulting from mixing a 100 builds! > This is definetely not something that Maven or m2e developers would > endorse or support. There are many clean & workable solutions to > application launching & classpath management. Sorry buddy, but you are > doing it wrong. > > Cheers, > Rafał > > On 11/19/2012 05:52 PM, Shumail Arshad wrote: > > Sorry, I just gave an example. But your statement below is worrying for > me. Why can't I specify a non-default directory, which does not exist in > the project. What If I have 100 projects and I want to build all of them in > the same directory so that classpath can be specified to single libs folder. > > "You can use any non-default directory for your project, in m2e, as long > as it's located under your project." > > > > _______________________________________________ > m2e-users mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/m2e-users > >
_______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
