On Friday, December 9, 2011, Amila Maha Arachchi <[email protected]> wrote: > I dont know why this error occurs (i mean why the carbon-platform pom is missing in the repo). But to get rid of this, you can build from the root, commenting out all the modules (i.e. theres nothing to be built actually). When the build completes, maven copies the platform pom to the .m2 repo. Then onwards, this error will not occur.
Yep. I thought Samisa already did that :) Even after doing that, you have to remove the said two files. Unless Maven3 does not recognize this pom even though it's in the repo. That's quite strange! --KasunG > > <profile> > <id>default</id> > <activation> > <activeByDefault>true</activeByDefault> > </activation> > <modules> > <!--<module>dependencies</module> > <module>orbit</module> > <module>service-stubs</module> > <module>core</module> > <module>components</module> > <module>features</module> > <module>samples/shopping-cart</module> > <module>products</module>--> > </modules> > </profile> > > > Thanks, > AmilaM. > > On Thu, Dec 8, 2011 at 8:48 AM, KasunG Gajasinghe <[email protected]> wrote: >> >> >> On Friday, December 9, 2011, Samisa Abeysinghe <[email protected]> wrote: >> > >> > >> > On Wed, Dec 7, 2011 at 6:32 PM, Kishanthan Thangarajah < [email protected]> wrote: >> >> >> >> Hi, >> >> On Wed, Dec 7, 2011 at 3:08 PM, Samisa Abeysinghe <[email protected]> wrote: >> >>> >> >>> service stubs fails parsing the pom >> >> >> >> I think the issue is not with parsing the pom, but the parent pom is missing in the repo. >> >> I also faced this issue, and i had to build the trunk (for service-stubs) from root level to get the parent pom to the repo. >> > >> > I built from root, yet it does not work. >> >> I see. Then this happened probably due to some unnecessary files residing in m2 repo. Can you go to the directory that's supposed to contain carbon root pom (carbon-platform), and remove these two files. <something>.pom.lastUpdated, and resolved_status.properties? Then try again. >> >> These are generated when trying to build from a sub-project, and does not get removed even when we build from root. IMO that is not a bug in wso2 rather in maven3. >> >> Thanks, >> -KasunG >> >> > >> > >> > Thanks, >> > >> > >> > E:\svn\carbon_trunk\service-stubs>e:\dev_tools\apache-maven-3.0.3\bin\mvn clean install -Dmaven.test.skip=true >> > [INFO] Scanning for projects... >> > [ERROR] The build could not read 156 projects -> [Help 1] >> > [ERROR] >> > [ERROR] The project org.wso2.carbon:org.wso2.carbon.stratos.common.stub:3.2.0-SNAPSHOT (E:\svn\carbon_trunk\service-stubs\org.wso2.carbon.stratos.common.stub\pom.xml) has 1 error >> > [ERROR] Non-resolvable parent POM for org.wso2.carbon:service-stubs:3.2.0-SNAPSHOT: Could not find artifact org.wso2.carbon:carbon-platform:pom:3.2.0-SNAPSHOT @ org.wso2.carbon:service-st >> > ubs:3.2.0-SNAPSHOT, C:\Users\Samisa Abeysinghe\.m2\repository\org\wso2\carbon\service-stubs\3.2.0-SNAPSHOT\service-stubs-3.2.0-SNAPSHOT.pom, line 20, column 13 -> [Help 2] >> > [ERROR] >> > [ERROR] The project org.wso2.carbon:org.wso2.carbon.tenant.register.gapp.stub:3.2.0-SNAPSHOT (E:\svn\carbon_trunk\service-stubs\org.wso2.carbon.tenant.register.gapp.stub\pom.xml) has 1 erro >> > r >> > [ERROR] Non-resolvable parent POM for org.wso2.carbon:service-stubs:3.2.0-SNAPSHOT: Could not find artifact org.wso2.carbon:carbon-platform:pom:3.2.0-SNAPSHOT @ org.wso2.carbon:service-st >> > ubs:3.2.0-SNAPSHOT, C:\Users\Samisa Abeysinghe\.m2\repository\org\wso2\carbon\service-stubs\3.2.0-SNAPSHOT\service-stubs-3.2.0-SNAPSHOT.pom, line 20, column 13 -> [Help 2] >> > [ERROR] >> > and loads of the, >> > On Wed, Dec 7, 2011 at 3:02 PM, Shelan Perera <[email protected]> wrote: >> > >> > >> > On Wed, Dec 7, 2011 at 2:57 PM, Harshana Martin <[email protected]> wrote: >> > >> > >> > On Wed, Dec 7, 2011 at 2:56 PM, Tharindu Mathew <[email protected]> wrote: >> > >> > Shindig needs to build with tests... >> > Are you building with tests? >> > >> > Yes. It failed with/without tests at the same place. >> > >> > It was successful when you build with tests for me. There were two occasions where we needed to run tests to proceed due to test jars.I hope that should be avoided in a >> > clean source (avoid test dependency). >> > Thanks >> > >> > >> > Thanks. >> > /Harshana >> > >> > On Wed, Dec 7, 2011 at 2:51 PM, Harshana Martin <[email protected]> wrote: >> > >> > >> > On Wed, Dec 7, 2011 at 2:49 PM, Samisa Abeysinghe <[email protected]> wrote: >> > >> > Sorry false alarm. Axis2 builds. Now Shinding. >> > [ERROR] Failed to execute goal on project shindig-extras: Could not resolve dependencies for project org.apache.shindig:shindig-extras:jar:3.0.0-SNAPSHOT: Could not find artifact org.apache.s >> > hindig:shindig-social-api:jar:tests:3.0.0-SNAPSHOT in diff_match_patch (http://google-diff-match-patch.googlecode.co >> _______________________________________________ >> Carbon-dev mailing list >> [email protected] >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> > >
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
