On Wed, 26 Nov 2008 16:13:32 David C. Hicks wrote:
Have you tried using the eclipse:eclipse plugin? That's how I'm
talk about the hard way...
eclipse:m2eclipse... and install the m2eclipse plugin...
--
Michael McCallum
Enterprise Engineer
mailto:[EMAIL PROTECTED]
m2eclipse and Q4E support nicely hierachical projects (with eclipse 3.3+ i
think) and the release plugin will be happy.
Arnaud
On Wed, Nov 26, 2008 at 4:10 AM, Rusty Wright [EMAIL PROTECTED]wrote:
Ok, thanks. I'm using the flat structure because that seems to work better
with eclipse. I
Michael McCallum wrote:
On Wed, 26 Nov 2008 16:13:32 David C. Hicks wrote:
Have you tried using the eclipse:eclipse plugin? That's how I'm
talk about the hard way...
eclipse:m2eclipse... and install the m2eclipse plugin...
I like m2eclipse, but the last few times I've tried to
I have the same problem. I tried to get the answer here but no one could
help me, maybe you are luck.
On 11/24/08 7:58 PM, Rusty Wright [EMAIL PROTECTED] wrote:
I'm using the flat structure where the parent directory (cars_parent) is a
sibling of its sub modules.
The parent's pom starts
Ok, thanks. I'm using the flat structure because that seems to work better
with eclipse. I guess I'll just have to walk away from the release plugin.
David C. Hicks wrote:
It has been well over a year ago, but the last time I tried to do this,
I encountered similar problems. It was at that
Have you tried using the eclipse:eclipse plugin? That's how I'm
working with projects now. It works great - just remember to run it
again if you change the dependencies in your pom. Then, you can arrange
you project hierarchically, use the release plugin, and still be working
in Eclipse.
I'm using the flat structure where the parent directory (cars_parent) is a
sibling of its sub modules.
The parent's pom starts with
project
xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=
