On 08/26/2010 10:37 AM, Patrick Wright wrote:
A big advantage of Maven is that all the major Java editors all allow you to open a project by opening a POM file. All resources, paths, etc. are immediately configured. This is a big plus for people who want to explore the code and possibly contribute. Dependency management is also much more straightforward using Maven.
I dont see a problem with dependency management with the current situation. If you create a dependency, you should include the stuff you depend on. A pom file for the final result to use river as a maven dependency should cause no problems. But we should differentiate between offering a set of jars with a pom file, and using it for building river altogether.
As to repeatability, maven is very easy to use when you take the trunk of a project, but if you want an older version, and rebuild, my personal experience is that its much harder. When i was bitten by maven, it was in circumstances where dependencies had disappeared. So my personal experience proved to me that it is hard for opensource projects to have the discipline to ensure that one can produce repeatable builds for older versions at some point in the future.
And thats something i find very important. Or are you saying, ok, as a developer-user of river, you live with the build of the day, and if you want to have something stable, you should ensure stable baselines yourself?
The current situation ensures these stable baselines. Gr. Sim
