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 27157 - Workspace is not added on platform when adding module using Tools->Options
Summary: Workspace is not added on platform when adding module using Tools->Options
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 3.x
Hardware: All All
: P2 blocker (vote)
Assignee: mslama
Depends on:
Blocks: 26338
  Show dependency tree
Reported: 2002-09-10 10:41 UTC by mslama
Modified: 2008-12-23 09:32 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Testing module (19.55 KB, application/octet-stream)
2002-09-10 10:42 UTC, mslama

Note You need to log in before you can comment on or make changes to this bug.
Description mslama 2002-09-10 10:41:42 UTC
Strange behaviour. When module is copied before
start to modules directory workspace is added both
in IDE and platform. When module is added using
Tools->Options->System->Modules->Add Module
workspace is added in IDE but NOT in platform.

Platform build is done using "ant -Dmodules="

Current dev build, JDK 1.4.1 b20, Linux.
Comment 1 mslama 2002-09-10 10:42:42 UTC
Created attachment 7360 [details]
Testing module
Comment 2 mslama 2002-09-10 12:33:31 UTC
Due to handling of project switch all data systems events are ignored
when project is not opened. However in case of platform there is no
project -> flag is not set -> all changes on winsys layers are
ignored. We need to detect such state (no project in system) and not
to check isProjectOpen() in such case. Vita is there any way how to do
Comment 3 mslama 2002-09-11 11:06:51 UTC
Fixed in main trunk.

core/src/org/netbeans/core/windows/ r.1.149
core/src/org/netbeans/core/windows/layers/ r.1.14

Listening on changes now works when projects module is not installed
or when projects module was installed but no project was opened yet or
when projects module is disabled.
Comment 4 JM Delsaux 2002-09-12 15:06:02 UTC
I've got the same problem and find a solution:

    -> remove mymodule.xml if needed

    -> remove mycomponent.settings if needed
    -> remove myWorkspace.wswksp_hidden
I don't remember exactly the extension for the workspace 
but there was a _hidden
After that, i can reinstall my module :-))
Comment 5 mslama 2002-09-12 15:50:01 UTC
JM I do not think your problem was the same. _hidden file for
workspace should not be created. Do you know how did it happen? If
your problem is reproducible please file new issue.
Comment 6 Marian Mirilovic 2002-10-11 14:38:43 UTC
OS/Platform independent issue.
Comment 7 Marian Mirilovic 2004-03-01 08:53:43 UTC
issue doesn't apply to new window system - verified