The version numbers come from the parent POM, so the "versionless"
reference to tapestry-ioc does have a version number supplied,
5.0.12-SNAPSHOT. There is no option in Maven to omit a version
number, but you can set up a kind of default in a parent POM.
I can't say what's going on in your environment that it's picking up
the wrong version.
On Thu, Mar 13, 2008 at 10:03 AM, Julian Wood <[EMAIL PROTECTED]> wrote:
> I noticed my unit tests failed when switching from 5.0.11-SNAPSHOT to
> 5.0.12-SNAPSHOT with a classnamelocator exception.
>
> I then noticed that I was using tapestry-ioc-5.0.10 rather than the
> 5.0.12-SNAPSHOT. Upgrading that to 5.0.12-SNAPSHOT fixed the problem.
>
> The bug seems to be in the tapestry-core-5.0.12-SNAPSHOT pom, where
> the dependency on tapestry-ioc is versionless, meaning that the last
> released version is used (which is 5.0.10). I think it needs to have
> <version>${project.version}</version> added.
>
> J
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Howard M. Lewis Ship
Creator Apache Tapestry and Apache HiveMind
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
