Re: [Axis2][Axiom]Axiom-***.jar not updated?

Hi Dims,
Yes - essentially as good practice we will stick to the use of
seperate jars. I'm not very sure how others will feel about dumping
the combined jar though !

Anyone has strong views about the combined jar ;)

Ajith

On 8/25/06, Davanum Srinivas <[email protected]> wrote:
> Ajith,
>
> I think we should not generate/use the combined jar.
>
> -- dims
>
> On 8/25/06, Ajith Ranabahu <[email protected]> wrote:
> > Hi,
> > I've figured out in a very painful way that there has been a
> > dependency in the secpolicy module to the axiom.***.jar and due to
> > that the axiom.***.jar gets copied to the libs folder when you do a
> > create-lib. However it seems that the axiom-***.jar is not uptodate
> > (at least in the repositories) and that causes a problem in certain
> > scenarios where the composite jar is picked up first in the class
> > path!
> >
> > So these are my conclusions
> >
> > 1. Axis2 guys should always refer to the seperate jars in their
> > implementations as good practice
> >
> > 2. Axiom guys (?) should have a check (perhaps the new m2 build)
> > whether the combined jar is created properly. It could be my problem
> > but it is safe to just make sure :)
> >
> >
> > Thanks
> > --
> > Ajith Ranabahu
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> >
> >
>
>
> --
> Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>


-- 
Ajith Ranabahu