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 solve
On Fri, Aug 27, 2010 at 4:59 AM, Florian MOGA 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 init
Hi Luciano,
There was no pom in the contrib/ folder as well (I've committed it at that
time) so the only way to have it working without copying poms was either
setting the parent to ../../trunk/modules/pom.xml or not using a parent
which wouldn't bring some tuscany dependencies.
Before making the
On Tue, Aug 24, 2010 at 5:22 PM, Florian MOGA wrote:
> Hi,
> Sorry for the late post, been out of town the last few days. Today I've
> committed some changes to the binding and the sample consisting in
> formatting the code with the Tuscany Eclipse formatter, using the Tuscany
> code template and
Hi,
Sorry for the late post, been out of town the last few days. Today I've
committed some changes to the binding and the sample consisting in
formatting the code with the Tuscany Eclipse formatter, using the Tuscany
code template and doing a little bit of refactoring where needed. This being
done
Should we move the binding-comet-* from [1] to [2], this makes it
easier to others to load and give feedback to the new code. Or even
better, are we ready to move it to trunk ?
[1] https://svn.apache.org/repos/asf/tuscany/sca-java-2.x/contrib/modules/
[2] https://svn.apache.org/repos/asf/tuscany/s
