Re: Reactivating the implementation.spring extension, ready to go with the latest commits to sandbox
Jean-Sebastien, OK, with the latest commit to the sandbox, there is a working version of the Spring implementation. It has the fixes you need, plus a set of other changes which have got the basic version working. I'll hold off on further updates until it's in trunk. The next step is to get References working from the Spring implementation to some external SCA components. Yours, Mike. Jean-Sebastien Delfino wrote: I reviewed the update of the Spring extension that Mike has put in the sandbox and it looks like a good step to get the Spring extension going again. I just had to adjust a few lines to use the 0.90 release SPIs to get it building with the level of code in trunk. I'll commit these fixes later today. Then I'd like to replace the old modules/spring-implementation in trunk (which is broken) by this update. If there's no objection I'll do that sometime tomorrow. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Reactivating the implementation.spring extension, ready to go with the latest commits to sandbox
Jean-Sebastien Delfino wrote: Mike Edwards wrote: Jean-Sebastien, OK, with the latest commit to the sandbox, there is a working version of the Spring implementation. It has the fixes you need, plus a set of other changes which have got the basic version working. I'll hold off on further updates until it's in trunk. The next step is to get References working from the Spring implementation to some external SCA components. Yours, Mike. Jean-Sebastien Delfino wrote: I reviewed the update of the Spring extension that Mike has put in the sandbox and it looks like a good step to get the Spring extension going again. I just had to adjust a few lines to use the 0.90 release SPIs to get it building with the level of code in trunk. I'll commit these fixes later today. Then I'd like to replace the old modules/spring-implementation in trunk (which is broken) by this update. If there's no objection I'll do that sometime tomorrow. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Great, Thanks! I'll work on integrating it with the main build in trunk, and will post here once it's ready. The Spring framework implementation extension is now integrated in the main build. I also did some minor cleanup, removed some old .scdl files and adjusted the disclaimer, license and notice. -- Jean-Sebastien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Reactivating the implementation.spring extension, ready to go with the latest commits to sandbox
Hi, It seems that it breaks the build as the following dependency cannot be resolved: dependency groupIdorg.osoa/groupId artifactIdsca-api/artifactId version1.0-incubating-SNAPSHOT/version /dependency I'll fix it to use org.apache.tuscany.sca as the group id. A side question, should the group id for sca-api be org.osoa or org.apache.tuscany.sca? Thanks, Raymond - Original Message - From: Jean-Sebastien Delfino [EMAIL PROTECTED] To: tuscany-dev@ws.apache.org Sent: Tuesday, June 05, 2007 9:48 AM Subject: Re: Reactivating the implementation.spring extension, ready to go with the latest commits to sandbox Jean-Sebastien Delfino wrote: Mike Edwards wrote: Jean-Sebastien, OK, with the latest commit to the sandbox, there is a working version of the Spring implementation. It has the fixes you need, plus a set of other changes which have got the basic version working. I'll hold off on further updates until it's in trunk. The next step is to get References working from the Spring implementation to some external SCA components. Yours, Mike. Jean-Sebastien Delfino wrote: I reviewed the update of the Spring extension that Mike has put in the sandbox and it looks like a good step to get the Spring extension going again. I just had to adjust a few lines to use the 0.90 release SPIs to get it building with the level of code in trunk. I'll commit these fixes later today. Then I'd like to replace the old modules/spring-implementation in trunk (which is broken) by this update. If there's no objection I'll do that sometime tomorrow. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Great, Thanks! I'll work on integrating it with the main build in trunk, and will post here once it's ready. The Spring framework implementation extension is now integrated in the main build. I also did some minor cleanup, removed some old .scdl files and adjusted the disclaimer, license and notice. -- Jean-Sebastien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Reactivating the implementation.spring extension, ready to go with the latest commits to sandbox
On 6/5/07, Raymond Feng [EMAIL PROTECTED] wrote: Hi, It seems that it breaks the build as the following dependency cannot be resolved: dependency groupIdorg.osoa/groupId artifactIdsca-api/artifactId version1.0-incubating-SNAPSHOT/version /dependency I'll fix it to use org.apache.tuscany.sca as the group id. A side question, should the group id for sca-api be org.osoa or org.apache.tuscany.sca? It didn't seem right to me for the org.apache.tuscany project to be publishing things outside of that namespace. Its worked in the past as we publish to the Incubator maven repository but would we even be able to publish outside of org.apache when its going to the real maven repository? ...ant
Re: Reactivating the implementation.spring extension, ready to go with the latest commits to sandbox
ant elder wrote: On 6/5/07, Raymond Feng [EMAIL PROTECTED] wrote: Hi, It seems that it breaks the build as the following dependency cannot be resolved: dependency groupIdorg.osoa/groupId artifactIdsca-api/artifactId version1.0-incubating-SNAPSHOT/version /dependency I'll fix it to use org.apache.tuscany.sca as the group id. A side question, should the group id for sca-api be org.osoa or org.apache.tuscany.sca? It didn't seem right to me for the org.apache.tuscany project to be publishing things outside of that namespace. Its worked in the past as we publish to the Incubator maven repository but would we even be able to publish outside of org.apache when its going to the real maven repository? ...ant Sorry, my fault... it was building for me as I had an old org.osoa/sca-api artifact in my Maven repository from before the change to org.apache.tuscany.sca. +1 for using org.apache.tuscany.sca, as this is what we use in all modules now. -- Jean-Sebastien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
