I am building a project using Maven that contains Hibernate.
One of the downsides of Maven appears to be that there is no way (that I have found) to allow you to specify dependencies upon dependencies.
So, for example, when including Hibernate in my project, i have to work out what dependencies Hibernate has, and include those as well. If the included libraries have dependencies, they too must be included.
So I end up having to specify a tree of dependencies in my project, and spend a LOT of time working out what the tree is, just to get my project to a point where Hibernate works.
Now I know that this is not an issue specific to Hibernate. Any project that has dependencies in this manner will have this problem.
However, one thing that could be done is to include an xml fragment with hibernate (similar to the VERSIONS text file in the lib directory) that lists the dependencies, and version numbers, and maybe a comment or two explaining when the dependant jars are required.
That way, when a developer wants to use Hibernate in Maven they can copy the xml fragment (or include it as an entity reference) into their Maven project.xml
Thoughts?...
|