Ant Trooper: "How long have you had that ant build?" Maven Skywalker: "About 3 or 4 releases." Ant Trooper: "I'd like to move to Maven but keep the ant folder structure." Maven Kenobi: "You don't need to keep the ant folder structure." Ant Trooper: "... I don't need to keep the ant folder structure ..." Maven Kenobi: "It's not the folder structure you're looking for." Ant Trooper: "... It's not the folder structure I'm looking for ..." Maven Kenobi: "We can go about our Maven business." Ant Trooper: "... you can go about your Maven business ..." Maven Kenobi: "Move along."
Ant Trooper: "Move along! Move along!" Not sure how much of the list is Star Wars savvy, buy hey. I didn't start it ;-). Anyway, getting off topic. > -----Original Message----- > From: Michael Haefele [mailto:[email protected]] > Sent: Thursday, May 19, 2011 12:42 PM > To: Maven Users List > Subject: Re: Maven folder structure > > "Let the Wookie win." > > On Thu, May 19, 2011 at 12:33 PM, Ron Wheeler > <[email protected]> wrote: > > +1 > > If you don't do things the Maven way, you will be in a battle until > Maven > > defeats you. > > You might as well give in early, you have no chance of wining. > > Maven is relentless and determined to bend you to its will. > > > > Ron > > > > On 19/05/2011 10:28 AM, Thiessen, Todd (Todd) wrote: > >> > >> Your scenario is not uncommon. I have seems many teams go through > it. > >> > >> The advice I always give is to NOT give in to the temptation to try > and > >> keep your existing structure when you move to maven. Your build > will be a > >> large mess. > >> > >> Converting to maven means more than simply adopting a folder > convention. > >> It is also about a build philosophy. For example, Maven strongly > encourages > >> one artifact per project. You will run into this when converting > your build > >> to use maven. If you deviate from using the default folder > conventions, in > >> my experience, only leads to greater confusion and more time to get > the > >> conversion done. > >> > >>> -----Original Message----- > >>> From: uday shankar [mailto:[email protected]] > >>> Sent: Thursday, May 19, 2011 10:15 AM > >>> To: [email protected] > >>> Subject: Re: Maven folder structure > >>> > >>> Hi Karl, > >>> I understand that you are asking me to stick to the default folder > >>> structure > >>> created by maven. > >>> This(sticking to the default folder structure) works fine when we > are > >>> using > >>> maven right from the beginning of the project.But what if say, > >>> Scenario 1: we have started the project in eclipse, and in the > middle > >>> of the > >>> development process I want to use maven. And maven commands seem to > be > >>> using > >>> the default folder structure. How can we use maven with a different > >>> folder > >>> structure(because a simple web application created using maven > commands > >>> have > >>> different structure when compared to a web application created in > >>> eclipse)?? > >>> > >>> Scenario 2: If say initially we were using Ant as the building tool > for > >>> a > >>> project. Now we want to use Maven as the tool , how do we implement > >>> that? > >>> What is the process of migration from ant to maven? > >>> > >>> If there is ambiguity anywhere, I will try explaining again. > >>> Thanks, > >>> Uday > >>> > >>> > >>> > >>> -- > >>> View this message in context: > http://maven.40175.n5.nabble.com/Maven- > >>> folder-structure-tp4409276p4409835.html > >>> Sent from the Maven - Users mailing list archive at Nabble.com. > >>> > >>> ------------------------------------------------------------------- > -- > >>> 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] > >> > >> > > > > > > --------------------------------------------------------------------- > > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
