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 49756 - arc review possible TCR: J2ee support should have its own cluster
Summary: arc review possible TCR: J2ee support should have its own cluster
Alias: None
Product: javaee
Classification: Unclassified
Component: Code (show other bugs)
Version: 4.x
Hardware: PC Windows ME/2000
: P2 blocker (vote)
Assignee: _ ludo
Depends on: 49634
  Show dependency tree
Reported: 2004-09-30 19:11 UTC by _ ludo
Modified: 2006-06-03 17:50 UTC (History)
3 users (show)

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description _ ludo 2004-09-30 19:11:16 UTC
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/,v
retrieving revision 1.17
diff -r1.17
< cdp.cluster.dir=ide4
> cdp.cluster.dir=enterprise1

d/ finally, we need to also check this story for
modified modules from nb4.0 beta2:

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
Comment 1 _ ludo 2004-09-30 19:12:32 UTC
Pavel, can you look at point number d/ and the changes necessary on the 
 /forte4j/cdpbuild/ file?
Comment 2 _ ludo 2004-10-01 17:55:22 UTC
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...
Comment 3 _ ludo 2004-10-04 21:06:22 UTC
Now that we have the launchers fro Yarda we can have this for EA1
Comment 4 Petr Jiricka 2004-10-06 18:08:49 UTC
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.
Comment 5 _ ludo 2004-10-06 21:05:09 UTC
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...
Comment 6 Michal Zlamal 2004-10-07 10:01:56 UTC
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 - The cluster 
must be disjunctive sets! Also there can't be circular dependencies 
between clusters.
Comment 7 _ ludo 2004-10-07 15:09:20 UTC
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

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.

Comment 8 Michal Zlamal 2004-10-07 16:43:56 UTC
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 
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...

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
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.
Comment 9 _ ludo 2004-10-07 22:25:52 UTC
Move to EA2
Comment 10 Petr Blaha 2004-10-13 10:45:21 UTC
Move issues from temprorary component.
Comment 11 _ ludo 2005-01-05 05:37:31 UTC
fixed in ea2
Comment 12 Petr Blaha 2005-01-20 09:02:41 UTC
New cluster is done. Build 20050119