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 26004 - CatalogSettings from XML catalog module is not public anymore
Summary: CatalogSettings from XML catalog module is not public anymore
Status: RESOLVED WONTFIX
Alias: None
Product: javaee
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: Milan Kuchtiak
URL:
Keywords:
Depends on: 22848
Blocks:
  Show dependency tree
 
Reported: 2002-07-25 10:00 UTC by _ rkubacki
Modified: 2016-07-07 08:53 UTC (History)
2 users (show)

See Also:
Issue Type: TASK
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 _ rkubacki 2002-07-25 10:00:16 UTC 
XML Catalog module doesn't allow to access other
classes than from spi package now. That's why CNFE
is thrown from instalation of web/advanced module.
Other way how to register our catalogs has to be
used. Petr can you recommend what is preffered
solution?
Comment 1 Milan Kuchtiak 2002-07-25 16:55:18 UTC 
Fixed in trunk.
Comment 2 _ rkubacki 2002-07-26 09:45:52 UTC 
The explicit dependency (org.netbeans.modules.xml.catalog/1 =
@BUILD_NUMBER_SUBST@) is only a workaround. Note that usually
web/advanced is build in a separate ant run so you will have to
specify -Dbuildnumber property to make this module compatible with
some IDE build.

Current approach blocks possible to publish module on autoupdate
because it doesn't make sense to publish something what works with
just one IDE build.
Comment 3 Milan Kuchtiak 2002-07-29 09:30:07 UTC 
I don't know exactly the mechanism how the autoupdate 
modules are being built. 
Unfortunately there is a strong dependancy on XML/catalog 
module, because there is no way how to install new XML 
catalog using f.e. layers. (see 22848).

Is there any way how to declare the dependancy on 
XML/catalog other then :

OpenIDE-Module-Module-Dependencies:
 org.netbeans.modules.xml.catalog/1 = @BUILD_NUMBER_SUBST@

This seems to be a bad idea - due to the special build 
proces for web/advanced module.

One solution is to move the proces of adding XML catalog 
from web/advanced to web/core module. But this seams not 
very nice as well.
Comment 4 Milan Kuchtiak 2002-07-29 10:20:02 UTC 
The package org.netbeans.modules.xml.catalog.settings was 
returned back to XML/catalog public pacages.

I am changing this to a Task with priority P3 depending on 
22848.

Adding XML catalog need to be changed in order to avoid the 
dependency on xml/catalog module.
Comment 5 _ lkramolis 2002-07-29 10:28:06 UTC 
You should not have problems to publish your module for NB 3.4
(release34 branch) because change in XML/Catalog was made in main
trunk (future release).

After discusion with Milan I have temporary published also
catalog.settings package, although I do not think you need it now.
Comment 6 Milan Kuchtiak 2002-09-09 09:23:10 UTC 
The work on this task will start after resolving 22848.
Comment 7 Martin Balin 2016-07-07 08:53:16 UTC 
This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue.

Thanks for your cooperation,
NetBeans IDE 8.2 Release Boss