> I guess this has been asked before, but is there any way to gracefully > handle situations in a multi-level modular project where the artifactId > does not always correspond to the folder name of the module?
Maven operates under certain conventions. This is not the convention, thus it is not well supported. > parent with "/childWithOtherName" appended, and there is no way I can > force it to use "/childB", unless I specify the whole path, which is > tedious with large projects. This is the "not well supported" aspect. I'm not even sure how good of an idea this is. Why can't you just change the artifactId or the module name?? Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
