[jira] Commented: (GERONIMO-2455) Upgrade to new MX4J service release
[ https://issues.apache.org/jira/browse/GERONIMO-2455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482004 ] Kevan Miller commented on GERONIMO-2455: Great. Thanks Jason. I doubt seriously that we'll ever have a 1.1.2. There'd be a bunch of updates required to meet new Apache src header licensing requirements. It would take a lot of work. The 1.1.x build problems are pretty troubling, though. I would assume that an attempt to build 1.1.1 would encounter the same problems... > Upgrade to new MX4J service release > --- > > Key: GERONIMO-2455 > URL: https://issues.apache.org/jira/browse/GERONIMO-2455 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: buildsystem >Affects Versions: 1.0, 1.1, 1.1.1, 1.1.2, 1.2 >Reporter: Kevan Miller > Assigned To: Kevan Miller > Fix For: 1.1.2, 1.2 > > Attachments: mx4j-3.0.2-bundle.jar, mx4j-jmx-3.0.2-bundle.jar, > mx4j-remote-3.0.2-bundle.jar, mx4j-tools-3.0.2-bundle.jar > > > There's a timing hole in the mx4j Monitor implementation. In some scenarios, > a Monitor will not receive an appropriate Notifcation after being started. > The fix for the problem has been committed to mx4j head. I've run tests using > a private build from mx4j head, all looks well. > Once available, we should upgrade to the mx4j service release 3.0.2. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2455) Upgrade to new MX4J service release
[ https://issues.apache.org/jira/browse/GERONIMO-2455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481976 ] Jason Dillon commented on GERONIMO-2455: I've updated 1.2 to use 3.0.2... but 1.1 is still using m1 and these jars aren't in the m1 central repo. We could add the jars to the 1.1's repository module and then update the version of mx4j to 3.0.2 too... but are we ever going to release 1.1.2? The build for 1.1 is a *huge* mess... > Upgrade to new MX4J service release > --- > > Key: GERONIMO-2455 > URL: https://issues.apache.org/jira/browse/GERONIMO-2455 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: buildsystem >Affects Versions: 1.0, 1.1, 1.1.1, 1.1.2, 1.2 >Reporter: Kevan Miller > Assigned To: Kevan Miller > Fix For: 1.1.2, 1.2 > > Attachments: mx4j-3.0.2-bundle.jar, mx4j-jmx-3.0.2-bundle.jar, > mx4j-remote-3.0.2-bundle.jar, mx4j-tools-3.0.2-bundle.jar > > > There's a timing hole in the mx4j Monitor implementation. In some scenarios, > a Monitor will not receive an appropriate Notifcation after being started. > The fix for the problem has been committed to mx4j head. I've run tests using > a private build from mx4j head, all looks well. > Once available, we should upgrade to the mx4j service release 3.0.2. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2455) Upgrade to new MX4J service release
[ http://issues.apache.org/jira/browse/GERONIMO-2455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461755 ] Donald Woods commented on GERONIMO-2455: Try the 4 attached jars, which I built from your jar contents at - http://people.apache.org/~kevan/mx4j-3.0.2-uploadRequest.jar which match the file format structure as pointed at at - http://maven.apache.org/guides/mini/guide-ibiblio-upload.html -Donald > Upgrade to new MX4J service release > --- > > Key: GERONIMO-2455 > URL: http://issues.apache.org/jira/browse/GERONIMO-2455 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: buildsystem >Affects Versions: 1.0, 1.1, 1.1.1, 1.1.2, 1.2 >Reporter: Kevan Miller > Assigned To: Kevan Miller > Fix For: 1.1.2 > > Attachments: mx4j-3.0.2-bundle.jar, mx4j-jmx-3.0.2-bundle.jar, > mx4j-remote-3.0.2-bundle.jar, mx4j-tools-3.0.2-bundle.jar > > > There's a timing hole in the mx4j Monitor implementation. In some scenarios, > a Monitor will not receive an appropriate Notifcation after being started. > The fix for the problem has been committed to mx4j head. I've run tests using > a private build from mx4j head, all looks well. > Once available, we should upgrade to the mx4j service release 3.0.2. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-2455) Upgrade to new MX4J service release
[ http://issues.apache.org/jira/browse/GERONIMO-2455?page=comments#action_12456701 ] Kevan Miller commented on GERONIMO-2455: Just checked the maven upload request that i submitted to get the new mx4j release uploaded to a maven repo. It got rejected for not being up to snuff. I'll have to look to see what's wrong... > Upgrade to new MX4J service release > --- > > Key: GERONIMO-2455 > URL: http://issues.apache.org/jira/browse/GERONIMO-2455 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: buildsystem >Affects Versions: 1.1.1, 1.1, 1.0, 1.1.2, 1.2 >Reporter: Kevan Miller > Assigned To: Kevan Miller > Fix For: 1.1.2, 1.2 > > > There's a timing hole in the mx4j Monitor implementation. In some scenarios, > a Monitor will not receive an appropriate Notifcation after being started. > The fix for the problem has been committed to mx4j head. I've run tests using > a private build from mx4j head, all looks well. > Once available, we should upgrade to the mx4j service release 3.0.2. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-2455) Upgrade to new MX4J service release
[ http://issues.apache.org/jira/browse/GERONIMO-2455?page=comments#action_12447915 ] Kevan Miller commented on GERONIMO-2455: I created a Maven upload request for 3.0.2 -- http://jira.codehaus.org/browse/MAVENUPLOAD-1220 Once available, I'll update our version number... > Upgrade to new MX4J service release > --- > > Key: GERONIMO-2455 > URL: http://issues.apache.org/jira/browse/GERONIMO-2455 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: buildsystem >Affects Versions: 1.1.1, 1.1, 1.0, 1.1.2, 1.2 >Reporter: Kevan Miller > Assigned To: Kevan Miller > Fix For: 1.1.2, 1.2 > > > There's a timing hole in the mx4j Monitor implementation. In some scenarios, > a Monitor will not receive an appropriate Notifcation after being started. > The fix for the problem has been committed to mx4j head. I've run tests using > a private build from mx4j head, all looks well. > Once available, we should upgrade to the mx4j service release 3.0.2. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
