So in this case it means I need to use command line svn to do checkout not Eclipse built-in SVN browser as I could not figure out how to check out parent direcotry in it (I may be missing an option for it)
In my opinion it would be better user/developer experience ot be able to check out projects from SVN in Eclispe - do we really need to have ws-messaging parent? Moreover message box is an independent service from message broker (it really is just a simple persistent event consumer with API to retrieve stored events) Thanks, Alek On Sat, Jul 16, 2011 at 10:52 PM, Suresh Marru <[email protected]>wrote: > On Jul 16, 2011, at 8:31 PM, Lahiru Gunathilake wrote: > > > Hi Alek, > > > > airavata/ws-messenger is considered as a single project so if you want to > > build airavata/ws-messenger/messagebox you need to checkout > > airavata/ws-messenger and try to build with it. In airavata/ws-messenger > is > > having different build profiles, you can simply invoke > > mvn clean install -Dmodule=messagebox > > Yes thats right. As of now WS-Messenger is the parent for the three > sub-components. But very soon we want to get a place where Airavata will be > the parent and everything else will be modules. > > From within the ws-messenger, message box can also be built as: mvn clean > install -f messagebox/pom.xml > > Suresh > > > > > > This will build only messagebox but still you need ws-messenger parent > pom > > to be there in your project. > > > > Regards > > Lahiru > > > > On Sat, Jul 16, 2011 at 3:18 PM, Alek Slominski (Apache) > > <[email protected]>wrote: > > > >> Hi, > >> > >> I had no problems with building XBaya in Eclipse but I am having > problems > >> with MessageBox > >> > >> pom.xml has this problem: Project build error: Non-resolvable parent > POM: > >> Could not find artifact Airavata:ws-messenger:pom:0.0.**1-SNAPSHOT and > >> 'parent.relativePath' points at wrong local POM > >> > >> does it mean that I need to do some special checkout from SVN to keep > >> parent directory? Is that documented somewhere? > >> > >> Thanks, > >> > >> Alek > >> > >> > >> > >
