Re: [m2e-users] Multi module project m2eclipse problem

["Weaver, James" <james.weaver@xxxxxxxxxxxxxx>]

Hi Igor,

Problem resolved.

It was nothing to do with the files (poms or eclipse settings).  It was just
me making a mistake in the wizard.  I was using the "name template" field,
but hardcoding a value.  Silly.  What was happening was that it was thus
giving the parent project and child project the same value for project name,
and of course getting an error.  Once I changed the value in name template
to use the [artifactId] variable, the project for each maven module was
correctly created.

jim



On 3/4/11 7:18 PM, "Igor Fedorenko" <igor@xxxxxxxxxxxxxx> wrote:

> ³Checkout Maven Projects from SCM² is expected to work. Does your parent
> pom.xml have <module> element for the child?
> 
> --
> Regards,
> Igor
> 
> On 11-03-04 06:34 PM, Weaver, James wrote:
>> Hi,
>> 
>> I have Eclipse Helios with 0.12 m2eclipse and subclipse latest stable
>> release.
>> 
>> I created a new project locally that contains a parent maven module and
>> one child maven module. I created the child module by using the new
>> maven module wizard. I ended up with two eclipse projects, one for the
>> parent maven module, one for the child. Eventually there will be more
>> child modules. I understand that 0.12 m2eclipse does not support a
>> single eclipse project with nested maven modules, and that¹s fine.
>> 
>> So everything is fine up to this point, but when I check the whole
>> enchilada into subversion, and other developers with the same eclipse
>> version / plugin versions try to check it out, we have issues. The file
>> structure in SVN looks fine. I have at the parent root folder a pom.xml,
>> a .classpath, and a .project file. In the folder for the child module,
>> same set of files. This is how it is structured on my local drive where
>> I initially created things, and how it looks in SVN.
>> 
>> First we tried checkout of the parent using SVN wizard. No good. The
>> other developer ends up with a single eclipse project, and even though
>> our .project files for both the parent and child are checked into
>> subversion, the java nature is ignored. So no build path, source
>> packages shown in package explorer, etc. All that is missing. It¹s just
>> like a big pile of files and all the eclipse metadata that is present
>> (.project and .classpath files) are apparently being ignored.
>> 
>> Then we tried using the ³Checkout Maven Projects from SCM² wizard. Also
>> no good. Again, we get a single project in eclipse, and the child module
>> is just a folder inside this project. And again, the java nature of the
>> project is lost. There¹s a checkbox in this wizard to ³check out all
>> projects². We have that checked.
>> 
>> So what is the deal? Once I¹ve checked a multi-pom project into eclipse,
>> how the heck does another developer check it out in such a way that they
>> get one eclipse project for each pom, and the eclipse metadata that is
>> present in subversion (.project, .classpath etc.) is properly applied to
>> each of those eclipse projects?
>> 
>> Cheers in advance!
>> 
>> 
>> 
>> _______________________________________________
>> 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