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 50097 - explorer-override.wsmode xml file in a layer has wrong module section
Summary: explorer-override.wsmode xml file in a layer has wrong module section
Status: CLOSED FIXED
Alias: None
Product: projects
Classification: Unclassified
Component: Generic Projects UI (show other bugs)
Version: 4.x
Hardware: All All
: P3 blocker (vote)
Assignee: Petr Hrebejk
URL:
Keywords:
Depends on:
Blocks: 41535
  Show dependency tree
 
Reported: 2004-10-07 13:51 UTC by David Simonek
Modified: 2006-03-24 10:26 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description David Simonek 2004-10-07 13:51:57 UTC 
explorer-override.wsmode layer file contains
core/ui  module listed in its module info section,
which is incorrect, there should be projects/ui
module.

In addition Hrebejk found, that projects/ui module
doesn't have spec version at all, which may cause
troubles in future.

However in a case of wsmode file, spec version
isn't required, may be omitted.
Comment 1 Jesse Glick 2004-10-07 14:20:09 UTC 
Certainly we should have spec versions for all our modules.
Comment 2 Petr Hrebejk 2004-10-07 17:03:59 UTC 
Sure

Checking in projectui/manifest.mf;
/cvs/projects/projectui/manifest.mf,v  <--  manifest.mf
new revision: 1.3; previous revision: 1.2
done
Processing log script arguments...
More commits to come...
Checking in
projectui/src/org/netbeans/modules/project/ui/resources/explorer-override.wsmode;
/cvs/projects/projectui/src/org/netbeans/modules/project/ui/resources/explorer-override.wsmode,v
 <--  explorer-override.wsmode
new revision: 1.3; previous revision: 1.2
done
Comment 3 Marian Mirilovic 2005-12-20 15:48:22 UTC 
This issue was solved long time ago. Because nobody has reopened it neither
added comments, we are verifying/closing it now. 
If you are still able to reproduce the problem, please reopen. Thanks in advance.