On 12/11/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
did you finally remove the usage of a parent pom for install-files? that made it easier to add information to all the artifacts than regenerate all poms
yes, at the moment no parent is used. It's a minor change, I could turn it on before the release if needed. Sincerely I still think it's better to have such info into each pom, given that a change in the parent pom should mean a new release for it and an update of each child (ok, you say you can "fix" it in a single place in the repo, but everybody who previously downloaded also a single eclipse artifact before will never see that change, since the parent pom will never be downloaded again). If you put those informations into each pom and change them only for different releases (I don't think we should even plan to "enrich" already deployed poms) that will be transparent to users. Another reason is that the make:artifacts goal was also intended to help users in generating/installing artifacts from a local eclipse installation to a local maven repository: breaking this by requiring a remotely downloaded parent pom doesn't worth this change IMHO. Anyway: at the moment only you and me discussed about this, I would like to hear some other thoughts from maven/eclipse users and from other devs involved in repository management (jason, brett?). Let's keep the release vote anyway, please, and I will turn the writing of the <parent> tag on or off based on the result of this discussion... fabrizio --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
