Supun, Can you create a JIRA issue and attach these patches to it.
Thanks, Senaka. On Mon, Oct 18, 2010 at 12:47 PM, Supun Malinga <[email protected]> wrote: > Hi, > I have finished deploying almost all the artifacts, mentioned above. > > Currently I'm trying to build the carbon/products using above deployed > artifacts. > So Starting from a clean m2 repo, I built dependencies and orbit, and > started building each product, > > Below is a listing of the products I have successfully built and the small > changes I had to do to poms to get the build working. Further I have listed > the products I couldn't get built. > > 1) appserver - build successfull > > 2) bam - build successfull > > 3) bps > > > 4) brs - build successfull > > 5) ds - build successfull > attachment : ds_patch.txt > > 6) es > failed, cep feature has recent changes, will have to deploy it again and > build the product. > > 7) esb > failed due to: > org.wso2.carbon:org.apache.axis2.transports.jms.feature:zip:1.1.0-wso2v3 is > not a snapshot version, hence can't be deployed until the branching is > complete. > > 8) greg - build successfull > attachment: greg_patch.txt > > 9) gs > failed: can't find dependencies [1] > > 10) is - build successfull > attachment: is_patch.txt > > 11) ms - build successfull > attachment: ms_patch.txt > > > > [1] gs > [INFO] > ------------------------------------------------------------------------ > [ERROR] BUILD ERROR > [INFO] > ------------------------------------------------------------------------ > [INFO] Failed to resolve artifact. > > Missing: > ---------- > 1) org.wso2.carbon:org.wso2.carbon.validator:jar:3.1.0-SNAPSHOT > > Try downloading the file manually from the project website. > > Then, install it using the command: > mvn install:install-file -DgroupId=org.wso2.carbon > -DartifactId=org.wso2.carbon.validator -Dversion=3.1.0-SNAPSHOT > -Dpackaging=jar -Dfile=/path/to/file > > Alternatively, if you host your own repository you can deploy the file > there: > mvn deploy:deploy-file -DgroupId=org.wso2.carbon > -DartifactId=org.wso2.carbon.validator -Dversion=3.1.0-SNAPSHOT > -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] > > Path to dependency: > 1) org.wso2.gs:wso2gs:jar:2.0.0-SNAPSHOT > 2) org.wso2.carbon:org.wso2.carbon.validator:jar:3.1.0-SNAPSHOT > > 2) org.wso2.carbon:org.wso2.carbon.validator.ui:jar:3.1.0-SNAPSHOT > > Try downloading the file manually from the project website. > > Then, install it using the command: > mvn install:install-file -DgroupId=org.wso2.carbon > -DartifactId=org.wso2.carbon.validator.ui -Dversion=3.1.0-SNAPSHOT > -Dpackaging=jar -Dfile=/path/to/file > > Alternatively, if you host your own repository you can deploy the file > there: > mvn deploy:deploy-file -DgroupId=org.wso2.carbon > -DartifactId=org.wso2.carbon.validator.ui -Dversion=3.1.0-SNAPSHOT > -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] > > Path to dependency: > 1) org.wso2.gs:wso2gs:jar:2.0.0-SNAPSHOT > 2) org.wso2.carbon:org.wso2.carbon.validator.ui:jar:3.1.0-SNAPSHOT > > 3) org.wso2.carbon:org.wso2.carbon.wsdlconverter:jar:3.1.0-SNAPSHOT > > Try downloading the file manually from the project website. > > Then, install it using the command: > mvn install:install-file -DgroupId=org.wso2.carbon > -DartifactId=org.wso2.carbon.wsdlconverter -Dversion=3.1.0-SNAPSHOT > -Dpackaging=jar -Dfile=/path/to/file > > Alternatively, if you host your own repository you can deploy the file > there: > mvn deploy:deploy-file -DgroupId=org.wso2.carbon > -DartifactId=org.wso2.carbon.wsdlconverter -Dversion=3.1.0-SNAPSHOT > -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] > > Path to dependency: > 1) org.wso2.gs:wso2gs:jar:2.0.0-SNAPSHOT > 2) org.wso2.carbon:org.wso2.carbon.wsdlconverter:jar:3.1.0-SNAPSHOT > > 4) org.wso2.carbon:org.wso2.carbon.wsdlconverter.ui:jar:3.1.0-SNAPSHOT > > Try downloading the file manually from the project website. > > Then, install it using the command: > mvn install:install-file -DgroupId=org.wso2.carbon > -DartifactId=org.wso2.carbon.wsdlconverter.ui -Dversion=3.1.0-SNAPSHOT > -Dpackaging=jar -Dfile=/path/to/file > > Alternatively, if you host your own repository you can deploy the file > there: > mvn deploy:deploy-file -DgroupId=org.wso2.carbon > -DartifactId=org.wso2.carbon.wsdlconverter.ui -Dversion=3.1.0-SNAPSHOT > -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] > > Path to dependency: > 1) org.wso2.gs:wso2gs:jar:2.0.0-SNAPSHOT > 2) > org.wso2.carbon:org.wso2.carbon.wsdlconverter.ui:jar:3.1.0-SNAPSHOT > > ---------- > 4 required artifacts are missing. > > for artifact: > org.wso2.gs:wso2gs:jar:2.0.0-SNAPSHOT > > from the specified remote repositories: > wso2-maven2-snapshot-repository (http://dist.wso2.org/snapshots/maven2), > m2-snapshot-repository ( > http://people.apache.org/repo/m2-snapshot-repository), > central (http://repo1.maven.org/maven2), > wso2-maven2-repository (http://dist.wso2.org/maven2), > tomcat-repository (http://tomcat.apache.org/dev/dist/m2-repository), > ws-zones-repository (http://ws.zones.apache.org/repository2) > > > > > > On Mon, Oct 11, 2010 at 3:36 PM, Supun Malinga <[email protected]> wrote: > >> Hi, >> I'm working on the $subject. >> >> currently I deployed some artifacts from the latest carbon 3.1.0 branch. >> Due to the current ongoing release still some components havn't updated >> their poms, and having build errors(for error log see the attachment). Apart >> from that i could deploy snapshots for carbon core and components >> successfully. I will try deploying carbon features today. >> >> My next goal is to integrate this scenario to the automated build process. >> As I found out that current build scripts do have a deploy goal, i tried to >> initiate it, but I didn't notice any deployed artifacts from that. There is >> a logging mechanism from the scripts, but I'm a bit confused where exactly >> look for logs. >> Your suggestions of how often(eg: current plan is to weekly deploy the >> artifacts each Sunday) should the artifacts deployed and if I am to modify >> the current build script, how I am to do it safely without harming the >> current build process, will be helpful. >> >> Please give me feedback on your suggestions and improvements. >> >> Thanks and Regards, >> -- >> Supun Malinga, >> >> Software Engineer, >> WSO2 Inc. >> http://wso2.com >> http://wso2.org >> email - [email protected] >> mobile - 071 56 91 321 >> >> > > > -- > Supun Malinga, > > Software Engineer, > WSO2 Inc. > http://wso2.com > http://wso2.org > email - [email protected] <[email protected]> > > mobile - 071 56 91 321 > > > _______________________________________________ > Carbon-dev mailing list > [email protected] > https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- *Senaka Fernando* Associate Technical Lead & Product Manager - WSO2 G-Reg; WSO2, Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://www.linkedin.com/in/senakafernando *Lean . Enterprise . Middleware
_______________________________________________ Carbon-dev mailing list [email protected] https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
