Cool - Thanks D - That's definitely on the list
- Ole
--- Dan Tran [EMAIL PROTECTED] wrote:
I did exactly that in my ~70 projects tree.
one more rule, nail down all plugin versions in the
pluginManagement
section too.
-D
On 12/2/06, Ole Ersoy [EMAIL PROTECTED] wrote:
OK
OK - I'm hijacking my own thread.
I think I have a simple rule / best practice
now for structuring dependencies.
I would love feedback on this before I begin coding
the mojo that checks conformance.
Here are the rules:
Keep all dependencies specified in the top
level pom's
I did exactly that in my ~70 projects tree.
one more rule, nail down all plugin versions in the pluginManagement
section too.
-D
On 12/2/06, Ole Ersoy [EMAIL PROTECTED] wrote:
OK - I'm hijacking my own thread.
I think I have a simple rule / best practice
now for structuring
On 12/2/06, Dan Tran [EMAIL PROTECTED] wrote:
I did exactly that in my ~70 projects tree.
one more rule, nail down all plugin versions in the pluginManagement
section too.
Hmmm... does that work for plugins that you don't 'declare' in child poms?
If you're using the default config for a
