First if this works i say there is no clear way to send to the list. I made a guess and expect that will get a bounce. (aka, how add to web how to talk to you)
I suggest that "those that know" do a clean download of the Ode source. That says you rename/remove your .m2 and do what it says on http://wiki.apache.org/ode/GettingSourceCode Now with nothing in the Maven .m2 try to build Ode. Besides Maven doing its odd things (if the world was perfect then Maven would fit right in) you may find some odd things. These 'odd things' are not obvious to those that just refresh and/or update the previous. However, being a newbie that is not my case. Anyway, below is a 'roadmap' of how it might work for someone that has nothing in their Maven .m2 given the state of the checkout. I wrote it for the managers that have people working for them and need to build Ode. Still, suggest you try it. Those of us on the 'outside' just try, and try, and try and, ... Thanks, Bill ======================= This assumes that your .m2 is empty or does not exist. Building SM may modify this as there are some overlaps. Note: That an empty .m2 can cause maven errors as it cannot get to a remote and/or the transfer just fails. This will occur even if you find the file on the remote. The general rule is to do it several times, wait hours and repeat. Then you can search to see if it just missed. Note: That sometimes maven will fail because it cannot get a .pom file. This is odd as it depends on the order that you do things. That is, clear all and do again in a differnt order and it does not care that a pom is missing, e.g., an Axis2 kernel pom. Note: That sometimes you cannot get around a remote error as it depends on speed. Sometimes slower is better -- so much for good thread programming -- so go through vpm to slow things down. Check out the version while in the dir you want it to appear: svn co http://svn.apache.org/repos/asf/incubator/ode/trunk/ ode-junk If ode-junk is not your name for the dir then change it. >From the checkout dir run the command mvn install If you get the error: Missing: ---------- 1) org.apache.ode:ode-dao-hibernate-db-derby:tar:2.0-SNAPSHOT Then do the follow command sequence: cd dao-hibernate-db-derby mvn package install <!-- you should get "BUILD SUCCESSFUL" from this step --> cd .. mvn install This may or may not result in the following error: ---------- 1 required artifact is missing. for artifact: org.apache.maven.plugins:maven-assembly-plugin:maven-plugin:2.1.20060107 .015454.4 At this point you need to remove the dependency on a build number. So open pom.xml in your checkout dir (notepad may not be good as some files are unix). Search for "20060107" so you see the build number in <!-- Alex: Use specific version for release --> <!--version>2.1-SNAPSHOT</version--> <version>2.1.20060107.015454.4</version> Edit the last line to read: <version>2.1</version> Save the file. Then go back and run the command mvm install in your checkout dir. At this point you should get BUILD SUCCESSFUL as the end result. Now in the target of jbi-examples is the file tarball.tar which sort of looks like what you need to run the examples in SM. No, they will not work but at this point it is just a simple ant xml to figure out what file to make/or the changes need so that is left to the reader ==============================================================
