Hi folks: Please note that although this first release will entail releasing all the transports simultaneously, this is quite possibly the LAST time that will happen barring any major API changes in Axis2.
We need to be able to release *each* transport individually, on their own schedules, as has been mentioned before. So Ruwan, when you're doing the release, can you check into doing it as N individual releases rather than one big one? Just trying to make sure that it's possible to do it that way and we haven't built anything into our Maven configuration that prevents it. Thanks, --Glen Ruwan Linton (JIRA) wrote: > [ > https://issues.apache.org/jira/browse/WSCOMMONS-492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Ruwan Linton updated WSCOMMONS-492: > ----------------------------------- > > Fix Version/s: Transports 1.0 > > SMS transport will be included in the Transports 1.0 release > >> Transport guide for the SMS Transport >> ------------------------------------- >> >> Key: WSCOMMONS-492 >> URL: https://issues.apache.org/jira/browse/WSCOMMONS-492 >> Project: WS-Commons >> Issue Type: Improvement >> Components: Transport >> Environment: any >> Reporter: Charith Dhanushka Wickramarachchi >> Assignee: Ruwan Linton >> Priority: Minor >> Fix For: Transports 1.0 >> >> Attachments: sms-transport-doc-02-08-2009.patch, >> sms-transport-doc-02-08-2009.patch >> >> >> Having a Transport guide for the SMS Transport will add value to that >> transport. >> I'll provide a patch for this improvement >
