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.
Users who want to work with schemas using a set of new schema tools, have to install Enterprise Pack. It has been decided that all schema related tools be moved from enterprise pack to base Netbeans. This will be a big benefit to the community.
Following xml/schema related modules are installed as a result of EntPack: Set A ===================== xml/catalogsupport,\ xml/graph,\ xml/nbprefuse,\ xml/prefuse,\ xml/refactoring,\ xml/schema/abe,\ xml/schema/core,\ xml/schema/refactoring,\ xml/schema/schemaui,\ xml/validation,\ xml/xamui,\ Set B ===================== xml/jxpath,\ xml/wsdl/refactoring,\ xml/wsdlext,\ xml/wsdlextui,\ xml/wsdlui,\ xml/xpath,\ xml/xsl/api In the first phase, modules in set A will be moved.
I propose that we create a separate cluster for all the xml tools related modules. Well, originally when these modules were introduced in NB5.5 EntPack, we used to have a separate cluster "xmltools1". This cluster will be part of standard Netbeans build and will contain the modules listed in set A.
Adding Chris and Nam to the interest list as well.
Please review and if there is no objections I would like to go ahead and commit these changes by 05-20/21. Here are the diff patches.
PB1: Can you attach the complete file layout of the new cluster (for example which of the modules/etx files will be moved into xmltools cluster?). What is the size of the new cluster when build (in megabytes)? PB2: If you were using xmltools1 in past then perhaps the name should be xmltools2 now. But I would rather use xml1, because no other cluster names attach "tools" to the name. PB3: Can you attach a diff for golden files to make it easier to check what inter-cluster dependencies would be changed? PB4: What is the plan for the set B? Is it going to remain in soa1 or will it be moved later? Thanks.
Created attachment 42434 [details] ide diff patch
Created attachment 42436 [details] nbbuild diff patch
Created attachment 42437 [details] cluster layout
Answer to PB1: Please see attachment layout.txt Size of the new cluster will be ~6MB. Note: Currently we bundle org-netbeans-api-visual.jar as binary. When the graph library becomes part of standard Netbeans, it will be removed. Answer to PB2: Few weeks before J1, all the modules from xmltools1 cluster were moved to soa1 cluster and xmltools1 was no longer in use. "xml1" name is fine with me. Answer to PB3: Please see ide diff patch and nbbuild diff patch for the changes. Answer to PB4: Some items from Set B should move to this new cluster. Am following up on that and will keep you posted.
I noticed that a new module xml/jaxb has been added perhaps today and may show up in the diff patch. That will not be part of this migration. It was included accidentally.
> Note: Currently we bundle org-netbeans-api-visual.jar as binary. > When the graph library becomes part of standard Netbeans, it will be removed. It was part of platform7 cluster in M9 already. I hoped David Kaspar will notify his users after we have accepted his library into platform.
Re: Answer to PB1: The library is a part of the NetBeans Platform since Milestone 8. The notification have been already sent after the API approval.
wsdL tools depends on print\api modules in enterprise pack. Can the print\api and print be moved to core?
wsdl tools belong to the set B part of xml tools in enterprise pack which consist of the following modules xml/wsdl/refactoring,\ xml/wsdlext,\ xml/wsdlextui,\ xml/wsdlui,\ There is a dependency on the print and print\api which is part of enterprise pack. Until those modules become part of core, wsdl tools cannot be moved.
It looks to me that original issue proposed by Samaresh was fixed. I think we should closed this one as fixed and create new one for extra stuff proposed by skini. A patch in this new issue can respond to some questions like: [rk1] what exactly is moving from which place to what place (I do not know what is 'core' and this change only introduced new 'xml' cluster)? [rk2] since one of the modules that you want to move is called print/api please clarify level of stability of this API (and if there are more modules publishing API please do the same for them). How general is this API? Should it deprecate & replace existing o.o.actions.PrintAction, o.o.cookies.PrintCookie and related classes)?
About Print: there are two modules - print.api and print (implementation). The API is more or less stable. The Print API replaces existing print api in NetBeans core: o.o.actions.PrintAction, o.o.cookies.PrintCookie. It replaces Print action in File menu and addes Print Preview action. Old print classes from core can be deprecated. New Print modules can be added in platform7 or ide8 clusters.
re: [rk1] WSDL related modules : xml/wsdl/refactoring, xml/wsdlext, xml/wsdlextui, xml/wsdlui need to be moved from EntPack to standard Netbeans. Core meaning standard Netbeans. re: [rk2] I hope yaroslavskiy made this clear. If there is no objections to moving print and print/api then I'll move them and the WSDL related modules.
re: [rk1] xml/wsdlui, xml/wsdlbindingsupport, xml/wsdlbindingsupport/api, xml/wsdlext, xml/wsdlrefactoring to xml cluster
Print and print api modules can be moved to platform7 cluster because the NetBeans Paltform has old Print action and it would be better if the platform has new Print Preview functionality.
> Print and print api modules can be moved to platform7 cluster Not in 6.0. We have to review and do some redesign for this functionality and APIn to be moved to the platform. This could be possible only after 6.0.
WSDL tools: I have removed the dependency on enterprise pack with relation to the print api from wsdl modules. (It now uses the o.o.cookies.PrintCookie) I intend to move the wsdl modules as I mentioned before to the xml cluster. Let me know of any objections. I plan to do these changes tomorrow.
Why did you remove PrintProvider implementation? There was print preview feature which was killed for wsdl diagram. Print modules were to be moved to xml cluster too? Weren't?
the xml team decided that the moving of wsdl modules to xml cluster is more important. Since print module was not approved to be moved, we decided to use the print core api's and move wsdl modules to xml. whenever the print api module moves to core, I will uncomment back all the changes.
Done.
Fixed long time ago