You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by Lance Waterman <la...@gmail.com> on 2006/12/13 09:56:49 UTC
Latest Updates
I just pulled down the latest SVN image and I'm seeing most of the unit
tests failing with parsing errors. Anyone else seeing this?
NAMESPACE_ERR: An attempt is made to create or change an object in a way
which is incorrect with regard to namespaces.
Lance
Re: Latest Updates
Posted by Assaf Arkin <ar...@intalio.com>.
I'd rather not mess with the delicate balance of the universe, renaming the
files sounds like the easier fix.
On 12/15/06, Matthieu Riou <ma...@gmail.com> wrote:
>
> I think the pattern is configurable somewhere.
>
> Matthieu
>
> On 12/15/06, Assaf Arkin <ar...@intalio.com> wrote:
> >
> > Turns out mvn test filters for classes that have a name ending with
> Test.
> > The test cases are all named ending with Tests.
> >
> > Assaf
> >
> > On 12/14/06, Lance Waterman <la...@gmail.com> wrote:
> > >
> > > It doesn't look like a vendetta thing. Not sure why the plugin can't
> > find
> > > the tests - I'll take a look.
> > >
> > > Lance
> > >
> > > On 12/13/06, Assaf Arkin <ar...@intalio.com> wrote:
> > > >
> > > > When I run bpel-test, I get "no tests to run". By design, or does
> > Maven
> > > > have
> > > > something personal against me?
> > > >
> > > > Assaf
> > > >
> > > > On 12/13/06, Lance Waterman <la...@gmail.com> wrote:
> > > > >
> > > > > Thanks Matthieu - yes I was trying to run the bpel-test. I'll
> check
> > my
> > > > > Xalan
> > > > > jar.
> > > > >
> > > > >
> > > > > On 12/13/06, Matthieu Riou <ma...@gmail.com> wrote:
> > > > > >
> > > > > > I have before. Which tests are failing, the bpel-test ones?
> > > > > >
> > > > > > This is due to a bad version of Xalan. All Maven servers I've
> > found
> > > > have
> > > > > a
> > > > > > Xalan 2.7.0 producing weird exceptions like this one (for a
> quick
> > > > check,
> > > > > > the
> > > > > > standard Xalan distro is 2.9MB whereas the corrupted one
> > downloaded
> > > by
> > > > > > Maven
> > > > > > is 2.6MB). To get rid of this problem I've added our own Xalan
> > > > directly
> > > > > > from
> > > > > > the distro with a groupId of org.apache.ode (check the root
> pom).
> > > That
> > > > > > sort
> > > > > > of reduces the maven uncertainty principle. A bit.
> > > > > >
> > > > > > Matthieu
> > > > > >
> > > > > > On 12/13/06, Lance Waterman <la...@gmail.com> wrote:
> > > > > > >
> > > > > > > I just pulled down the latest SVN image and I'm seeing most of
> > the
> > > > > unit
> > > > > > > tests failing with parsing errors. Anyone else seeing this?
> > > > > > >
> > > > > > > NAMESPACE_ERR: An attempt is made to create or change an
> object
> > in
> > > a
> > > > > way
> > > > > > > which is incorrect with regard to namespaces.
> > > > > > >
> > > > > > > Lance
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > CTO, Intalio
> > > > http://www.intalio.com
> > > >
> > > >
> > >
> > >
> >
> >
> > --
> > CTO, Intalio
> > http://www.intalio.com
> >
> >
>
>
--
CTO, Intalio
http://www.intalio.com
Re: Latest Updates
Posted by Matthieu Riou <ma...@gmail.com>.
I think the pattern is configurable somewhere.
Matthieu
On 12/15/06, Assaf Arkin <ar...@intalio.com> wrote:
>
> Turns out mvn test filters for classes that have a name ending with Test.
> The test cases are all named ending with Tests.
>
> Assaf
>
> On 12/14/06, Lance Waterman <la...@gmail.com> wrote:
> >
> > It doesn't look like a vendetta thing. Not sure why the plugin can't
> find
> > the tests - I'll take a look.
> >
> > Lance
> >
> > On 12/13/06, Assaf Arkin <ar...@intalio.com> wrote:
> > >
> > > When I run bpel-test, I get "no tests to run". By design, or does
> Maven
> > > have
> > > something personal against me?
> > >
> > > Assaf
> > >
> > > On 12/13/06, Lance Waterman <la...@gmail.com> wrote:
> > > >
> > > > Thanks Matthieu - yes I was trying to run the bpel-test. I'll check
> my
> > > > Xalan
> > > > jar.
> > > >
> > > >
> > > > On 12/13/06, Matthieu Riou <ma...@gmail.com> wrote:
> > > > >
> > > > > I have before. Which tests are failing, the bpel-test ones?
> > > > >
> > > > > This is due to a bad version of Xalan. All Maven servers I've
> found
> > > have
> > > > a
> > > > > Xalan 2.7.0 producing weird exceptions like this one (for a quick
> > > check,
> > > > > the
> > > > > standard Xalan distro is 2.9MB whereas the corrupted one
> downloaded
> > by
> > > > > Maven
> > > > > is 2.6MB). To get rid of this problem I've added our own Xalan
> > > directly
> > > > > from
> > > > > the distro with a groupId of org.apache.ode (check the root pom).
> > That
> > > > > sort
> > > > > of reduces the maven uncertainty principle. A bit.
> > > > >
> > > > > Matthieu
> > > > >
> > > > > On 12/13/06, Lance Waterman <la...@gmail.com> wrote:
> > > > > >
> > > > > > I just pulled down the latest SVN image and I'm seeing most of
> the
> > > > unit
> > > > > > tests failing with parsing errors. Anyone else seeing this?
> > > > > >
> > > > > > NAMESPACE_ERR: An attempt is made to create or change an object
> in
> > a
> > > > way
> > > > > > which is incorrect with regard to namespaces.
> > > > > >
> > > > > > Lance
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > CTO, Intalio
> > > http://www.intalio.com
> > >
> > >
> >
> >
>
>
> --
> CTO, Intalio
> http://www.intalio.com
>
>
Re: Latest Updates
Posted by Assaf Arkin <ar...@intalio.com>.
Turns out mvn test filters for classes that have a name ending with Test.
The test cases are all named ending with Tests.
Assaf
On 12/14/06, Lance Waterman <la...@gmail.com> wrote:
>
> It doesn't look like a vendetta thing. Not sure why the plugin can't find
> the tests - I'll take a look.
>
> Lance
>
> On 12/13/06, Assaf Arkin <ar...@intalio.com> wrote:
> >
> > When I run bpel-test, I get "no tests to run". By design, or does Maven
> > have
> > something personal against me?
> >
> > Assaf
> >
> > On 12/13/06, Lance Waterman <la...@gmail.com> wrote:
> > >
> > > Thanks Matthieu - yes I was trying to run the bpel-test. I'll check my
> > > Xalan
> > > jar.
> > >
> > >
> > > On 12/13/06, Matthieu Riou <ma...@gmail.com> wrote:
> > > >
> > > > I have before. Which tests are failing, the bpel-test ones?
> > > >
> > > > This is due to a bad version of Xalan. All Maven servers I've found
> > have
> > > a
> > > > Xalan 2.7.0 producing weird exceptions like this one (for a quick
> > check,
> > > > the
> > > > standard Xalan distro is 2.9MB whereas the corrupted one downloaded
> by
> > > > Maven
> > > > is 2.6MB). To get rid of this problem I've added our own Xalan
> > directly
> > > > from
> > > > the distro with a groupId of org.apache.ode (check the root pom).
> That
> > > > sort
> > > > of reduces the maven uncertainty principle. A bit.
> > > >
> > > > Matthieu
> > > >
> > > > On 12/13/06, Lance Waterman <la...@gmail.com> wrote:
> > > > >
> > > > > I just pulled down the latest SVN image and I'm seeing most of the
> > > unit
> > > > > tests failing with parsing errors. Anyone else seeing this?
> > > > >
> > > > > NAMESPACE_ERR: An attempt is made to create or change an object in
> a
> > > way
> > > > > which is incorrect with regard to namespaces.
> > > > >
> > > > > Lance
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
> > --
> > CTO, Intalio
> > http://www.intalio.com
> >
> >
>
>
--
CTO, Intalio
http://www.intalio.com
Re: Latest Updates
Posted by Lance Waterman <la...@gmail.com>.
It doesn't look like a vendetta thing. Not sure why the plugin can't find
the tests - I'll take a look.
Lance
On 12/13/06, Assaf Arkin <ar...@intalio.com> wrote:
>
> When I run bpel-test, I get "no tests to run". By design, or does Maven
> have
> something personal against me?
>
> Assaf
>
> On 12/13/06, Lance Waterman <la...@gmail.com> wrote:
> >
> > Thanks Matthieu - yes I was trying to run the bpel-test. I'll check my
> > Xalan
> > jar.
> >
> >
> > On 12/13/06, Matthieu Riou <ma...@gmail.com> wrote:
> > >
> > > I have before. Which tests are failing, the bpel-test ones?
> > >
> > > This is due to a bad version of Xalan. All Maven servers I've found
> have
> > a
> > > Xalan 2.7.0 producing weird exceptions like this one (for a quick
> check,
> > > the
> > > standard Xalan distro is 2.9MB whereas the corrupted one downloaded by
> > > Maven
> > > is 2.6MB). To get rid of this problem I've added our own Xalan
> directly
> > > from
> > > the distro with a groupId of org.apache.ode (check the root pom). That
> > > sort
> > > of reduces the maven uncertainty principle. A bit.
> > >
> > > Matthieu
> > >
> > > On 12/13/06, Lance Waterman <la...@gmail.com> wrote:
> > > >
> > > > I just pulled down the latest SVN image and I'm seeing most of the
> > unit
> > > > tests failing with parsing errors. Anyone else seeing this?
> > > >
> > > > NAMESPACE_ERR: An attempt is made to create or change an object in a
> > way
> > > > which is incorrect with regard to namespaces.
> > > >
> > > > Lance
> > > >
> > > >
> > >
> > >
> >
> >
>
>
> --
> CTO, Intalio
> http://www.intalio.com
>
>
Re: Latest Updates
Posted by Assaf Arkin <ar...@intalio.com>.
When I run bpel-test, I get "no tests to run". By design, or does Maven have
something personal against me?
Assaf
On 12/13/06, Lance Waterman <la...@gmail.com> wrote:
>
> Thanks Matthieu - yes I was trying to run the bpel-test. I'll check my
> Xalan
> jar.
>
>
> On 12/13/06, Matthieu Riou <ma...@gmail.com> wrote:
> >
> > I have before. Which tests are failing, the bpel-test ones?
> >
> > This is due to a bad version of Xalan. All Maven servers I've found have
> a
> > Xalan 2.7.0 producing weird exceptions like this one (for a quick check,
> > the
> > standard Xalan distro is 2.9MB whereas the corrupted one downloaded by
> > Maven
> > is 2.6MB). To get rid of this problem I've added our own Xalan directly
> > from
> > the distro with a groupId of org.apache.ode (check the root pom). That
> > sort
> > of reduces the maven uncertainty principle. A bit.
> >
> > Matthieu
> >
> > On 12/13/06, Lance Waterman <la...@gmail.com> wrote:
> > >
> > > I just pulled down the latest SVN image and I'm seeing most of the
> unit
> > > tests failing with parsing errors. Anyone else seeing this?
> > >
> > > NAMESPACE_ERR: An attempt is made to create or change an object in a
> way
> > > which is incorrect with regard to namespaces.
> > >
> > > Lance
> > >
> > >
> >
> >
>
>
--
CTO, Intalio
http://www.intalio.com
Re: Latest Updates
Posted by Lance Waterman <la...@gmail.com>.
Thanks Matthieu - yes I was trying to run the bpel-test. I'll check my Xalan
jar.
On 12/13/06, Matthieu Riou <ma...@gmail.com> wrote:
>
> I have before. Which tests are failing, the bpel-test ones?
>
> This is due to a bad version of Xalan. All Maven servers I've found have a
> Xalan 2.7.0 producing weird exceptions like this one (for a quick check,
> the
> standard Xalan distro is 2.9MB whereas the corrupted one downloaded by
> Maven
> is 2.6MB). To get rid of this problem I've added our own Xalan directly
> from
> the distro with a groupId of org.apache.ode (check the root pom). That
> sort
> of reduces the maven uncertainty principle. A bit.
>
> Matthieu
>
> On 12/13/06, Lance Waterman <la...@gmail.com> wrote:
> >
> > I just pulled down the latest SVN image and I'm seeing most of the unit
> > tests failing with parsing errors. Anyone else seeing this?
> >
> > NAMESPACE_ERR: An attempt is made to create or change an object in a way
> > which is incorrect with regard to namespaces.
> >
> > Lance
> >
> >
>
>
Re: Latest Updates
Posted by Matthieu Riou <ma...@gmail.com>.
I have before. Which tests are failing, the bpel-test ones?
This is due to a bad version of Xalan. All Maven servers I've found have a
Xalan 2.7.0 producing weird exceptions like this one (for a quick check, the
standard Xalan distro is 2.9MB whereas the corrupted one downloaded by Maven
is 2.6MB). To get rid of this problem I've added our own Xalan directly from
the distro with a groupId of org.apache.ode (check the root pom). That sort
of reduces the maven uncertainty principle. A bit.
Matthieu
On 12/13/06, Lance Waterman <la...@gmail.com> wrote:
>
> I just pulled down the latest SVN image and I'm seeing most of the unit
> tests failing with parsing errors. Anyone else seeing this?
>
> NAMESPACE_ERR: An attempt is made to create or change an object in a way
> which is incorrect with regard to namespaces.
>
> Lance
>
>