It'll work, some defaults might have to be overridden (eg SCM inheritance, though that's hopefully going to change), and the parent path if not ..
- Brett On 1/14/06, Grégory Joseph <[EMAIL PROTECTED]> wrote: > Wendy, > > A problem you might run into with this kind of configuration, > unrelated to the artifactId's name, is that your parent apparently is > to levels up, so you either need to use <relativePath> in <parent>, or > just know that maven will always use the installed/deployed version of > the parent pom, not the local one. > > HTH, > > g > > On 14/01/06, Arik Kfir <[EMAIL PROTECTED]> wrote: > > I'm doing that and things work fine... > > > > On 1/14/06, Wendy Smoak <[EMAIL PROTECTED]> wrote: > > > Attempting to resolve a question raised elsewhere... > > > > > > Does it matter if the directory names don't match the <artifactId>s of > > > the poms within them? > > > > > > For instance, I have /current/struts/action, and pom.xml has > > > <artifactId>struts-action</artifactId>. > > > > > > Are there any known issues with this? (With Maven or possibly Continuum?) > > > > > > Thanks, > > > -- > > > Wendy > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > -- > > Regards, > > _____________________________________ > > Arik Kfir [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
