Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Users List" <users@maven.apache.org>
Received-SPF: pass (nike.apache.org: local policy)
Message-ID: <4DD5464C.4010508@artifact-software.com>
Date: Thu, 19 May 2011 12:33:16 -0400
From: Ron Wheeler <rwheeler@artifact-software.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-GB;
 rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: users@maven.apache.org
Subject: Re: Maven folder structure
References: <1305799527370-4409276.post@n5.nabble.com>
 <1305802354630-4409348.post@n5.nabble.com>
 <1305805549596-4409454.post@n5.nabble.com>
 <1305813010723-4409763.post@n5.nabble.com>
 <1305814470797-4409835.post@n5.nabble.com>
 <6369CB70BFD88942B9705AC1E639A33822CBF66E0D@DC-US1MBEX4.global.avaya.com>
In-Reply-To: 
 <6369CB70BFD88942B9705AC1E639A33822CBF66E0D@DC-US1MBEX4.global.avaya.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

+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:adonis.uday@gmail.com]
>> Sent: Thursday, May 19, 2011 10:15 AM
>> To: users@maven.apache.org
>> 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: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org