Thanks for the fix.
It appears buildr only packages the first project ("ode") by default; I'm
not sure if this is by design.
In any case, I've just updated the Buildfile to also package ode-extensions
by default so we're covered now.
alex
On Thu, Aug 20, 2009 at 2:07 PM, Tammo van Lessen <[email protected]>wrote:
> Hi Alex,
>
> should be fixed now, sorry. For some reason, buildr is skipping the
> extensions directory by default, at least in my install. Do you have any
> idea why?
>
> Tammo
>
> Alex Boisvert wrote:
> > Anybody getting the same?
> >
> > Packaging apache-ode-docs-2.1-SNAPSHOT.zip
> > Compiling ode-extensions:e4x into
> > /home/boisvert/svn/ode/trunk/extensions/e4x/target/classes
> > Compiling ode-extensions:e4x:test into
> > /home/boisvert/svn/ode/trunk/extensions/e4x/target/test/classes
> >
> /home/boisvert/svn/ode/trunk/extensions/e4x/src/test/java/org/apache/ode/extension/e4x/JSOperationTest.java:49:
> > run(java.lang.Object,java.lang.String,org.w3c.dom.Element) in
> > org.apache.ode.bpel.rtrep.common.extension.AbstractSyncExtensionOperation
> > cannot be applied to
> > (org.apache.ode.test.MockExtensionContext,org.w3c.dom.Element)
> > jso.run(c, e);
> >
> > alex
> >
>
>
> --
> Tammo van Lessen - http://www.taval.de
>
