>
> I think doing some sort of on-the-fly translation into a 4.0.0 POM purely
> to be deployed for backwards compat would be enough here...though we may
> want to explore how we could make Maven smart enough to say, "I can't read
> this POM, use a later version" or somesuch...
>
> Why only consider deployed POM for backward compatibility ? Same system may
use older maven somewhere else and still share the localRepository. We
should either always translate the POM to 4.0.0 even during install, or do
some sort of double-versioning.

Reply via email to