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 (asf.osuosl.org: local policy)
Message-ID: <434D5EF4.6060404@paraware.com>
Date: Wed, 12 Oct 2005 15:07:32 -0400
From: Brian Bonner <brian.bonner@paraware.com>
User-Agent: Thunderbird 1.4 (Windows/20050908)
MIME-Version: 1.0
To: Maven Users List <users@maven.apache.org>
Subject: Re: Flattened Eclipse Project
References: <434D531F.4050707@paraware.com> <434D552B.5070104@paraware.com>
In-Reply-To: <434D552B.5070104@paraware.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

FWIW, This sample posted in MNG-743 is *very useful*.  Nice way of 
illustrating dependent builds.  If you haven't pulled this down already, 
I'd recommend doing so and running an m2 install against it and then m2 
eclipse:eclipse.  It's a great starter template.

The biggest pain I see is that if a developer (me) uses eclipse to 
checkout the root project he has to check it out to another location and 
then delete the project from the workspace (without actually deleting 
the contents).

After this (at least with 3.1) the developer (me, again) can import the 
root project.  It will correctly import each of the modules into eclipse 
(or so it seems).

A couple of questions:

1.  I noticed the dependencies are at the pom packaging level vs. the 
war/ear, etc. level.  Is there a reason for this, except that if you for 
example added another war to the servlets project, the assumption is 
that this *too* would be dependent upon fop?

2.  I noticed that eclipse:eclipse only uses standard builders (i.e. 
jar).  Did anyone have any thoughts on generating the other eclipse 
artifacts (for example for the WTP) for WARs.

Thanks.

Brian


Brian Bonner wrote:
> Doh!  I found this post after posting my post:  
> http://www.nabble.com/Re%3A-M2-Recommended-Project-Layout-and-Eclipse-t361944.html#a1002147 
>
>
> I'm reading through it now.
>
> Brian
>
>
>
> Brian Bonner wrote:
>> Hi,
>>
>> Is there any way to create a flattened project hierarchy that is 
>> eclipse-friendly.  I.e.
>>
>> instead of:
>>
>> master-project
>> +---sub-project-A
>> +---sub-project-B
>>
>> to have a hierarchy like this:
>>
>> master-project
>> sub-project-A
>> sub-project-B
>>
>> Likewise, maybe this is my naivete with respect to using maven w/ 
>> eclipse and sub-projects.   Can anybody give me some suggestions in 
>> this regard?
>>
>> Eclipse (seems) to cater to a flattened hierarchy (dynamic web 
>> project, EAR, etc.)  projects and it expects things in a nice 
>> location for testing and easy use of their debugger.
>>
>> btw, I found this post:  
>> http://www.nabble.com/Eclipse-configuration-for-a-root-multiproject-t66873.html#a190854, 
>> but this is for maven-1 and I'm not sure if it's easy to convert this 
>> for m2.
>>
>> Thanks.
>>
>> -- 
>> Brian
>>
>>
>> ---------------------------------------------------------------------
>> 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