wrong file types in Jazz source control properties
Hello
I just discovered that some of our Java source files (ending .java) have
the "application/binary" MIME type in the "Jazz source control"
properties tab. I do not (yet) know how this could happen or when it
happened. I thought of changing it into "text/plain". I've run a search
all over the workspace to find all textual files (*.java, *.xml, *.mf,
*.txt). In the search result, I can mark all files and select
"Team"->"Change file properties".
Is it a good idea to bulk change the file type for all those files in
one big action? Is there the risk to lose history, the file
accessibility or something else? Or is it highly recommended to perform
this action in order to boost Jazz performance and allow Jazz SCM to
deal with the text files in a proper manner?
Worst case would be to lose data, corrupt the repo or to create the need
for a rollback.
Thanks,
Stefan
I just discovered that some of our Java source files (ending .java) have
the "application/binary" MIME type in the "Jazz source control"
properties tab. I do not (yet) know how this could happen or when it
happened. I thought of changing it into "text/plain". I've run a search
all over the workspace to find all textual files (*.java, *.xml, *.mf,
*.txt). In the search result, I can mark all files and select
"Team"->"Change file properties".
Is it a good idea to bulk change the file type for all those files in
one big action? Is there the risk to lose history, the file
accessibility or something else? Or is it highly recommended to perform
this action in order to boost Jazz performance and allow Jazz SCM to
deal with the text files in a proper manner?
Worst case would be to lose data, corrupt the repo or to create the need
for a rollback.
Thanks,
Stefan
2 answers
Stefan Stern wrote:
After we developed the feature, we switched over our MIME types and
encodings in a similar manner. You should not be at risk of corrupting
any of your repository data or history.
JohnC
SCM Server
Hello
I just discovered that some of our Java source files (ending .java) have
the "application/binary" MIME type in the "Jazz source control"
properties tab. I do not (yet) know how this could happen or when it
happened. I thought of changing it into "text/plain". I've run a search
all over the workspace to find all textual files (*.java, *.xml, *.mf,
*.txt). In the search result, I can mark all files and select
"Team"->"Change file properties".
Is it a good idea to bulk change the file type for all those files in
one big action? Is there the risk to lose history, the file
accessibility or something else? Or is it highly recommended to perform
this action in order to boost Jazz performance and allow Jazz SCM to
deal with the text files in a proper manner?
Worst case would be to lose data, corrupt the repo or to create the need
for a rollback.
After we developed the feature, we switched over our MIME types and
encodings in a similar manner. You should not be at risk of corrupting
any of your repository data or history.
JohnC
SCM Server
There are two main properties of interest in the properties page, the mime type and the line delimiter. The mime type is used to help decide which merger to use for content merging, but it's not the only thing we also use the content type registry, and the line delimiter for text files allows teams on different platform to harmonize line endings in the repository (eg, we convert on check-in and on load to what you specify).
By default new resources get default values, but this was only added later after beta2. You can bulk update these values without any fear of data loss. We check that if you want delimiters of Platform and during the conversion we find inconsistent line endings we stop.
Jean-Michel
Jazz Source Control Team
By default new resources get default values, but this was only added later after beta2. You can bulk update these values without any fear of data loss. We check that if you want delimiters of Platform and during the conversion we find inconsistent line endings we stop.
Jean-Michel
Jazz Source Control Team