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.
Afer devrev review today, it was highly recommended we swtich to a separate cluster for the J2ee support even for EA1. The recommendations are: 1/`the new cluster name: enterprise1 2/ the user directory name: .netbeans/4.1ea1 3/ the launcher name: nbj2ee and netbeansj2ee (.cmd, .exe ) don't know about macosx... Prague people will see if they can provide the launcher for us, and accomodate it to user 1/ and 2/ I looked quickly is this is possible, and it does not seem to be complex: a/ websvc regitry build.xml needs to avoid ide4 name dependancies on jar location b/ the registry xml file describing extra jar also need to be modified a little c/ our cluster def needs to change: RCS file: /forte4j/cdpbuild/cluster.properties,v retrieving revision 1.17 diff -r1.17 cluster.properties 23c23 < cdp.cluster.dir=ide4 --- > cdp.cluster.dir=enterprise1 d/ finally, we need to also check this story for modified modules from nb4.0 beta2: tomcatint j2eeserver webproject these modules need to go to the entreprise1 cluster as well since the loading order will first looat this cluster, then the regular ide4, allowing us to override the std nb4.0 bits... This is asked for because of possible issues with RPM or pacakge based installs on linux or solaris. It also clearly demarks j2ee work from nb regular bits.
Pavel, can you look at point number d/ and the changes necessary on the /forte4j/cdpbuild/cluster.properties file?
a/ and /b are new integrated. RE would now have to handle the changes in the cluster definition to put j2ee all modules, as well as all the modules that are not from nb4.0 beta2 branch (j2eeserver, web/project, tomcat, maybe other) inot this new cluster also. We can do that as soon as we have a new launcher...
Now that we have the launchers fro Yarda we can have this for EA1
I think doing d/ is not easy - it requries to build both the beta2 version of these modules, and the promoe_dev modified version of them. Please suggest how this should be handled by the build script.
our build can use a built binarary beta2 version of the 3 modules and put them in the cocrrect location, and still continue to build the modified versions. Very simple: unzip a zip file somewhere in ide4 cluster...
This seems like a big hack. I thought that this change is intented to be clean in architecture. The thing what are you proposing seem to me as big contradiction to - http://openide.netbeans.org/proposals/arch/clusters.html. The cluster must be disjunctive sets! Also there can't be circular dependencies between clusters.
There is no HACK into releasing bits we do not build. We do the same for Tomcat, app server plugin, etc. This is a common pattern for building products. These 3 modules belong to NetBeans 4.0 Beta2 and we build NetBeans 4.1 EA1. So This is very clean for me. There is also NO circular dependency. enterprise1 depends on IDE4 and can overwrite IDE4 when necessary. If you have issue with is DEVREV recommendation, talk to this team.
For tomcat and appserver plugin we take whole binary and not changing it. What you are proposing is to take the NetBeans beta2, rebuild its 3 modules and add enterprise1 cluster, which will contain those 3 modules - it seems to me as hack. Note that some can use autoupdate facility incorporated in NetBeans beta2 and completly screw up the product. Here is the scenario: Install netbeans beta2 Install enterprise1 cluster run netbeans beta2 and update its content to ie FCS or anything else which will not dependencies in enterprise1 cluster run netbeans with enterprise1 cluster... Secondly: If we'll start building from NB beta2 binary, then there will be no rebuild of NetBeans beta2 module, only those which should go to enterprice1 cluster will be rebuild. Ad dependencies: Are there any modules in ide4 cluster which depend on those 3 modules which are moved from NB to enterprise1 cluster? If so, then you have cilcular dependency Ad rewriting module in ide4 cluster: read the http://openide.netbeans.org/proposals/arch/installation.html. If you have any changes to it, you should release new version of whole cluster, you can't update patrs of it. Ad DEVREV recommendation: Trung told that we don't use it for EA1.
Move to EA2
Move issues from temprorary component.
fixed in ea2
New cluster is done. Build 20050119