Hi Mike, Michael Mills wrote:
> I have a problem on a 70+ module project. > > I have changed the group id of about 10 modules, then modified all the > other poms to use that new group id. > > I clean out my local repository, then build the modules. This results in > a compilation failure, stating that a library (hibernate), loaded as a > transient dependency for that module, is not available for javac. > > I was wondering if the group id in the format com.x.y means something > more than just a string label. Obviously it has an effect on where the > artifact lives in the local repo, but does it imply more in terms of > inheritance of other poms? (which is normally why you would specify the > parent pom). Maven artifacts are identified by groupId:artifactId:type:version:classifier, while type is 'jar' by default and the classifier is empty. So, if you change the group id of an artifact, Maven will no longer match it with older versions of that artifact ... but that's it. Any other error is more likely a definition error in the POM. > The only other info I can give is that we use SNAPSHOTs for most of > those modules. > > Does anyone know how to diagnose this issue further? Call maven with -X and/or use the dependency:tree goal to get more insight. - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
