You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by Ulhas Bhole <ap...@gmail.com> on 2008/03/04 16:52:03 UTC
Fwd: Test failure on ServiceMix 3.2 branch
Hi All,
I am trying to build Servicemix 3.2 and getting test failure in
deployables/serviceengines/servicemix-lwcontainer.
Test org.apache.servicemix.lwcontainer.LwContainerComponentTest is trying
to look for the servicemix-quartz-3.2.2-SNAPSHOT-installer.zip in default
~/.m2/repository location whereas my repository is located in non-default
location and is specified in maven settings.xml
Does anyone came across such problem? If yes, what's the
solution/workaround? I have attached failure log file here.
Regards,
Ulhas Bhole
Re: Test failure on ServiceMix 3.2 branch
Posted by Bruce Snyder <br...@gmail.com>.
On Wed, Mar 5, 2008 at 5:35 AM, Ulhas Bhole <ap...@gmail.com> wrote:
> I have the fix now and raised a JIRA issue
> https://issues.apache.org/activemq/browse/SM-1262
> I will attach the patch shortly.
Thanks for the patch, Ulhas. I've committed it to both the trunk and
the 3.2 branch.
Bruce
--
perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
Apache ActiveMQ - http://activemq.org/
Apache Camel - http://activemq.org/camel/
Apache ServiceMix - http://servicemix.org/
Apache Geronimo - http://geronimo.apache.org/
Blog: http://bruceblog.org/
Re: Test failure on ServiceMix 3.2 branch
Posted by Ulhas Bhole <ap...@gmail.com>.
I have the fix now and raised a JIRA issue
https://issues.apache.org/activemq/browse/SM-1262
I will attach the patch shortly.
Regards,
Ulhas Bhole
On Tue, Mar 4, 2008 at 4:58 PM, Ulhas Bhole <ap...@gmail.com> wrote:
> Thanks Guillaume,
> For the quick pointer. I will follow it and try to get it fixed.
>
> Regards,
>
> Ulhas Bhole
>
>
> On Tue, Mar 4, 2008 at 4:53 PM, Guillaume Nodet <gn...@gmail.com> wrote:
>
> > I suspect the test to reference the library directly.
> > Looking at the code, it seems to come from the
> >
> > core/servicemix-core/src/main/java/org/apache/servicemix/jbi/container/DeploySupport.java
> > class which looks for an artifact in the local repo.
> > I guess it could be improved to be more compliant with maven behavior
> > and find your local
> > repo ...
> >
> > On Tue, Mar 4, 2008 at 5:42 PM, Ulhas Bhole <ap...@gmail.com>
> > wrote:
> > > Hi Guillaume,
> > >
> > > I am surely planning to dig into the issue and if it needs patch will
> > > provide one. However, I am unable to understand why all other
> > dependencies
> > > are pickedup correctly from the non-default local repository and
> > fails on
> > > this one. I manually checked that the dependency it is failing on is
> > there
> > > in the local repository it is just that it's in non-default location.
> > >
> > > Regards,
> > >
> > > Ulhas Bhole
> > >
> > >
> > >
> > > On Tue, Mar 4, 2008 at 3:58 PM, Guillaume Nodet <gn...@gmail.com>
> > wrote:
> > >
> > > > The only workaround is to build without tests or disable the
> > failing test
> > > > by modifying the pom.
> > > > However, i think there is a way to fix the test by using the
> > > > maven-dependency-plugin which allows to copy some dependencies
> > > > in a known folder inside target for example so that the tests can
> > use it.
> > > > THis is obviously the best solution.
> > > > Fancy providing a patch for that ?
> > > >
> > > > On Tue, Mar 4, 2008 at 4:52 PM, Ulhas Bhole <ap...@gmail.com>
> > wrote:
> > > > >
> > > > >
> > > > > Hi All,
> > > > >
> > > > > I am trying to build Servicemix 3.2 and getting test failure in
> > > > > deployables/serviceengines/servicemix-lwcontainer.
> > > > >
> > > > > Test org.apache.servicemix.lwcontainer.LwContainerComponentTestis
> > > > trying
> > > > > to look for the servicemix-quartz-3.2.2-SNAPSHOT-installer.zip in
> > > > default
> > > > > ~/.m2/repository location whereas my repository is located in
> > > > non-default
> > > > > location and is specified in maven settings.xml
> > > > >
> > > > > Does anyone came across such problem? If yes, what's the
> > > > > solution/workaround? I have attached failure log file here.
> > > > >
> > > > > Regards,
> > > > >
> > > > > Ulhas Bhole
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Cheers,
> > > > Guillaume Nodet
> > > > ------------------------
> > > > Blog: http://gnodet.blogspot.com/
> > > >
> > >
> >
> >
> >
> > --
> > Cheers,
> > Guillaume Nodet
> > ------------------------
> > Blog: http://gnodet.blogspot.com/
> >
>
>
Re: Test failure on ServiceMix 3.2 branch
Posted by Ulhas Bhole <ap...@gmail.com>.
Thanks Guillaume,
For the quick pointer. I will follow it and try to get it fixed.
Regards,
Ulhas Bhole
On Tue, Mar 4, 2008 at 4:53 PM, Guillaume Nodet <gn...@gmail.com> wrote:
> I suspect the test to reference the library directly.
> Looking at the code, it seems to come from the
>
> core/servicemix-core/src/main/java/org/apache/servicemix/jbi/container/DeploySupport.java
> class which looks for an artifact in the local repo.
> I guess it could be improved to be more compliant with maven behavior
> and find your local
> repo ...
>
> On Tue, Mar 4, 2008 at 5:42 PM, Ulhas Bhole <ap...@gmail.com> wrote:
> > Hi Guillaume,
> >
> > I am surely planning to dig into the issue and if it needs patch will
> > provide one. However, I am unable to understand why all other
> dependencies
> > are pickedup correctly from the non-default local repository and fails
> on
> > this one. I manually checked that the dependency it is failing on is
> there
> > in the local repository it is just that it's in non-default location.
> >
> > Regards,
> >
> > Ulhas Bhole
> >
> >
> >
> > On Tue, Mar 4, 2008 at 3:58 PM, Guillaume Nodet <gn...@gmail.com>
> wrote:
> >
> > > The only workaround is to build without tests or disable the failing
> test
> > > by modifying the pom.
> > > However, i think there is a way to fix the test by using the
> > > maven-dependency-plugin which allows to copy some dependencies
> > > in a known folder inside target for example so that the tests can use
> it.
> > > THis is obviously the best solution.
> > > Fancy providing a patch for that ?
> > >
> > > On Tue, Mar 4, 2008 at 4:52 PM, Ulhas Bhole <ap...@gmail.com>
> wrote:
> > > >
> > > >
> > > > Hi All,
> > > >
> > > > I am trying to build Servicemix 3.2 and getting test failure in
> > > > deployables/serviceengines/servicemix-lwcontainer.
> > > >
> > > > Test org.apache.servicemix.lwcontainer.LwContainerComponentTest is
> > > trying
> > > > to look for the servicemix-quartz-3.2.2-SNAPSHOT-installer.zip in
> > > default
> > > > ~/.m2/repository location whereas my repository is located in
> > > non-default
> > > > location and is specified in maven settings.xml
> > > >
> > > > Does anyone came across such problem? If yes, what's the
> > > > solution/workaround? I have attached failure log file here.
> > > >
> > > > Regards,
> > > >
> > > > Ulhas Bhole
> > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Cheers,
> > > Guillaume Nodet
> > > ------------------------
> > > Blog: http://gnodet.blogspot.com/
> > >
> >
>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
>
Re: Test failure on ServiceMix 3.2 branch
Posted by Guillaume Nodet <gn...@gmail.com>.
I suspect the test to reference the library directly.
Looking at the code, it seems to come from the
core/servicemix-core/src/main/java/org/apache/servicemix/jbi/container/DeploySupport.java
class which looks for an artifact in the local repo.
I guess it could be improved to be more compliant with maven behavior
and find your local
repo ...
On Tue, Mar 4, 2008 at 5:42 PM, Ulhas Bhole <ap...@gmail.com> wrote:
> Hi Guillaume,
>
> I am surely planning to dig into the issue and if it needs patch will
> provide one. However, I am unable to understand why all other dependencies
> are pickedup correctly from the non-default local repository and fails on
> this one. I manually checked that the dependency it is failing on is there
> in the local repository it is just that it's in non-default location.
>
> Regards,
>
> Ulhas Bhole
>
>
>
> On Tue, Mar 4, 2008 at 3:58 PM, Guillaume Nodet <gn...@gmail.com> wrote:
>
> > The only workaround is to build without tests or disable the failing test
> > by modifying the pom.
> > However, i think there is a way to fix the test by using the
> > maven-dependency-plugin which allows to copy some dependencies
> > in a known folder inside target for example so that the tests can use it.
> > THis is obviously the best solution.
> > Fancy providing a patch for that ?
> >
> > On Tue, Mar 4, 2008 at 4:52 PM, Ulhas Bhole <ap...@gmail.com> wrote:
> > >
> > >
> > > Hi All,
> > >
> > > I am trying to build Servicemix 3.2 and getting test failure in
> > > deployables/serviceengines/servicemix-lwcontainer.
> > >
> > > Test org.apache.servicemix.lwcontainer.LwContainerComponentTest is
> > trying
> > > to look for the servicemix-quartz-3.2.2-SNAPSHOT-installer.zip in
> > default
> > > ~/.m2/repository location whereas my repository is located in
> > non-default
> > > location and is specified in maven settings.xml
> > >
> > > Does anyone came across such problem? If yes, what's the
> > > solution/workaround? I have attached failure log file here.
> > >
> > > Regards,
> > >
> > > Ulhas Bhole
> > >
> > >
> >
> >
> >
> > --
> > Cheers,
> > Guillaume Nodet
> > ------------------------
> > Blog: http://gnodet.blogspot.com/
> >
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
Re: Test failure on ServiceMix 3.2 branch
Posted by Ulhas Bhole <ap...@gmail.com>.
Hi Guillaume,
I am surely planning to dig into the issue and if it needs patch will
provide one. However, I am unable to understand why all other dependencies
are pickedup correctly from the non-default local repository and fails on
this one. I manually checked that the dependency it is failing on is there
in the local repository it is just that it's in non-default location.
Regards,
Ulhas Bhole
On Tue, Mar 4, 2008 at 3:58 PM, Guillaume Nodet <gn...@gmail.com> wrote:
> The only workaround is to build without tests or disable the failing test
> by modifying the pom.
> However, i think there is a way to fix the test by using the
> maven-dependency-plugin which allows to copy some dependencies
> in a known folder inside target for example so that the tests can use it.
> THis is obviously the best solution.
> Fancy providing a patch for that ?
>
> On Tue, Mar 4, 2008 at 4:52 PM, Ulhas Bhole <ap...@gmail.com> wrote:
> >
> >
> > Hi All,
> >
> > I am trying to build Servicemix 3.2 and getting test failure in
> > deployables/serviceengines/servicemix-lwcontainer.
> >
> > Test org.apache.servicemix.lwcontainer.LwContainerComponentTest is
> trying
> > to look for the servicemix-quartz-3.2.2-SNAPSHOT-installer.zip in
> default
> > ~/.m2/repository location whereas my repository is located in
> non-default
> > location and is specified in maven settings.xml
> >
> > Does anyone came across such problem? If yes, what's the
> > solution/workaround? I have attached failure log file here.
> >
> > Regards,
> >
> > Ulhas Bhole
> >
> >
>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
>
Re: Test failure on ServiceMix 3.2 branch
Posted by Guillaume Nodet <gn...@gmail.com>.
The only workaround is to build without tests or disable the failing test
by modifying the pom.
However, i think there is a way to fix the test by using the
maven-dependency-plugin which allows to copy some dependencies
in a known folder inside target for example so that the tests can use it.
THis is obviously the best solution.
Fancy providing a patch for that ?
On Tue, Mar 4, 2008 at 4:52 PM, Ulhas Bhole <ap...@gmail.com> wrote:
>
>
> Hi All,
>
> I am trying to build Servicemix 3.2 and getting test failure in
> deployables/serviceengines/servicemix-lwcontainer.
>
> Test org.apache.servicemix.lwcontainer.LwContainerComponentTest is trying
> to look for the servicemix-quartz-3.2.2-SNAPSHOT-installer.zip in default
> ~/.m2/repository location whereas my repository is located in non-default
> location and is specified in maven settings.xml
>
> Does anyone came across such problem? If yes, what's the
> solution/workaround? I have attached failure log file here.
>
> Regards,
>
> Ulhas Bhole
>
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/