Re: [m2e-users] nested modules

["ildella@xxxxxxxxx" <ildella@xxxxxxxxx>]

I think this is so true. 
I haven't seen a single developer I've met in the last year, from zero to 15 years of experience, that does a damn "svn co". They checkdout project in eclipse or whatever IDE they were using. 

So they want a solution for a problem they create, that instead should be addressed with other tecniques, like "keep your SCM organized and up to date" not hoping that some tools fix a problem that does not really exists.

On Wed, Dec 1, 2010 at 2:09 PM, Benson Margulies <bimargulies@xxxxxxxxx> wrote:

Igor, I get this idea that there are people out there who have never,
ever, done a conventional checkout of their projects into the file
system. Their projects are sitting in source control in some
arrangement that does not correspond to the aggregate/parent
structure, and they have become accustomed to taking advantage of the
'classic' eclipse mechanism of grabbing projects  from wherever and
checking them out into the workspace.

I've never personally seen the attraction of this, but I think it is
what drives all the upset email about the SCM integration.

On Wed, Dec 1, 2010 at 7:47 AM, Igor Fedorenko <igor@xxxxxxxxxxxxxx> wrote:
> M2E supports conventional maven project layout, where child modules are
> located in subfolders of parent/aggregator project on filesystem. You do
> not need to change how you projects is stored in scm or on local filesystem.
> Likewise, you do not need to change command line build.
>
> When M2E imports maven project in Eclipse workspace, it will map
> underlying filesystem resources to a flat list of workspace projects,
> again without changing how the projects are located on filesystem.
>
> --
> Regards,
> Igor
>
> On 10-12-01 02:45 AM, Van Den Bosch, Gunther wrote:
>>
>> Hi,
>> For quite a while our environment is based on:
>>
>>    * Eclipse
>>    * m2Eclipse
>>    * Maven
>>    * Mercurial
>>    * Hudson
>>
>> Until now we have been using the Galileo version of eclipse and an older
>> version of the m2Eclipse plugin. This setup also supported nested Maven
>> modules which could be build within Eclipse and also using Maven command
>> line through Hudson. The whole project (including the nested modules)
>> was put in the Mercurial scm.
>> When we tried to upgrade Eclipse(to Helios) we found that the
>> corresponding m2Eclipse plugin no longer supports nested modules. I read
>> in the docs that one should use a flat structure and map every nested
>> module into a separate Eclipse project. This could work when using SVN
>> which allows checking out a 'subtree'. As we are using Mercurial, this
>> seems no longer possible (an Eclipse project maps to a Mercurial repo).
>> Can somebody describe which approach we should take to be able to:
>>
>>    * develop in Eclipse
>>    * use Mercurial scm
>>    * use multiple modules
>>    * build from maven command line (Hudson)
>>
>> Thanks,
>> Gunther
>>
>>
>>
>> _______________________________________________
>> m2e-users mailing list
>> m2e-users@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/m2e-users
>
> _______________________________________________
> m2e-users mailing list
> m2e-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/m2e-users
>
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users

-- 
Daniele Dellafiore
http://danieledellafiore.net