I had to build endpoint.server.feature 4.1.1 in order to get the build done (which is wrong).
ESB folks, how do you build 4.1.2 in a clean repo? AFAIK, there cant be a released enpoint.server.feature 4.1.1 because no ESB was released with 4.1.1. You need to move this to 4.1.2 On Thu, May 2, 2013 at 6:32 PM, Amila Maha Arachchi <[email protected]> wrote: > Hi folks, > > I get the following error when I am building from the 4.1.2 patch release > pom. > > [INFO] > ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 18:02.519s > [INFO] Finished at: Thu May 02 17:26:04 IST 2013 > [INFO] Final Memory: 1238M/1987M > [INFO] > ------------------------------------------------------------------------ > [ERROR] Failed to execute goal on project > org.wso2.carbon.endpoint.feature: Could not resolve dependencies for > project org.wso2.carbon:org.wso2.carbon.endpoint.feature:pom:4.1.2: Could > not find artifact > org.wso2.carbon:org.wso2.carbon.endpoint.server.feature:zip:4.1.1 in > wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/) -> > [Help 1] > [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/DependencyResolutionException > [ERROR] > [ERROR] After correcting the problems, you can resume the build with the > command > [ERROR] mvn <goals> -rf :org.wso2.carbon.endpoint.feature > > I can see endpoint.server.feature 4.1.1 in the source. But it is not in > the patch-release pom (which is acceptable since it is a 4.1.1). But, then, > it should be available in the nexus repo (but it is not there). > > So, either the endpoint.server.feature has to be moved to 4.1.2 or 4.1.1 > feature should be deployed to nexus (but, I think we decided only to deploy > S2 related jars to nexus after the 4.1.1 release). > > Or, have I missed something? > > Regards, > AmilaM. > > -- > *Amila Maharachchi* > Technical Lead > Member, Management Committee - Cloud & Platform TG > WSO2, Inc.; http://wso2.com > > Blog: http://maharachchi.blogspot.com > Mobile: +94719371446 > > -- *Amila Maharachchi* Technical Lead Member, Management Committee - Cloud & Platform TG WSO2, Inc.; http://wso2.com Blog: http://maharachchi.blogspot.com Mobile: +94719371446
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
