Hello,
Clustering features are in the jboss-all/cluster package which is in fact
... the "jbossmx" CVS module.
The reason is that when Stacy Curl originaly submitted clustering code for
MBEANs, she (he?) put it in this module. Then Jason wrote the new build
system, then I commited my code in what was appearing to be the cluster
module. For now, all is nice.
Now, Juha is going to commit JMX code. Consequenlty, it would seem logical
for him to commit in the CVS jbossmx module... You know what I mean?
Bill and I commit clustering in jboss-all/cluster which in fact is ...
jbossmx
Juha commits JMX code in jbossmx which in fact is ... jboss-all/cluster
Questions:
- Should we stay like this and all commit at the same place?
- Should Bill and I move our clustering stuff somewhere else?
- Should Juha moves the JMX stuff somewhere else?
Opinions?
Cheers,
Sacha
-----Message d'origine-----
De : Juha Lindfors [mailto:[EMAIL PROTECTED]]
Envoye : mercredi, 28 novembre 2001 20:36
A : Sacha Labourey
Objet : RE: [JBoss-dev] CVS update:
jboss/src/main/org/jboss/verifier/strategy AbstractVerifier.java
At 14:04 28.11.2001 +0100, you wrote:
>Would like that we move our clustering code in jbosscluster (or jbossha, or
>whatever else)?
>
>If jbossmx is gonna grow fast and big, the clustering stuff may be more of
a
>problem/confusion than anything else.
>
>What is your point of view?
You may be right about it getting confusing. But you don't have to move on
my account. If you do want to move to get rid of the jbossmx on the CVS
logs then let me know, because I will take over the module in that case.
Otherwise, i can just create a module with a different name, maybe just JMX
and have the build system move it into "jbossmx". Just thought invading an
existing module would save me from having to figure out the new build
system, which I'm completely clueless of.
-- Juha
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
