Community
Participate
Working Groups
Technically, this doesn't cause any problems ... other than making it hard to find them with 'search' functions. And, kind of a hassle to fix/change the module names ... but, I think it should be done at some time. It should be transparent to consumers, since the names are correct in the MANIFEST.MF files ... so, could be scheduled when there was no pressure to produce a build under deadline, etc.
Hmmm, they seem to be correct in cvs, after all ... I think ... but noticed the HEAD version had "apacha" in the .project file ... which, some how, was causing all branches to be to be checked out in my workspace with "apacha" instead of "apache". This ... I think ... interacted with the tools in some strange way, to cause the first branch 3_1_1 not to be tagged/structured correctly? During a build, it had this in the log: 115739 [orbit-set1] FetchFromCVS: 115740 [orbit-set1] [CVS - org.apache.hadoop.zookeeper_3.3.1] cvs export: No CVSROOT specified! Please use the `-d' option 115741 [orbit-set1] [CVS - org.apache.hadoop.zookeeper_3.3.1] cvs [export aborted]: or set the CVSROOT environment variable. Where as for others, such as 3.3.2 branch, had this: 115743 [orbit-set1] FetchFromCVS: 115744 [orbit-set1] [CVS - org.eclipse.orbit/org.apache.hadoop.zookeeper] cvs export: CVSROOT must be an absolute pathname (not `') 115745 [orbit-set1] [CVS - org.eclipse.orbit/org.apache.hadoop.zookeeper] cvs export: when using local access method. 115746 [orbit-set1] [CVS - org.eclipse.orbit/org.apache.hadoop.zookeeper] cvs export: warning: skipping invalid entry in password file at line 1 115747 [orbit-set1] [CVS - org.eclipse.orbit/org.apache.hadoop.zookeeper] cvs export: Updating org.apache.hadoop.zookeeper_3.3.2 115748 [orbit-set1] [CVS - org.eclipse.orbit/org.apache.hadoop.zookeeper] U org.apache.hadoop.zookeeper_3.3.2/.classpath 115749 [orbit-set1] [CVS - org.eclipse.orbit/org.apache.hadoop.zookeeper] U org.apache.hadoop.zookeeper_3.3.2/.project 115750 [orbit-set1] [CVS - org.eclipse.orbit/org.apache.hadoop.zookeeper] U org.apache.hadoop.zookeeper_3.3.2/about.html So ... bottom line, I fixed "apacha" in the HEAD .project file, committed that, then deleted what was in my workspace, checked out again ... this time with the name "apache" in my local module name ... and then retagged and we'll see how the next build goes ... But, I'm assuming this is now "fixed" by virtue of fixing the .project file in HEAD.
Still got same build-time error, so will re-open. I'm going to try temporarily removing the 3.3.1 and 3.3.2 versions from feature and see is rest builds with just 3.3.3 in feature, and if so, will work from there.
It seemed to build ok with only 3.3.3, so will next try also adding 3.3.2 ... probably only a problem with 3.3.1 ... that's a pretty weird message; 115740 [orbit-set1] [CVS - org.apache.hadoop.zookeeper_3.3.1] cvs export: No CVSROOT specified! Please use the `-d' option Maybe I messed up just that one branch with the "apacha" name issue? But will try and set it right. ... At worse, maybe revert to what versions was being used with "missing provider names" ... since doubt anyone is using that "old" version in practice? Guess I never did say, here, I was tagging while trying to fix issues with "provider" and "bundleName" as discussed in bug 346305.
Turns out, the odd cvs export problem was just do to a typo I'd made in the map file ... dropped a comma after the version and ":pserver" ... so, I'm confident next build will be ok (tested it locally) and the problem with "apacha" was only with the .project file ... and just confused me. But now that's fixed too.
