Also, having trouble installing and running the auction-sample by checking out each of the projects as eclipse projects. Can’t get them to compile due to unresolved maven dependency chain with jms1.1 and hibernate libraries not being on the repo and their versions…any ideas
the auction example is managed by Michael. He’s monitoring this mailing list as well and should respond shortly (unless he’s on vacation).
Michael, is there a specific reason why your root pom isn’t in the root of your folder structure? And I noticed that your the project version is 1.0.0. Maven usually expects work-in-progress to have the SNAPSHOT suffix in the project version.
Do you have a ".m2" sub directory with a "settings.xml" in your home
I have two additional entries there that are currently not included in
the project pom itself:
<name>Java.net Repository for Maven</name>
I think this should help.
Michael, is there a specific reason why your root pom isn't in
the root of your folder structure?
Eclipse doesn't work with that structure very well... But if you use
the Sonatype's Maven Integration for Eclipse and open the "auction-
root" it should work fine.
And I noticed that your the project version is 1.0.0.
It works for me but I'll fix that when I switch to the Versions Maven
Plugin next days.
Maybe I'll also create a small Eclipse Installation that contains
everything configured to get started out-of-the-box.
Thank you will try that out…also I would strongly encourage the team to look at eclipse integration for the adoption of the framework due to the breadth of developers who can leverage the framework with the tooling support. Eclipse with maven plugin and Spring integration is becoming a tooling mainstream (Springsource STS is a wrapped version of Eclipse with Spring perspecgives)I believe the key challenge for the mass adoption of these ideas is to make it easily consumable by the masses, otherwise people with give up very quickly before understanding the solution. Thanks for your quick response. This seems to be a high potential framework with lot of opportunity for the future.
tried changes…do not have m2 settings.xml…tried that and did not work as the eclipse overrode the one in m2, I thing…as I have eclipse install with profiles in settings and I had to add the above to the POM repositories tag and change this one dependency of hibernate version for c3p0 hibernate dependency to remove POM errors
However still getting build errors as unit tests failing…any ideas…thanks
T E S T S
As you suggested in an earlier post an Eclipse install would be of great help to review the sample in action…thanks