On Thu, Nov 20, 2008 at 4:13 AM, Luciano Resende <[EMAIL PROTECTED]>wrote:
> On Tue, Nov 18, 2008 at 10:59 PM, Ramkumar R <[EMAIL PROTECTED]> > wrote: > > Hi All, > > > > Branch: https://svn.apache.org/repos/asf/tuscany/branches/sca-java-1.x > > > > Noticed that the following modules/projects (as shown below) are not been > > included OR commented in the parent .pom file in the trunk. > > > > sca/java/demos: > > load-balancing-webapp > > workpool-distributed > > > > sca/java/itest: > > admin > > binding-sca-jms > > contribution-classloader > > domain > > interop-soap-client > > interop-soap-round2-client > > interop-soap-service > > The interop-soap ones are not working, from the last time I checked > > > osgi-tuscany > > promotion-interface-mismatch > > > > sca/java/samples: > > calculator2 > > calculator-osgi > > calculator-rcp > > I'd say that the osgi and rcp are more suitable for the 2,x branch > > > callbacks-jms > > chat2-webapp > > domain-management > > domain-webapp > > helloworld-bpel-ws > This bpel should be working, not sure why it's out of the build > > > helloworld-distributed > > helloworld-jsp > > helloworld-servlet > > helloworld-web > > helloworld-web-callback > > helloworld-ws-deep-webapp > > helloworld-ws-service-webapp > > spi-implementation-pojo > > > > I understand that we have few projects/modules, which does not get > included > > as part of the distribution for a valid reason. > > > > But could not understand the reason behind, not including the above > > mentioned projects as active in the trunk. Can some one help me > understand? > > Thanks. > > > > I have commented some above. I also think that couple others are still > experimental, but I'll leave for others to comment. > > A good strategy would be to double check with the previous release > branch/binary distribution and see if these are old modules that have > not been released, or if they are new and might be experimental for > now. > > The way this has been done in the past is that everything is included in the release unless there is a good reason not to, eg something like it doesn't build, or drags in lots of dependencies and its deemed not ready, or someone specifically asks to have something they are still working on not included, etc. ...ant
