Incidentally,
Do you by chance know if
there is a way to make
mvn eclipse:eclipse work
for a project with pom packaging?
This would be really nice for quickly
editing the dependencyManagement section
on a parent.
Thanks,
- Ole
--- Wendy Smoak <[EMAIL PROTECTED]> wrote:
> On 12/2/06, Ole E
Yes!
Cool - It makes perfect sense.
Thanks for the reassurance.
--- Wendy Smoak <[EMAIL PROTECTED]> wrote:
> On 12/2/06, Ole Ersoy <[EMAIL PROTECTED]> wrote:
>
> > I'm leaning toward this as a best practice,
> because we
> > could have a build that has 3 modules and then we
> add
> > a 4th on
On 12/2/06, Ole Ersoy <[EMAIL PROTECTED]> wrote:
I'm leaning toward this as a best practice, because we
could have a build that has 3 modules and then we add
a 4th one, and if the parent had dependencies included
in the pom, the 4th module automatically gets them,
and maybe it didn't really want
Hello again,
We were discussing this on the Apache directory dev
list as well, and Greg Duffy provided some
clarification.
So I attempted to come up with a best practice around
it.
If you have a chance it would be great to hear more
feedback on this. Here is my answer to Greg.
OK - I think
Hi,
I'm working on a mojo that will analyze a build's
poms and come up with structuring recommendations.
For dependencies I had a simple rule in mind.
Keep them either on the parent or the child, unless
one of the children has to override the parent's
version setting...so this would only happen
