> > - projects declare any aliases in their gump descriptor (and Maven > > allows that in the POM so it can generate the descriptor for > > them). So beanutils-core has an alias of beanutils > > I understand the part about projects declaring aliases (we may even > need to do that on the artifact level IMHO). I don't understand why > Maven needs to know about those at all - other than the Gump plugin, > maybe.
I'm thinking of the case where a project name changes, and the aliases are project metadata. I'm not talking about gump names changing - I'm talking about the artifactID changing over time (as was the case with beanutils). > I'm absolutely willing to maintain these aliases on an > as-needed basis. That sounds like the 3rd solution, however it seems the 1st worked anyway :) > > - we don't do anything. When a project changes name, they accept > > they are going to break projects and they have to catch > > up. > > But have the projects chosen the name? I mean, is it the project's > fault if the name we (Gump) assign to it and the one Maven uses for it > are different? Has the project itself any say in either of both? Sorry for mixing up words, Iwas talking about artifactId that the project chooses. - Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
