Re: [JBoss-dev] JBossMX and jboss-all
I can explain how todo this, or simply do it if you like... it is rather easy. --jason ___ View: http://jboss.org/forums/thread.jsp?forum=66&thread=4999 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] JBossMX and jboss-all
sure, just need to setup a seperate project like jboss-mq, setup build files and bingo. unfortunatly the namespace is kinda messed up, so you would probably have to setup a jboss-mx project. --jason On Fri, 7 Dec 2001, Juha-P Lindfors wrote: > > Is there a way to co and build a standalone jbossmx? that should be > possible, can it be done the way MQ uses CVS now? > > -- Juha > > > On Thu, 6 Dec 2001, Jason Dillon wrote: > > > Date: Thu, 6 Dec 2001 17:25:43 -0700 (MST) > > From: Jason Dillon <[EMAIL PROTECTED]> > > To: [EMAIL PROTECTED] > > Subject: Re: [JBoss-dev] JBossMX and jboss-all > > > > just added build files. you will need to checkout jboss-all again to get the >changes. > > > > --jason > > > ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] JBossMX and jboss-all
Is there a way to co and build a standalone jbossmx? that should be possible, can it be done the way MQ uses CVS now? -- Juha On Thu, 6 Dec 2001, Jason Dillon wrote: > Date: Thu, 6 Dec 2001 17:25:43 -0700 (MST) > From: Jason Dillon <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Re: [JBoss-dev] JBossMX and jboss-all > > just added build files. you will need to checkout jboss-all again to get the >changes. > > --jason > ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] JBossMX and jboss-all
oh ya, when it comes time to hook these up, we need to add module defs in build/build.xml and add it to one of the default groups. I left it out for the moment, so it won't get built by default. _ View: http://jboss.org/forums/thread.jsp?forum=66&thread=4999 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] JBossMX and jboss-all
No the jmx stuff is in the right place, though if it is called jbossmx it might have made sence to use that... but since that is currently the cluster module... ahhh. It is all messed up. We really should re-org the entire repository, to reflect the namespace that we are using on checkout. This is make it much easier to add new modules... except for external modules. Take the jboss-mq project for example. It is really just a subset of the jboss-all project with a seperate build module... or all the modules except build are external. I would like to see us re-org like this: /CVSROOT /tools /thirdparty /jboss/ build/ server/ jmx/ cluster/ ... /jbossmq/ build/ and so on. By doing this, the main 'jboss' project would be easier to maintain, in that when new sub-modules are added users could update and sync to the correct version. jbossmq would still have to use CVSROOT/modules to import the modules from jboss, and users should have to re-checkout when a structure change is made. Since it is more likly that a structure change will be made (like the addition of the jmx stuff) to jboss, it makes sence to gear things in its favor. Right now we are creating the project workspace entirely by the usage of CVSROOT/modules. This is confusing to new (and seasoned users) and should eventually be changed to reflect the current (and possibly medium-term future) for the project. The down side is that it will take a little time to get users to resync, and that we currently don't have easy access to the actual file system where the repository resides on to make effective changes. --jason On Fri, 7 Dec 2001, Juha-P Lindfors wrote: > > hmm? did I drop my module in the wrong place in the CVS? > > -- Juha > > On Thu, 6 Dec 2001, Jason Dillon wrote: > > > Date: Thu, 6 Dec 2001 16:45:57 -0700 (MST) > > From: Jason Dillon <[EMAIL PROTECTED]> > > To: [EMAIL PROTECTED] > > Subject: Re: [JBoss-dev] JBossMX and jboss-all > > > > come to think of it, users will have to checkout again to get the jboss-all/jmx >directory too. > > > > we really need to reorganize the repository to avoid this in the future. > > > >:( > > > > --jason > > > > View: http://jboss.org/forums/thread.jsp?forum=66&thread=4999 > > > > ___ > > Jboss-development mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] JBossMX and jboss-all
just added build files. you will need to checkout jboss-all again to get the changes. --jason _ View: http://jboss.org/forums/thread.jsp?forum=66&thread=4999 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] JBossMX and jboss-all
hmm? did I drop my module in the wrong place in the CVS? -- Juha On Thu, 6 Dec 2001, Jason Dillon wrote: > Date: Thu, 6 Dec 2001 16:45:57 -0700 (MST) > From: Jason Dillon <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Re: [JBoss-dev] JBossMX and jboss-all > > come to think of it, users will have to checkout again to get the jboss-all/jmx >directory too. > > we really need to reorganize the repository to avoid this in the future. > > :( > > --jason > > View: http://jboss.org/forums/thread.jsp?forum=66&thread=4999 > > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] JBossMX and jboss-all
come to think of it, users will have to checkout again to get the jboss-all/jmx directory too. we really need to reorganize the repository to avoid this in the future. :( --jason View: http://jboss.org/forums/thread.jsp?forum=66&thread=4999 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] JBossMX and jboss-all
That's up to bill and sacha.. but I think you're right, moving might be more trouble than its worth -- Juha On Thu, 6 Dec 2001, Jason Dillon wrote: > What is the deal with the cluster stuff? It is currently in jbossmx module > in cvs. It should be moved, but moving it will break all jboss-all > checkouts, which I am not really into doing too often. I think we should > leave it there until there is time to fix the CVS depot of all of its > namespace issues. > > --jason ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] JBossMX and jboss-all
I will build'ify it. What is the deal with the cluster stuff? It is currently in jbossmx module in cvs. It should be moved, but moving it will break all jboss-all checkouts, which I am not really into doing too often. I think we should leave it there until there is time to fix the CVS depot of all of its namespace issues. --jason On Thu, 6 Dec 2001, Juha Lindfors wrote: > > if you want to.. although its not used anywhere yet.. and it's completely > lacking the build infrastructure so you'd have to add that. Of course I > don't mind if you want to work on it :) > > -- Juha > > At 19:32 5.12.2001 -0800, Jason Dillon wrote: > >Should we add the JBossMX stuff to jboss-all? I don't mean the clustering > >stuff, I mean the /jmx bits. Should probably move the jbossmx stuff to > >cluster or something... > > > >--jason > ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] JBossMX and jboss-all
if you want to.. although its not used anywhere yet.. and it's completely lacking the build infrastructure so you'd have to add that. Of course I don't mind if you want to work on it :) -- Juha At 19:32 5.12.2001 -0800, Jason Dillon wrote: >Should we add the JBossMX stuff to jboss-all? I don't mean the clustering >stuff, I mean the /jmx bits. Should probably move the jbossmx stuff to >cluster or something... > >--jason ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JBossMX and jboss-all
Should we add the JBossMX stuff to jboss-all? I don't mean the clustering stuff, I mean the /jmx bits. Should probably move the jbossmx stuff to cluster or something... --jason ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
