I'm trying to upload my project to clearcase repository using the eclipse plugin, but I'm having problems with jquery file, the minified version, jquery-1.7.min.js. When I try to upload it this is the error:
我正在尝试使用eclipse插件将我的项目上载到clearcase存储库，但是我遇到了jquery文件的问题。当我尝试上传它时，这是错误的:
text_file_delta: Error: "/tmp/ccrctemp/tmp12564" is not a 'text file': it contains a line exceeding 8000 bytes. Use a different type manager (such as compressed file).
text_file_delta: Error:“/tmp/ccrctemp/tmp12564”不是一个“文本文件”:它包含超过8000字节的行。使用不同的类型管理器(例如压缩文件)。
I guess that "/tmp/ccrctemp/tmp12564" is the jquery file. I've been looking for any solution on the Internet, but I only find solutions via command, I want to know how to solve it with eclipse plugin if there is any solution to this.
我猜“/tmp/ccrctemp/tmp12564”是jquery文件。我一直在互联网上寻找任何解决方案，但我只通过命令找到解决方案，我想知道如何使用eclipse插件解决它，如果有解决方案的话。
I'm using Rational ClearTeam Explorer 8.0.0
我使用的是Rational ClearTeam Explorer 8.0.0
Thanks in advance.
提前谢谢。
Greetings.
问候。
UPDATE
更新
I'm also having problems with empty files, Why I can´t upload empty files? Is there any way to upload it? I thought about modifying the file by typing a space, but maybe I need that empty file as it will be filled later.
我也用空的文件有问题,为什么我不能上传空文件´吗?有办法上传吗?我想通过输入空格来修改这个文件，但是也许我需要这个空文件，因为它稍后会被填充。
Greetings.
问候。
2 个解决方案
#1
1
If the issue is related to the type manager which doesn't interpret the content of that specific file as text, you can cahnge its type:
如果问题与类型管理器有关，而类型管理器不将特定文件的内容解释为文本，则可以强制执行其类型:
cleartool chtype compressed_file
See more with the IBM technote "Clearimport fails when importing text files that are seen as binary files into a VOB".
I detail this issue in "Clearcase issue while “add file to source control”".
请参阅IBM technote“在将文本文件作为二进制文件导入到VOB时发生的Clearimport失败”。我在“Clearcase问题”和“将文件添加到源代码控制”中详细说明了这个问题。
#2
-1
The file type is chosen/processed when the file is created. Once the file is created you can only change file type the cmd line tool. The most effective way of ensuring all file types are correct is by adding an entry to the ClearCase magic file (OK 2 entries) so the appropriate type is chosen when adding to source control.
在创建文件时选择/处理文件类型。创建文件后，只能更改cmd行工具的文件类型。确保所有文件类型正确的最有效方法是向ClearCase magic文件(OK 2个条目)添加一个条目，以便在添加到源代码控制时选择合适的类型。
minimized_javascript web_file script binary_delta_file : -printable & -name "*.[mM][iI][nN].[jJ][sS]";
minimized_javascript web_file script binary_delta_file : -name "*.[mM][iI][nN].[jJ][sS]" ;
These entries need to be processed AHEAD of the regular .js entries in the magic file when the file gets created.
当文件被创建时，这些条目需要在魔法文件中的常规.js条目前面进行处理。
If you are using ClearTeam Explorer and Web based views (CTE default), the changes need to made on the view server's magic file, not the local one.
如果您正在使用ClearTeam Explorer和基于Web的视图(CTE默认)，那么需要对视图服务器的魔法文件进行更改，而不是本地文件。
Magic file ? What's that? Well, Rational does a terrible job of explaining it, but it is a very powerful mechanism for managing how CC handles files. Feel free to read:
神奇的文件?那是什么?Rational在解释它时做得很糟糕，但是它是一个非常强大的机制来管理CC如何处理文件。请阅读:
About the ClearCase Magic file
关于ClearCase魔法文件
关于MAGIC_PATH变量
Evaluating multiple magic files
评估多个魔法文件
Unfortunately, IBM was never able to provide me a clear answer what should be in the custom magic file: just the custom lines and no closure line or the custom plus all the lines from the default. So, we changed our MAGIC_PATH to:
不幸的是，IBM从来没能给我一个清晰的答案，在自定义魔术文件中应该是什么:只有自定义行，没有闭包行或自定义加上默认的所有行。因此，我们将MAGIC_PATH更改为:
MAGIC_PATH=/cc_store/vobstg/vobstore/magic:/opt/rational/clearcase/config/magic
and added a copy w/custom lines ahead of the provided rules in the first path, which we called cc.magic. I suspect as long as you have no catch-all, it will process every *.magic path per the ordering rules until it finds a matching rule or catch-all.
并在第一个路径中，在提供的规则之前添加了一个w/custom行拷贝，我们称之为cc.magic。我怀疑，只要你没有抓住一切，它就会处理每一个*。每个排序规则都有一个神奇的路径，直到找到匹配的规则或全部。
They also failed to point out for the above to actually work in CC8 using CTE, you also need to modify the Websphere server file: /apps/infra/rational/SDLC/common/ccrcprofile/config/cells/dfltCell/nodes/dfltNode/servers/server1/server.xml
他们也没有指出，要使用CTE在CC8中工作，您还需要修改Websphere服务器文件:/apps/infra/rational/SDLC/common/ccrcprofile/config/cells/dfltCell/node /dfltNode/servers/server /server1/server.xml
<environment xmi:id="Property_1387399742135" name="MAGIC_PATH" value="/cc_store/vobstg/vobstore/magic:/opt/rational/clearcase/config/magic" description="Setting req'd so CCRC web views can access MAGIC_PATH" required="false"/>
It is documented that under CC7, you needed to change the files: /var/adm/rational/common/rwp/conf/ ccrcweb.conf and ccrc.conf But CC8 of course comes w/standalone Webshpere, so the files are no longer there.
有文件表明，在CC7下，您需要更改文件:/var/adm/rational/common/rwp/conf/ ccrcweb。conf和ccrc。conf但是CC8当然是w/ independent Webshpere，所以文件已经不在那里了。
Of course, if you got this far, you probably realize you need write access to the view server ClearCase install to change these settings, in which case you also have access to run the command line tool cleartool.
当然，如果您了解到这一点，您可能会意识到需要对视图服务器ClearCase安装进行写访问，以更改这些设置，在这种情况下，您还可以访问运行命令行工具cleartool。
And if you have command line access, here's a little command you can run against dynamic view to change all the files with the wrong settings:
如果你有命令行访问权限，这里有一个小命令，你可以运行在动态视图中，用错误的设置修改所有文件:
cleartool find * -type f -name "*.min.js" -element '! eltype(binary_delta_file)' -print |sed 's:@@::' | xargs -I {} cleartool chtype -force binary_delta_file {}
#1
1
If the issue is related to the type manager which doesn't interpret the content of that specific file as text, you can cahnge its type:
如果问题与类型管理器有关，而类型管理器不将特定文件的内容解释为文本，则可以强制执行其类型:
cleartool chtype compressed_file
See more with the IBM technote "Clearimport fails when importing text files that are seen as binary files into a VOB".
I detail this issue in "Clearcase issue while “add file to source control”".
请参阅IBM technote“在将文本文件作为二进制文件导入到VOB时发生的Clearimport失败”。我在“Clearcase问题”和“将文件添加到源代码控制”中详细说明了这个问题。
#2
-1
The file type is chosen/processed when the file is created. Once the file is created you can only change file type the cmd line tool. The most effective way of ensuring all file types are correct is by adding an entry to the ClearCase magic file (OK 2 entries) so the appropriate type is chosen when adding to source control.
在创建文件时选择/处理文件类型。创建文件后，只能更改cmd行工具的文件类型。确保所有文件类型正确的最有效方法是向ClearCase magic文件(OK 2个条目)添加一个条目，以便在添加到源代码控制时选择合适的类型。
minimized_javascript web_file script binary_delta_file : -printable & -name "*.[mM][iI][nN].[jJ][sS]";
minimized_javascript web_file script binary_delta_file : -name "*.[mM][iI][nN].[jJ][sS]" ;
These entries need to be processed AHEAD of the regular .js entries in the magic file when the file gets created.
当文件被创建时，这些条目需要在魔法文件中的常规.js条目前面进行处理。
If you are using ClearTeam Explorer and Web based views (CTE default), the changes need to made on the view server's magic file, not the local one.
如果您正在使用ClearTeam Explorer和基于Web的视图(CTE默认)，那么需要对视图服务器的魔法文件进行更改，而不是本地文件。
Magic file ? What's that? Well, Rational does a terrible job of explaining it, but it is a very powerful mechanism for managing how CC handles files. Feel free to read:
神奇的文件?那是什么?Rational在解释它时做得很糟糕，但是它是一个非常强大的机制来管理CC如何处理文件。请阅读:
About the ClearCase Magic file
关于ClearCase魔法文件
关于MAGIC_PATH变量
Evaluating multiple magic files
评估多个魔法文件
Unfortunately, IBM was never able to provide me a clear answer what should be in the custom magic file: just the custom lines and no closure line or the custom plus all the lines from the default. So, we changed our MAGIC_PATH to:
不幸的是，IBM从来没能给我一个清晰的答案，在自定义魔术文件中应该是什么:只有自定义行，没有闭包行或自定义加上默认的所有行。因此，我们将MAGIC_PATH更改为:
MAGIC_PATH=/cc_store/vobstg/vobstore/magic:/opt/rational/clearcase/config/magic
and added a copy w/custom lines ahead of the provided rules in the first path, which we called cc.magic. I suspect as long as you have no catch-all, it will process every *.magic path per the ordering rules until it finds a matching rule or catch-all.
并在第一个路径中，在提供的规则之前添加了一个w/custom行拷贝，我们称之为cc.magic。我怀疑，只要你没有抓住一切，它就会处理每一个*。每个排序规则都有一个神奇的路径，直到找到匹配的规则或全部。
They also failed to point out for the above to actually work in CC8 using CTE, you also need to modify the Websphere server file: /apps/infra/rational/SDLC/common/ccrcprofile/config/cells/dfltCell/nodes/dfltNode/servers/server1/server.xml
他们也没有指出，要使用CTE在CC8中工作，您还需要修改Websphere服务器文件:/apps/infra/rational/SDLC/common/ccrcprofile/config/cells/dfltCell/node /dfltNode/servers/server /server1/server.xml
<environment xmi:id="Property_1387399742135" name="MAGIC_PATH" value="/cc_store/vobstg/vobstore/magic:/opt/rational/clearcase/config/magic" description="Setting req'd so CCRC web views can access MAGIC_PATH" required="false"/>
It is documented that under CC7, you needed to change the files: /var/adm/rational/common/rwp/conf/ ccrcweb.conf and ccrc.conf But CC8 of course comes w/standalone Webshpere, so the files are no longer there.
有文件表明，在CC7下，您需要更改文件:/var/adm/rational/common/rwp/conf/ ccrcweb。conf和ccrc。conf但是CC8当然是w/ independent Webshpere，所以文件已经不在那里了。
Of course, if you got this far, you probably realize you need write access to the view server ClearCase install to change these settings, in which case you also have access to run the command line tool cleartool.
当然，如果您了解到这一点，您可能会意识到需要对视图服务器ClearCase安装进行写访问，以更改这些设置，在这种情况下，您还可以访问运行命令行工具cleartool。
And if you have command line access, here's a little command you can run against dynamic view to change all the files with the wrong settings:
如果你有命令行访问权限，这里有一个小命令，你可以运行在动态视图中，用错误的设置修改所有文件:
cleartool find * -type f -name "*.min.js" -element '! eltype(binary_delta_file)' -print |sed 's:@@::' | xargs -I {} cleartool chtype -force binary_delta_file {}