Looks like the Spring Context 2.0.2 jars were published with
${project.version} in them which is not being properly interpreted by
Maven. So instead of using the ${project.version} from the
spring-context-2.0.2.pom (which should substitute 2.0.2), Maven is
using the version from the currently exec
I'm running into this right now on a machine having to do with Spring
and trying to download version 2.4.1 jars. Was there ever any
resolution to this?
Rich
LAMY Olivier wrote:
> Hi,
> Look : http://jira.codehaus.org/browse/MNG-2339
>
> I think it's a big issue because sometimes it's impossible
Hi,
Look : http://jira.codehaus.org/browse/MNG-2339
I think it's a big issue because sometimes it's impossible to use
${project.version}.
Sometimes works sometime not (that's certainly why this issue will be hard
to solved).
--
Olivier
-Message d'origine-
De : JRatTFT [mailto:[E
