On 15 August 2014 13:17, Gordon Sim <[email protected]> wrote: > On 08/15/2014 12:56 PM, Robbie Gemmell wrote: > >> On 14 August 2014 21:42, Gordon Sim <[email protected]> wrote: >> >>> (3) qpid-java-0.30-beta.tar.gz >>> >>> - tests all pass, packages produced >>> - tested 0-10 and 1.0 client examples >>> (I couldn't get the mvn build to work for these; probably something >>> I'm >>> doing wrong though) >>> >>> >> What issue did you see? >> > > I got: > > $ mvn clean package dependency:copy-dependencies -DincludeScope=runtime >> -DskipTests >> /usr/lib/jvm/java >> [INFO] Scanning for projects... >> [ERROR] The build could not read 1 project -> [Help 1] >> [ERROR] >> [ERROR] The project org.apache.qpid:qpid-client-examples:0.30-SNAPSHOT >> (/home/gordon/qpid-releases/0.30/installation/java_install/ >> qpid-client/0.30-SNAPSHOT/example/pom.xml) has 1 error >> [ERROR] Non-resolvable parent POM: Could not find artifact >> org.apache.qpid:qpid-java-build:pom:0.30-SNAPSHOT and >> 'parent.relativePath' points at wrong local POM @ line 21, column 11 -> >> [Help 2] >> [ERROR] >> [ERROR] To see the full stack trace of the errors, re-run Maven with the >> -e switch. >> [ERROR] Re-run Maven using the -X switch to enable full debug logging. >> [ERROR] >> [ERROR] For more information about the errors and possible solutions, >> please read the following articles: >> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ >> ProjectBuildingException >> [ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/ >> UnresolvableModelException >> > > Ok, so that is saying that the parent pom cant be found, because it isnt present in your local repo, or any remote repo it has checked, and cant be found at the indicated/assumed relativePath from th pom (because as you mention later you are building from the client package, meaning the parent isnt available relatively as it would be in-tree).
Thats an interesting case because that pom it is in a remote repo you have access to (the apache snapshots repo), however it is the parent poms (qpid-java-build, then qpid-parent, and then apache) that it couldnt discover which would normally let it know where the snapshots repo is in our case, and so it was out of luck. Installing the main build locally would resolve that. As would changing the example poms to reference the snapshots repo directly. > > I mentioned in the readme that you need to do a local install of the >> clients to test locally-built artifacts, but in this case because the >> source is still versioned 0.30-SNAPSHOT the examples should resolve >> against >> the remote snapshots repo too. >> > > I saw that, however I was looking at the binary package, which I had > produced from the source and then extracted into my install area. I wasn't > sure if it applied in that case It does. > , or how I would go about installing from there You would install the whole java tree first in this case (the main qpid-java-build pom and the clients are all thats needed to be precise, but the easiest way to achive that would result in everything since they are all built as an aggregate currently, and it isnt really worth the hoop jumping to get only those bits). > (or if install only works from the source build). You can manually install poms/jars/etc locally using a specific command, but the easiest/typical way is certainly just to run 'mvn install' on the original source build. > This is all largely about my lack of understanding regarding maven as a > tool, and I imagine those more familiar with it will be quite at home. > > I just ran javac against the examples in the end, since all the dependent > jars were there in lib and that was simple enough. > > Yes, I actually considered documenting how to do that in the README, but decided to keep it shorter by not, since I figured it was simple enough that those who might want to would likely know how to already.
