This is no longer true, Eclipse (m2e) supports both approaches nowadays.
On 23 Dec 2011, at 23:02, Dan Allen wrote:
I agree that it potentially puts some bumps in the road, but the benefit is
that you can import that parent into the IDE when it's adjacent to the
other modules. When it's above
I agree that it potentially puts some bumps in the road, but the benefit is
that you can import that parent into the IDE when it's adjacent to the
other modules. When it's above the modules, at least in Eclipse, it can't
be imported without having all the submodules as resources inside the
parent
Hi,
Oh, I did not know that. I am using IntelliJ, no problems here ;)
Regards,
Jakob
2011/12/24 Dan Allen dan.j.al...@gmail.com:
I agree that it potentially puts some bumps in the road, but the benefit is
that you can import that parent into the IDE when it's adjacent to the
other modules.
To: deltaspike-dev@incubator.apache.org
Cc:
Sent: Friday, December 23, 2011 11:58 PM
Subject: separate parent module - why not use the pom.xml from the main
folder as parent?
Hi,
I just checked the initial code in our git repo and found out that we
have a separate parent module. Is there a reason
