On Jan 17, 2008 2:09 PM, ant elder <[EMAIL PROTECTED]> wrote: > The SCA 1.1 distro ships Derby 10.1.2.1 whereas in the SCA 1.0.1 we > shipped > Derby 10.1.3.1. Is there a reason for this change? I'm guessing it > probably > makes no real difference to us, it just feels slightly odd to be going > back > so thought i'd ask if it was done intentionally? > > ...ant
Not an intentional change. I hadn't actually noticed. The dependency is coming in through here derby-10.1.2.1.jar test Apache Tuscany SCA Data Engine Helper derby-10.1.2.1 derby-10.1.2.1.jar compile Apache Tuscany SCA Host JMS ActiveMQ derby-10.1.2.1 derby-10.1.2.1.jar runtime Apache Tuscany SCA Data Implementation Extension derby-10.1.2.1 derby-10.1.2.1.jar test Apache Tuscany SCA HelloWorld Web Service Reference JMS Sample tuscany-host-jms-activemq-1.1-incubating-SNAPSHOT derby-10.1.2.1 derby-10.1.2.1.jar compile Apache Tuscany SCA HelloWorld Web Service JMS Sample tuscany-host-jms-activemq-1.1-incubating-SNAPSHOT derby-10.1.2.1 derby-10.1.3.1.jar compile Apache Tuscany SCA BPEL Implementation Extension derby-10.1.3.1 derby-10.1.3.1.jar runtime Apache Tuscany SCA HelloWorld BPEL Sample tuscany-implementation-bpel-1.1-incubating-SNAPSHOT derby-10.1.3.1 It's ActiveMQ and the Data Implementation extension pulling it back to 1.2.1 . Simon
