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 36922

Summary:	There should be a way how to make a module work with winsys1 and winsys2 at once
Product:	platform	Reporter:	Jaroslav Tulach <jtulach>
Component:	Window System	Assignee:	mslama <mslama>
Status:	VERIFIED WONTFIX
Severity:	blocker	CC:	pzavadsky
Priority:	P4
Version:	3.x
Hardware:	PC
OS:	Linux
Issue Type:	DEFECT	Exception Reporter:
Bug Depends on:
Bug Blocks:	36122

Description Jaroslav Tulach 2003-10-30 07:37:53 UTC

Often our external integrators are ready to adopt
a module to work well with two or more versions of
NetBeans. Then they get really upset if such
effort is not possible. That is why there should
be a documented way how to make one module (or
more modules) working well with old window system
and with new one. 

This includes some kind of support for
specification of layout of components in Windows/
as well as Windows2/

Comment 1 mslama 2003-11-05 09:39:28 UTC

It can work well when module defines the same set of TopComponents
(settings files) in both old and new configuration. If there is some
component in old configuration which is not defined in new
configuration there is currently no way how to detect that this
component should not be imported. Is such limitation acceptable? If
yes then it is ok to define old and new winsys configuration in new
module.

Comment 2 Jaroslav Tulach 2003-11-05 10:36:57 UTC

Defining components in both layouts is acceptable limitation in my
opinion.

Comment 3 mslama 2003-11-05 10:49:50 UTC

Actualy limitation is not so strict. Components defined in old
configuration must be subset of components defined in new
configuration. In other words if component is defined in old
configuration then it must be defined in new configuration. (New
configuration can define more components than old configuration.)

Comment 4 Milos Kleint 2004-09-29 15:20:47 UTC

this is IMHO invalid.
rather then having a module to work with 2 distinct version of the IDE
out of the box, it's better and more maintainable to have 2 distinct
version of the modules.

people working with the platform will always fix their product to a
giveen platform version, possibly doing a complete upgrade from time
to time.

Yarda, do you have a usecase where it's causing trouble to roll out 2
version of the module?

Closing as won't fix, please reopen if you disagree.

Comment 5 Jaroslav Tulach 2004-09-30 07:45:32 UTC

A bit too late, I am affraid. This was needed for modules to run in
3.5 and 3.6.

Comment 6 Marian Mirilovic 2005-07-12 10:02:32 UTC

closed