tag:blogger.com,1999:blog-19835054.post2719251589063805100..comments2024-03-16T13:42:14.318+01:00Comments on Belas Blog: JGroups to investigate adopting Apache License 2.0Bela Banhttp://www.blogger.com/profile/01830789377474906550noreply@blogger.comBlogger7125tag:blogger.com,1999:blog-19835054.post-63147412965288477902013-06-05T12:48:22.972+02:002013-06-05T12:48:22.972+02:00Yes, you probably have to modify Util, should be p...Yes, you probably have to modify Util, should be pretty simple though... unless you want to automate this.<br />Re JmxTest: I don't use the maven build, so I don't knowBela Banhttps://www.blogger.com/profile/03832183909163653875noreply@blogger.comtag:blogger.com,1999:blog-19835054.post-80141013199975944872013-06-05T10:41:19.872+02:002013-06-05T10:41:19.872+02:00Thanks for your idea.
Now, how to make a cross-pl...Thanks for your idea.<br /><br />Now, how to make a cross-platfrom version of JGroups so that it can be merged into the main codebase when we have some Java import package references not supported by Android and removing those tests directory that may be needed to test a JGroup build?<br /><br />For example, in org.jgroups.util.Util.java, I have to disable all Java import packages of java.lang.management.*, javax.management.* just to disable (comment out) dumpThreads(), _printThreads(), getMBeanServer() and registerChannel(). <br /><br />If I don't remove/disable (comment out) them, they will trigger errors in an Android build.<br /><br />Besides that, with Maven, I could not find a way to exclude tests/junit-functional/org/jgroups/tests/JmxTest.java from build-helper-maven-plugin's 'add-test-source' execution goal which needs the source tests/junit-functional. The best way is to reorganize the tests directory so that JmxTest.java can be excluded from a test.<br /><br />Any ideas?Eclectic Eehttps://www.blogger.com/profile/13722088054757904040noreply@blogger.comtag:blogger.com,1999:blog-19835054.post-78302813829395353942013-06-05T10:29:43.662+02:002013-06-05T10:29:43.662+02:00Thanks Belas...
How portable will it be to be mer...Thanks Belas...<br /><br />How portable will it be to be mergeable to the main codebase when we have static Java import package references not supported by Android?<br /><br />For example, in org.jgroups.util.Util.java, I have to disable all Java import packages of java.lang.management.*, javax.management.* just to disable (comment out) dumpThreads(), _printThreads(), getMBeanServer() and registerChannel(). <br /><br />If I don't remove/disable (comment out) them, they will trigger errors in an Android build.<br /><br />Besides that, I could not find a way to exclude tests/junit-functional/org/jgroups/tests/JmxTest.java from build-helper-maven-plugin's 'add-test-source' execution goal which needs the source tests/junit-functional.<br /><br />Any ideas?Eclectic Eehttps://www.blogger.com/profile/13722088054757904040noreply@blogger.comtag:blogger.com,1999:blog-19835054.post-33203134965524439302013-06-03T12:14:40.209+02:002013-06-03T12:14:40.209+02:00The integration with JMX is not really deep; we us...The integration with JMX is not really deep; we use annotations @ManagedAttribute and @ManagedOperation to expose attributes and methods via JMX. You could probably simply replace classes ResourceDMBean and JmxConfigurator in org.jgroups.jmx with Mock classes to get rid of JMX support. Or even better, make it configurable, then this change could go back into the main code base...<br /><br />Re the Byteman scripts: I set the classpath to be ./conf, so ./scipts is sifficient, when executing BM tests. Can't you simply remove the tests directory ?Bela Banhttps://www.blogger.com/profile/03832183909163653875noreply@blogger.comtag:blogger.com,1999:blog-19835054.post-85492298333084749862013-06-03T11:38:13.186+02:002013-06-03T11:38:13.186+02:00I am trying to port the latest 3.4.0.Alpha1 versio...I am trying to port the latest 3.4.0.Alpha1 version of JGroups to Android...but its deep integration with JMX is very annoying to me to disable since JMX is not available under Android (an attempt to make sure Jgroups codebase can support Android and be merged back to master git without side effects).<br /><br />Besides that, why are the Byteman script files not referred correctly: "conf/scripts/.." instead of "scripts/..."? Thanks for the latest correction to the Maven pom file; I've managed to run Maven under Eclipse Juno IDE, though some plugins have no version id.Eclectic Eehttps://www.blogger.com/profile/13722088054757904040noreply@blogger.comtag:blogger.com,1999:blog-19835054.post-77804999500121907172013-06-03T11:38:02.173+02:002013-06-03T11:38:02.173+02:00I am trying to port the latest 3.4.0.Alpha1 versio...I am trying to port the latest 3.4.0.Alpha1 version of JGroups to Android...but its deep integration with JMX is very annoying to me to disable since JMX is not available under Android (an attempt to make sure Jgroups codebase can support Android and be merged back to master git without side effects).<br /><br />Besides that, why are the Byteman script files not referred correctly: "conf/scripts/.." instead of "scripts/..."? Thanks for the latest correction to the Maven pom file; I've managed to run Maven under Eclipse Juno IDE, though some plugins have no version id.Eclectic Eehttps://www.blogger.com/profile/13722088054757904040noreply@blogger.comtag:blogger.com,1999:blog-19835054.post-68770014482224380832013-05-28T12:31:16.066+02:002013-05-28T12:31:16.066+02:00Would be interesting as it would ease adoption int...Would be interesting as it would ease adoption into Apache project and would qualify directly for corporate entities which have a restricted set of preferred licenses.Robert Munteanuhttps://www.blogger.com/profile/13908222919248232461noreply@blogger.com