On 2014-06-19, 10:30, Stephen Connolly wrote:
- Igor is*mostly* right in that we should not deploy the pom that is used to build to the repository... - Where Igor is wrong is that for <packaging>pom</packaging> we should actually deploy the build time pom to the repository... probably with the classifier `build`... this is safe as `pom` does cannot have a classifier in model version 4.0.0. - You couple that with a simple and obvious restriction... your parent must be the same or earlier version of Maven. You cannot have as a parent a newer version of Maven than the child is built with.
I think there is more to this. At very least we need to decide what to do with <parent> in 4.0.0 compatible poms. Maybe we should always deploy effective pom with build-related elements removed. I am also not sure if it is enough to deploy "build" parent poms as is. Your suggested "parent must be the same or earlier version of Maven" implies new versions of Maven can read older pom formats, which I think will significantly limit our flexibility to evolve pom format. I wonder if we can have different solution for force parent poms, like org.apache:apache, which are used by multiple projects and different versions of maven and project-specific parent poms, where it is much easier to require specific version of maven. -- Regards, Igor --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
