Re: [RESULT][VOTE] Rename Apache Connectors Framework to ManifoldCF
That sounds good, and it is great to finally see the project naming move towards a final form that can stand up to even the most rigorous challenge. Long live ManifoldCF! That said, we may still choose to informally refer to MCF or mcf, although we should of course promote the proper name, either as ManifoldCF or Apache ManifoldCF (or Apache Manifold Connectors Framework?), as often and widely as possible. Did we ever settle whether that long-form name with CF expanded was okay for descriptive purposes even if the official Apache project name is "Apache ManifoldCF"? -- Jack Krupansky -- From: "Karl Wright" Sent: Monday, October 04, 2010 9:56 AM To: Subject: Re: [RESULT][VOTE] Rename Apache Connectors Framework to ManifoldCF On reflection, I've actually decided to just use manifoldcf everywhere, just because that's least likely to run into problems in the long run. Karl On Sun, Oct 3, 2010 at 9:35 PM, Karl Wright wrote: I think using mcf in the package name and the names of the webapps will likely be fine. I'm less worried about everything else. Grant, any comments? Karl On Sun, Oct 3, 2010 at 8:58 PM, Jack Krupansky wrote: I'm okay with all of that, but with a question whether we can get away with using an abbreviation in "org.apache.mcf" as opposed to "org.apache.manifoldcf". And then, whether the graduated project would be at "http://mcf.apache.org"; or "http://manifoldcf.apache.org";. I have no idea whether there might be pushback higher up on that, but my inclination is to go ahead with using mcf. I'll defer to Karl as to whether he wants to verify our assumption through/with Grant/et al or just go ahead. -- Jack Krupansky -- From: "Karl Wright" Sent: Sunday, October 03, 2010 7:35 PM To: "connectors-dev" Subject: [RESULT][VOTE] Rename Apache Connectors Framework to ManifoldCF The vote passes. Barely. Total count +1. Although I believe we didn't hear from lots of folks that made ManifoldCF their #1 choice last time. So, our new name is ManifoldCF. I'm thinking this will translate to: org.apache.mcf MCFException MCF abbreviation ManifoldCF full name webapps mcf-crawler-ui, mcf-authority-service, mcf-api-service ... and I can begin to change the tree around probably by tomorrow morning. Sound okay to everyone? Karl
Fw: svn commit: r1004504 - in /incubator/lcf/trunk/modules/framework/scripts: executecommand.bat executecommand.sh setclasspath.bat setdefine.bat
Should be MANIFOLDCF_HOME to be consistent with other project name usage? -- Jack Krupansky -- From: Sent: Monday, October 04, 2010 9:42 PM To: Subject: svn commit: r1004504 - in /incubator/lcf/trunk/modules/framework/scripts: executecommand.bat executecommand.sh setclasspath.bat setdefine.bat Author: kwright Date: Tue Oct 5 01:42:38 2010 New Revision: 1004504 URL: http://svn.apache.org/viewvc?rev=1004504&view=rev Log: Scripts should use MCF_HOME, not LCF_HOME Modified: incubator/lcf/trunk/modules/framework/scripts/executecommand.bat incubator/lcf/trunk/modules/framework/scripts/executecommand.sh incubator/lcf/trunk/modules/framework/scripts/setclasspath.bat incubator/lcf/trunk/modules/framework/scripts/setdefine.bat Modified: incubator/lcf/trunk/modules/framework/scripts/executecommand.bat URL: http://svn.apache.org/viewvc/incubator/lcf/trunk/modules/framework/scripts/executecommand.bat?rev=1004504&r1=1004503&r2=1004504&view=diff == --- incubator/lcf/trunk/modules/framework/scripts/executecommand.bat (original) +++ incubator/lcf/trunk/modules/framework/scripts/executecommand.bat Tue Oct 5 01:42:38 2010 @@ -1,22 +1,22 @@ @echo off -rem check that JAVA_HOME and LCF_HOME are set +rem check that JAVA_HOME and MCF_HOME are set if not exist "%JAVA_HOME%\bin\java.exe" goto nojavahome -if not exist "%LCF_HOME%\properties.xml" goto nolcfhome +if not exist "%MCF_HOME%\properties.xml" goto nolcfhome rem save existing path here set OLDDIR=%CD% -cd "%LCF_HOME%\processes" +cd "%MCF_HOME%\processes" set CLASSPATH=. for %%f in (jar/*) do call script\setclasspath.bat %%f set JAVADEFINES= for %%g in (define/*) do call script\setdefine.bat %%g rem restore old path here cd "%OLDDIR%" -"%JAVA_HOME%\bin\java" "-Dorg.apache.lcf.configfile=%LCF_HOME%\properties.xml" %JAVADEFINES% -classpath "%CLASSPATH%" %* +"%JAVA_HOME%\bin\java" "-Dorg.apache.manifoldcf.configfile=%MCF_HOME%\properties.xml" %JAVADEFINES% -classpath "%CLASSPATH%" %* goto done :nojavahome echo Environment variable JAVA_HOME is not set properly. goto done :nolcfhome -echo Environment variable LCF_HOME is not set properly. +echo Environment variable MCF_HOME is not set properly. goto done :done Modified: incubator/lcf/trunk/modules/framework/scripts/executecommand.sh URL: http://svn.apache.org/viewvc/incubator/lcf/trunk/modules/framework/scripts/executecommand.sh?rev=1004504&r1=1004503&r2=1004504&view=diff == --- incubator/lcf/trunk/modules/framework/scripts/executecommand.sh (original) +++ incubator/lcf/trunk/modules/framework/scripts/executecommand.sh Tue Oct 5 01:42:38 2010 @@ -8,23 +8,23 @@ fi #Make sure environment variables are properly set if [ -e "$JAVA_HOME"/bin/java ] ; then -if [ -f "$LCF_HOME"/properties.xml ] ; then +if [ -f "$MCF_HOME"/properties.xml ] ; then # Build the classpath CLASSPATH="" -for filename in $(ls -1 "$LCF_HOME"/processes/jar) ; do +for filename in $(ls -1 "$MCF_HOME"/processes/jar) ; do if [ -n "$CLASSPATH" ] ; then - CLASSPATH="$CLASSPATH""$PATHSEP""$LCF_HOME"/processes/jar/"$filename" + CLASSPATH="$CLASSPATH""$PATHSEP""$MCF_HOME"/processes/jar/"$filename" else -CLASSPATH="$LCF_HOME"/processes/jar/"$filename" +CLASSPATH="$MCF_HOME"/processes/jar/"$filename" fi done # Build the defines -DEFINES="-Dorg.apache.lcf.configfile=$LCF_HOME/properties.xml" -if [ -e "$LCF_HOME/processes/define" ] ; then -for filename in $(ls -1 "$LCF_HOME"/processes/define) ; do -DEFINEVAR=-D"$filename"=$(cat "$LCF_HOME"/processes/define/"$filename") + DEFINES="-Dorg.apache.manifoldcf.configfile=$MCF_HOME/properties.xml" +if [ -e "$MCF_HOME/processes/define" ] ; then +for filename in $(ls -1 "$MCF_HOME"/processes/define) ; do +DEFINEVAR=-D"$filename"=$(cat "$MCF_HOME"/processes/define/"$filename") DEFINES="$DEFINES $DEFINEVAR" done fi @@ -33,7 +33,7 @@ if [ -e "$JAVA_HOME"/bin/java ] ; then exit $? else -echo "Environment variable LCF_HOME is not properly set." 1>&2 +echo "Environment variable MCF_HOME is not properly set." 1>&2 exit 1 fi Modified: incubator/lcf/trunk/modules/framework/scripts/setclasspath.bat URL: http://svn.apache.org/viewvc/incubator/lcf/trunk/modules/framework/scripts/setclasspath.bat?rev=1004504&r1=1004503&r2=1004504&view=diff == --- incubator/lcf/trunk/modules/framework/scripts/setclasspath.bat (original) +++ incubator/lcf/trunk/modules/framework/scripts/setclasspath.bat Tue Oct 5 01:42:38 2010 @@ -1 +1 @@ -set CLASSPATH=%CLASS
Re: [RESULT][VOTE] Rename Apache Connectors Framework to ManifoldCF
On reflection, I've actually decided to just use manifoldcf everywhere, just because that's least likely to run into problems in the long run. Karl On Sun, Oct 3, 2010 at 9:35 PM, Karl Wright wrote: > I think using mcf in the package name and the names of the webapps > will likely be fine. I'm less worried about everything else. Grant, > any comments? > > Karl > > > On Sun, Oct 3, 2010 at 8:58 PM, Jack Krupansky > wrote: >> I'm okay with all of that, but with a question whether we can get away with >> using an abbreviation in "org.apache.mcf" as opposed to >> "org.apache.manifoldcf". And then, whether the graduated project would be at >> "http://mcf.apache.org"; or "http://manifoldcf.apache.org";. I have no idea >> whether there might be pushback higher up on that, but my inclination is to >> go ahead with using mcf. I'll defer to Karl as to whether he wants to verify >> our assumption through/with Grant/et al or just go ahead. >> >> -- Jack Krupansky >> >> -- >> From: "Karl Wright" >> Sent: Sunday, October 03, 2010 7:35 PM >> To: "connectors-dev" >> Subject: [RESULT][VOTE] Rename Apache Connectors Framework to ManifoldCF >> >>> The vote passes. Barely. Total count +1. Although I believe we >>> didn't hear from lots of folks that made ManifoldCF their #1 choice >>> last time. >>> >>> So, our new name is ManifoldCF. I'm thinking this will translate to: >>> >>> org.apache.mcf >>> MCFException >>> MCF abbreviation >>> ManifoldCF full name >>> webapps mcf-crawler-ui, mcf-authority-service, mcf-api-service >>> >>> >>> ... and I can begin to change the tree around probably by tomorrow >>> morning. Sound okay to everyone? >>> >>> Karl >> >> >
