Bob Fields wrote:Your org.eclipse.emf.ecore pom is different than the one from the team.andromda repository, that one has a dependency on the emf.common 2.1.0. Unfortunately, there is no 'standard' dependency for these artifacts, since the 'master' on ibiblio is screwed up, various repositories (including andromda) went their own way with naming conventions and versions and dependencies for the org.eclipse artifacts. It wouldn't hurt anything in the current source tree to add this additional dependency to the uml2 metafacade, so it will be compatible with fornax and many other repositories, since we can't assume the downloaded artifacts will always come from team.andromda. You can delete/rename your local org/eclipse/emf/ecore directory and download the new one from andromda, or add the new dependency locally to metafacades/emf/uml2, or wait until the pom.xml is updated in the andromda3 source tree (shortly).
uml2.common 1.1.1 is the correct dependency in both places, I think you meant to say emf.common instead. We use maven2 for everything.
Yes, I meant emf.common
Now, there is something that I do not understand. You say that andromda team had to repackage the artifact because central one was screwed up. Ok, no problem with that, but then you must
change the version number and (for example) suffix it with as custom value. Otherwise there is 2 different artifacts with the same groupId/artifactId/version and depending on the environment (in fact whether the first looked repository is andromda or central) you will get different results. This is quite bad for build reproductivity.
The other solution is to use a dependencyManagement session in the poms to set the version of the used artifact. Then you do not even need to publish the jar.