This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 41243 - [36cat] commit on .sh files does no keyword substitution
Summary: [36cat] commit on .sh files does no keyword substitution
Status: RESOLVED WONTFIX
Alias: None
Product: obsolete
Classification: Unclassified
Component: vcsgeneric (show other bugs)
Version: 3.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: Martin Entlicher
URL:
Keywords:
Depends on: 21458
Blocks:
  Show dependency tree
 
Reported: 2004-03-24 07:39 UTC by quintessence
Modified: 2004-09-17 13:07 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description quintessence 2004-03-24 07:39:04 UTC
[ JDK VERSION : J2SE 1.4.2_01 ]

A commit on files named *.sh does not lead to a keyword substitution.
It seems that for .sh files always -kb is used (even when I try to change this behaviour by explicitly setting it to -kvv).
The server side cvswrapper file is still ignored.
Comment 1 quintessence 2004-03-24 10:06:48 UTC
As I just stated on nbuser the problem seems to be the following:

The org/openide/filesystems/FileUtil.java defines a MIME-TYPE
application/x-shar for the file extension sh and the CVS client uses
this for binary file detection (and shar is a binary).

As far as I have seen the source (and that is alltogether for about
the last 3 hours) there should be a mime-resolver which uses some
local settings or even better the cvswrapper file. 

Sorry, but even if I burn to code it, I do not have the time to do it
(as I stated my code knowledge of nb before)
Comment 2 Martin Entlicher 2004-03-31 13:12:27 UTC
There needs to be done something about the way how MIME-TYPEs are
treated, the user should have a clear indication of what keyword
substitution is used for which files. There's already issue #21458,
that should solve similar problem. This usecase needs to be considered
as well.
Comment 3 Richard Gregor 2004-09-17 13:07:47 UTC
Hi,

becasue of mentioned enhancement I'm closing this as wontfix. Current
behaviour is as designed. I agree that it should be handled better.
This requiremnet wiil be satisfied through enhancement ASAP - I hope
in 4.1. Please use issue#21458 for further comments.