Hide Forgot
Date of First Response: 2008-09-30 09:40:37 project_key: SOA We need to clarify with jon team to ensure that plugin code stays in synch and that documentation etc does not get missed.
My view is that we should leave the JON team to handle the base (extensible) server and we should manage the ESB plugin. The ESB plugin has a tighter dependency with the ESB code and is more likely to change as a consequence of ESB changes than JON changes.
The JON build will not include the ESB JON plug-in. The ESB team will build the plug-in and hand off to the JON team for release on the CSP. The JON team asks if the ESB team has considered re-branding and will send information about re-branding to the ESB team. There is no patch model for JON at the moment. When needed there have been Service Patch releases. Patch releases and regular releases need to be coordinated between the teams (products) now that we are adding this dependency.
It should also be made clear that neither JON, nor the JON plug in will be shipped with SOA or ESB. The distribution of the JON plug in will be handled by the JON team.
We need to clarify what packaging the JON team expect for the plugin, Have emailed them to query.
Linked to SOA-910 (md5/sha256 issue).
Link: Added: This issue related SOA-910
Attachment: Added: scripts.2008-10-03.zip
This is done. Open specific issues from now on.