toggle quoted messageShow quoted text
Agreed. Rather than doing the
technically wrong thing, I think we really need a well-written
guidelines to project structure, which not only dictates what, but
also details why.
I will add this to the cross-project best practices group wiki and
will follow up from there.
On 10/15/2014 10:23 PM, Colin Dixon wrote:
I think the goal in making sure that the directory
structure corresponded to pom structure (in terms of parents)
was more about making it easier for humans to understand and
parse the the variety of poms in a project easily.
Maybe the *right* approach is to put a comment in the
actual root (aggregator) pom saying that "this is not the
logical parent, in pom space, the logical parent can be found
at: <path-to-project-parent-pom>". Alternately, if there
are a few different parent poms, we should explain that there.
Ideally, we'd also communicate to all projects (both as
tutorials for projects and as best-practices to follow going
forward) what a common-case setup would look like.
If projects mostly followed these patterns it would help a