On 4 April 2014 12:56, Fraser Adams <fraser.ad...@blueyonder.co.uk> wrote:
> Hey Robbie, sorry I've taken so long to start looking at this - I've been > trying to break the back of some of my JavaScript Proton stuff. > > I'm afraid that I've fallen at the first hurdle :-( > > Well second - at least I managed to pull down > https://svn.apache.org/repos/asf/qpid/branches/QPID-5610- > maven3-build-qmf-tools OK ;-> > > The first thing that I tried to do was to build the Java Broker and client > using the instructions below: > > " > > Optionally, build the Java broker/client/etc and install them in your local > repo. If you don't, the QMF2 tools build will just use the artefacts from > the snapshots repo: > cd <qpid trunk checkout>/qpid/java/ > mvn clean install -DskipTests=true -Denable=true > > " > I first tried > cd /home/fadams/qpid/QPID-5610-maven3-build-qmf-tools/qpid/java > > mvn clean install -DskipTests=true -Denable=true > > but that barfed with: > > " > [INFO] Scanning for projects... > [ERROR] The build could not read 1 project -> [Help 1] > [ERROR] > [ERROR] The project org.apache.qpid:qpid-java-build:0.28-SNAPSHOT > (/home/fadams/qpid/QPID-5610-maven3-build-qmf-tools/qpid/java/pom.xml) > has 1 error > [ERROR] Non-resolvable parent POM: Could not find artifact > org.apache.qpid:qpid-parent:pom:1.0-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 > " > > I reread the instruction and noticed you actually said "cd <qpid trunk > checkout>/qpid/java/ " though I've no idea why it wouldn't work using the > branch? > > But in any case when I did > > cd /home/fadams/qpid/qpid-trunk/qpid/java > > mvn clean install -DskipTests=true -Denable=true > > I got the same error :-( > > the pom.xml has > > <parent> > <groupId>org.apache.qpid</groupId> > <artifactId>qpid-parent</artifactId> > <version>1.0-SNAPSHOT</version> > </parent> > > In the section referred to in the error > > > > My *guess* is that this is all because I haven't yet done > > > " > > Ensure you have the latest qpid-parent pom installed in your local repo (a > temporary step until we start deploying it soon, so I didn't document this > bit): > svn cohttp://svn.apache.org/repos/asf/qpid/qpid-parent-pom/trunk <your > > chosen dir name> > cd <your chosen dir name> > mvn clean install > > " > > The reason I didn't was because I wasn't sure from your instructions > whether building the broker/client etc. was supposed to do that (though I'm > guessing not from the error) but TBH also when you say install in the local > repo above I'm not quite sure what you mean I suspect that you probably > mean "/home/fadams/.m2/repository", so do your instructions above mean in > my case: > > svn cohttp://svn.apache.org/repos/asf/qpid/qpid-parent-pom/trunk > /home/fadams/.m2/repository > cd /home/fadams/.m2/repository > mvn clean install > > No... "install in the local repo" is what the mvn clean install will do... So, you literally just have to follow Robbie's instructions: check out the qpid-parent-pom/trunk directory, run mvn clean install from wherever you checked it out to... then go back to the broker and the maven build should complete ok. Hope this helps, Rob > > I know I know total N00b questions, but as I said previously I've never > used Maven before and it's currently Black Magic to me :o] > > Cheers, > Frase > > > > On 16/03/14 15:09, Robbie Gemmell wrote: > >> Hi all, >> >> I have made changes for 'Option 2' so people can take a look, its >> available >> on this branch: >> https://svn.apache.org/repos/asf/qpid/branches/QPID-5610- >> maven3-build-qmf-tools >> >> The commits are all logged on >> https://issues.apache.org/jira/browse/QPID-5610 >> >> For the manual tests I elected to make another module with those as the >> main code. Rather than update the test shell scripts to do the equivalent >> (i.e point at the target dir) to what they were doing or add another >> assembly to package them all up so they could work anywhere, I took a >> different approach and added a helper profile to the module pom which can >> run a particular class from the test package on demand whether it was >> previously build or not. While I didn't like the idea of pointing the test >> scipts at the target dir, I did this as much to try it out as anything >> because I think we should be doing something similar with any client >> examples etc in the main tree, so we can always put the scripts back if >> required. See the README in qpid-qmf2-test for details. >> >> Version wise it is marked as 0.30-SNAPSHOT to reflect its 'coming in >> future' status, but I have made it use the 0.28-SNAPSHOT/trunk >> dependencies >> for now so it works with the current codebase. >> >> I have updated the README files somewhat to reflect the update, add >> details >> to how to build javadoc etc, but to summarise in case you want to play >> with >> it: >> >> Ensure you have the latest qpid-parent pom installed in your local repo (a >> temporary step until we start deploying it soon, so I didn't document this >> bit): >> svn co http://svn.apache.org/repos/asf/qpid/qpid-parent-pom/trunk <your >> chosen dir name> >> cd <your chosen dir name> >> mvn clean install >> >> Optionally, build the Java broker/client/etc and install them in your >> local >> repo. If you don't, the QMF2 tools build will just use the artefacts from >> the snapshots repo: >> cd <qpid trunk checkout>/qpid/java/ >> mvn clean install -DskipTests=true -Denable=true >> >> Build the QMF2 broker plugin and tools: >> svn co >> http://svn.apache.org/repos/asf/qpid/branches/QPID-5610- >> maven3-build-qmf-tools/<your >> chosen dir name> >> cd <your chosen dir name>/qpid/tools/src/java >> mvn clean package >> >> You will now have the jars, the tools assembly which you can extract and >> use the tools/gui, and a broker plugin assembly which you can extract and >> install in a broker release (that assembly was optionally created earlier >> in qpid/java/broker/target) as per the instructions. >> >> Robbie. >> >> On 13 March 2014 21:36, Robbie Gemmell <robbie.gemm...@gmail.com> wrote: >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org > For additional commands, e-mail: users-h...@qpid.apache.org > >
