[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [m2e-users] nested modules
|
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
