I made an export of the management console using the Eclipse PDE Builder with version 3.4 plug-ins, and the splash screen worked as expected. The only meaningful difference appeard to be that it used an executable to start up: as I commented before I noted that when I removed execute permissions from that file accidentally when making the ant build scripts, that too stopped the splash screen working (although the console itself still did)...so I think that is where the problem lies, the launcher executable is what runs the splash screen and it currently isn’t there to be used.
The updated equinox launcher you used still uses all the shared objects as the 3.2 launcher I did, they are just in a different place. So I think it should be ok to lay out the new executable file where it is supposed to be (it also needs some config changes) as it appears the updated launcher plugin/libraries works fine on RHEL4. While at it, I think updating the build to use the new launchers for the win32 build would be good, and making a linux x86_64 version too. This would also a reduction in complexity of the launch shell scripts, as the console can launch itself from that executable. The platform detection routine the scripts use does not work on all linux variants (notably ubuntu - perhaps not the most supported platform of choice, but that doenst really change the fact the script doenst work all the time when dong something it doesnt even need to), and the QPIDMC_HOME env variable is not required. The platform dependant bits of the mc are hardcoded anyway, so all the script does is tell it what it already knows if is on the right platform, or tell it information it cant use when it is being used on the wrong platform or the script cant detect the architecture automatically and the user hasn’t set it explicitly for the script. This leaves console logging and security type as the only things it is really useful for, the latter of which I hope to remove the need for in future. I am really busy this week but after that I will be free to work on things, so I will put together an patch to update the mc build to use 3.4 plugins, with win32 and linux x64 + x86_64 versions. Robbie -----Original Message----- From: Robert Gemmell (JIRA) [mailto:[EMAIL PROTECTED] Sent: 27 November 2008 19:01 To: [email protected] Subject: [jira] Commented: (QPID-1243) Provide mechanism to build management console[MESSAGE NOT SCANNED] [ https://issues.apache.org/jira/browse/QPID-1243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12651412#action_12651412 ] Robert Gemmell commented on QPID-1243: -------------------------------------- Im not sure about the splash, the stuff I have read about it basically said it was a case of ensuring it was stored in the correct place within the plugin and as you say setting the splashpath config property. When I get a chance ill take a look and see if theres anything obvious out there that will fix it, and failing that ill try an Eclipse PDE Builder export of the whole console and see if it works as expected, then compare the difference. The last time i tried to have the PDE Builder export a release it threw its toys out the pram, so ill try to figure out why that was too :) > Provide mechanism to build management console > --------------------------------------------- > > Key: QPID-1243 > URL: https://issues.apache.org/jira/browse/QPID-1243 > Project: Qpid > Issue Type: Bug > Components: Ant Build System, Java Management : JMX Console > Affects Versions: M3 > Reporter: Martin Ritchie > Assignee: Martin Ritchie > Attachments: QPID-1243_21nov2008.zip, QPID-1243_24nov2008.zip > > > Summary: > Currently, there is no way to build the management console using ant, whilst > the maven system may still work we should complete the move to ant by also > updating the packaging required for the console. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
