You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by John Fallows <jo...@gmail.com> on 2005/08/09 11:05:12 UTC
[m2] version string loses a zero during dependency resolution for pom
Using the latest M2 trunk.
Suppose a JAR dependency has <version>0.09</version>.
When this dependency is being resolved, the POM that is used has a
filename ending in 0.9.pom rather than 0.09.pom.
It loses the first zero after the decimal point, leading to a
dependency resolution failure.
Kind Regards,
John Fallows.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] version string loses a zero during dependency resolution for pom
Posted by Brett Porter <br...@gmail.com>.
Fixed in SVN (if a version part has a leading 0, version comparison
falls back to a basic string comparison).
- Brett
On 8/9/05, John Fallows <jo...@gmail.com> wrote:
> Using the latest M2 trunk.
>
> Suppose a JAR dependency has <version>0.09</version>.
>
> When this dependency is being resolved, the POM that is used has a
> filename ending in 0.9.pom rather than 0.09.pom.
>
> It loses the first zero after the decimal point, leading to a
> dependency resolution failure.
>
> Kind Regards,
> John Fallows.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org