Hi Luciano, I'm afraid it's been a little misunderstanding as I totally agree with moving the code to trunk/contrib and I was just detailing why I did the copy of poms from trunk to contrib. It's just that the same build problem was affecting the other modules and samples in contrib/ so that solved them too. I've committed new versions of them (contrib/pom.xml and contrib/modules/pom.xml) which has an empty <modules> section so that they won't report they can't find the modules. Let me know if you agree with the present solution or feel free to let me know if you have other alternatives for it. In the future, is it wanted to move all the work from contrib to trunk/contrib?
Meanwhile, I moved the comet binding to trunk/contrib. Could you give me some more details on the stability and readiness of a new extension. I'm not sure what are the next steps I need to do in order to get the binding ready for the release. Thanks, Florian On Fri, Aug 27, 2010 at 8:17 PM, Luciano Resende <luckbr1...@gmail.com>wrote: > On Fri, Aug 27, 2010 at 4:59 AM, Florian MOGA <moga....@gmail.com> wrote: > > > Regarding the binding, I've just fixed the last issues and details so if > > that's ok with everybody I can proceed moving it to trunk these days. > Will > > it enter the 2.0 release or are there any further steps needed? > > Florian > > I guess my initial suggestion was much simpler, just move from > contrib/modules [1] to trunk/contrib/modules [2], to simplify how > others would checkout and load the extension to their IDE. As for > including in the release, I guess you would be the best to access the > stability and readiness of the new extension and if all tests are > passing, etc > > > [1] https://svn.apache.org/repos/asf/tuscany/sca-java-2.x/contrib/modules/ > [2] > https://svn.apache.org/repos/asf/tuscany/sca-java-2.x/trunk/contrib/modules/ > > > -- > Luciano Resende > http://people.apache.org/~lresende > http://twitter.com/lresende1975 > http://lresende.blogspot.com/ >
