Hey, two weeks ago, Christophe Cordenier has been promoted as an Apache Tapestry 5 committer. Congratulations to him. This is definitely a great opportunity for “spread the source” to contribute to the Tapestry 5 framework.
As far as I know, his first goal is to contribute to the documentation effort started by Ulrich Stärck. By the way, Ulrich has been promoted as an Apache Tapestry 5 PMC member.
As a side news, wooki 0.3 is almost finished. This will be a huge release in terms of refactoring and new features. We made some terrific things. Stay tuned, the announce will come in next few days.
Those new modules are extremely interesting. The “migrations” module could be a small revolution for our business. I’ve been trying to do something similar for some time now, but this is far smarter than my attempts :)
Check this out : https://twitter.com/robinkomiwes/status/18039995728 ! :)
Sweet.
I just had to try this new module out. I ran into one problem. In our application we have classes packaged in jars. When we make changes to those classes during development, they are compiled into WEB-INF/classes, making them override the ones in the jars because WEB-INF/classes is read first by the classloader. This is a convenient way of developing for us.
But: The ClassNameLocator does not take this into account. So it finds 2 classes with the same name, one from the jar and one from WEB-INF/classes. This makes the MigrationManager complain about “More than one migration are having the same version”, of course.
I’m not sure if this is a ClassNameLocator bug, your bug or my hack bug. What do you think?
I would say that the problem come from ClassNameLocator. It seems that there is no handling of duplication.
We will seriously think about your problem and try to find a solution, maybe by opening the discution directly on tapestry mailing list and providing a patch…
But if you have an immediate solution, maybe you can fork our project on Github, implement the solution and then ask for a pull request.