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.
************************************************** * This issue is tracked in Bugster as CR 6777516 * ************************************************** < PATCH REQUEST > < PROBLEM DESCRIPTION > NetBeans Treats xsd/xsl files as Binary – when importing into subversion < STEPS TO REPRODUCE > 1.Create a project in NetBeans. 2.either create an XSD/XSL file or import some into the project in step 1. 3.right click on the project 4.on the pop up menu go to Versioning --> Import into SubVersion Repository 5.When you get to the files to import screen 6.The commit Action for XSDs will be Add as Binary as default < ESR LEVEL > Java CAPS 6 < WORKAROUNDS AND REJECTION REASON > The work around is to manually change the Commit Action to Text. < DATE REQUIRED & BUSINESS CASE > < CUSTOMER INFO > Telecom NZ <CRITERIA > Criteria #3: Making development painful – Yes Criteria #4: Making testing painful (including migration issues) -Yes *** (#1 of 1): 2008-11-28 05:34:34 CET vince.chau@sun.com
There is fix for customers that use NB 6.1. The fix is only for NB 6.1, the problem is not reproducible in NB 6.5 (MIME type registration was rewritten in NB 6.5). This issue will be delivered as part of 6.1 patch 5.
> the problem is not reproducible in NB 6.5 means it is FIXED. doesn't it?
It is fixed in NB 6.5, but this issue was created for the escalation from the customer that still uses NB 6.1. So the fix will be provided to the customer for NB 6.1, but the fix will NOT be propagated into NB 6.5, of course.
does this also mean that when we fix an issue we keep it open (or reopen them eventually) until they are integrated into all previous releases they are supposed to be integrated into? And how does this go together with http://wiki.netbeans.org/IssueLifeCycle#section-IssueLifeCycle-EvaluatingIssues ? maybe i understand something wrong, but as long an issue is reported against the subversion module in 6.1 and not reproducible in 6.5 i consider it as fixed or worksforme. is there no other channel to keep track about issues like this? It is polluting our dashboard for 7.0 and is a source of confusion as we have bugcounts to meet for M1 etc. please, consult this with the dashboard team or keep it at least as incomplete
Reopening, marking as INCOMPLETE not to confuse developers. This issue is just for tracking escalation already stored in Bugster, Apollo, and internal JCAPS ecalation db.
Replacing keywords. The issue report is not incomplete, but does not apply to NB 6.5 and 7.0.
The issue has been fixed in the release61_fixes branch http://hg.netbeans.org/release61_fixes/rev/ceff35501dbc
Verified.