The Qpid 0.9 jars are now hosted on our Maven2 repo so that you do not need to build them.
Danushka On Sat, Dec 18, 2010 at 9:37 PM, Kathiravelu Pradeeban <pradee...@wso2.com>wrote: > Guess you meant, we have to checkout [1] and build Qpid [2] using ant. > > [1] http://svn.apache.org/repos/asf/qpid/trunk/qpid/ > [2] http://qpid.apache.org/download.cgi > > Thanks, > Pradeeban. > > > On Sat, Dec 18, 2010 at 8:24 PM, Kathiravelu Pradeeban <pradee...@wso2.com > > wrote: > >> >> >> On Wed, Dec 15, 2010 at 10:44 AM, Danushka Menikkumbura < >> danus...@wso2.com> wrote: >> >>> The latest Qpid artifacts are not hosted on a repo. Even the Qpid repo >>> does not have the latest ones. You need to build Qpid locally (it has an ant >>> build) and install artifacts into your local repo using maven until we host >>> them on our maven repo. >>> >>> I am also hit with the same issue when trying to build orbit. Build fails >> in orbit/qpid. I am unable to locate any ant builds on orbit/qpid or orbit >> either. Did I miss something? >> >> Regards, >> Pradeeban. >> >> Danushka >>> >>> On Wed, Dec 15, 2010 at 9:55 AM, Manjula Rathnayake >>> <manju...@wso2.com>wrote: >>> >>>> Hi all, >>>> >>>> I am trying to build qpid component in trunk. And I build online but >>>> still artifacts are not resolved. >>>> Following is the repositories in orbit/pom.xml >>>> >>>> <repositories> >>>> <repository> >>>> <id>wso2-maven2-snapshot-repository</id> >>>> <name>WSO2 Maven2 SNAPSHOTS</name> >>>> <url>http://dist.wso2.org/snapshots/maven2</url> >>>> <snapshots> >>>> <enabled>true</enabled> >>>> <updatePolicy>always</updatePolicy> >>>> <checksumPolicy>ignore</checksumPolicy> >>>> </snapshots> >>>> <releases> >>>> <enabled>false</enabled> >>>> </releases> >>>> </repository> >>>> <repository> >>>> <id>wso2-maven2-repository</id> >>>> <name>WSO2 Maven2 Repository</name> >>>> <url>http://dist.wso2.org/maven2</url> >>>> <snapshots> >>>> <enabled>false</enabled> >>>> </snapshots> >>>> <releases> >>>> <enabled>true</enabled> >>>> <updatePolicy>never</updatePolicy> >>>> <checksumPolicy>fail</checksumPolicy> >>>> </releases> >>>> </repository> >>>> <repository> >>>> <id>jboss-maven-repository</id> >>>> <name>JBoss Maven Repository </name> >>>> <url> >>>> https://repository.jboss.org/nexus/content/groups/public/</url> >>>> </repository> >>>> </repositories> >>>> >>>> So do we have to update repository locations? or I am missing something >>>> here? >>>> >>>> >>>> Thank you. >>>> >>>> -- >>>> Manjula Rathnayaka >>>> Software Engineer >>>> WSO2, Inc. >>>> Mobile:+94 77 743 1987 >>>> >>>> _______________________________________________ >>>> Carbon-dev mailing list >>>> Carbon-dev@wso2.org >>>> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>> >>>> >>> >>> _______________________________________________ >>> Carbon-dev mailing list >>> Carbon-dev@wso2.org >>> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> >> >> >> -- >> Kathiravelu Pradeeban. >> Software Engineer. >> WSO2 Inc. >> >> Blog: [Llovizna] http://kkpradeeban.blogspot.com/ >> >> > > > -- > Kathiravelu Pradeeban. > Software Engineer. > WSO2 Inc. > > Blog: [Llovizna] http://kkpradeeban.blogspot.com/ > > > _______________________________________________ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev > >
_______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
