Actually, the base-runtime jar dependency is worse than the development time issues. I just discovered that CAA compliance tests are failing now due to the following facts:
base-runtime brings in a META-INF/services declarations that duplicate the ones from the modules jars. As a result, the DataBindingTransformationInterceptor is added twice into the InvocationChain and we're getting ClassCastExceptions. Thanks, Raymond ________________________________________________________________ Raymond Feng [email protected] Apache Tuscany PMC member and committer: tuscany.apache.org Co-author of Tuscany SCA In Action book: www.tuscanyinaction.com Personal Web Site: www.enjoyjava.com ________________________________________________________________ On Dec 8, 2010, at 8:33 AM, Luciano Resende wrote: > On Wed, Dec 8, 2010 at 8:09 AM, Raymond Feng <[email protected]> wrote: >> That won't fix the problem. The top down mvn eclipse:eclipse will add >> tuscany-base-runtime as a PROJECT >> dependency to many itest projects. We see errors all over the place. >> I suggest that we move back to base-runtime-pom as the maven dependency. > > +1, I made this change in the store sample last night in order to be > able to test some recent changes and it seems to work fine. > > > -- > Luciano Resende > http://people.apache.org/~lresende > http://twitter.com/lresende1975 > http://lresende.blogspot.com/
