Hello, I know I can configure maven to handle dir != artifactId.
But if you look at the adf source and at the tobago source they follow this convention(please correct me if I'm wrong). If they are a part of the myfaces project should they go back to the old structure?
We should try to get a unified layout. Is there a really problem to name the dir == artifactId. You have tp configure more if you not follow this convention. We should try to keep all simple. Is there a real technical reason to keep the dir name? I don't think so. Bernd Wendy Smoak schrieb:
Since I'm not having any trouble with the m2 Struts build where the directory names don't match the <artifactId>s, I asked on [EMAIL PROTECTED]: http://marc.theaimsgroup.com/?t=113724973700002&r=1&w=2 One person said no problem, another brought up the (unrelated) point that if the parent pom isn't directly above the child, you need to use <relativePath>. There are only two things I've found that Maven does *not* want to do, and they are 1) dealing with circular dependencies, and 2) building multiple artifacts from a single source tree. It's pretty flexible about everything else, and the more you conform to its conventions, the easier it gets. -- Wendy
