You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commons-dev@ws.apache.org by Ajith Ranabahu <aj...@gmail.com> on 2006/08/25 09:00:01 UTC
[Axis2][Axiom]Axiom-***.jar not updated?
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: commons-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: commons-dev-help@ws.apache.org
Re: [Axis2][Axiom]Axiom-***.jar not updated?
Posted by Eran Chinthaka <ch...@opensource.lk>.
+1.
Ajith Ranabahu wrote:
> Hi,
> What happened was this
>
> 1. Secpolicy module had axiom-combined jar as a dependency where as
> all other modules (I'm talking about maven modules in the Axis2 build)
> had the seperate Axiom jars.
>
> 2. When you do a create-lib it copies dependancies of all the modules
> to the lib folder. Since there were the three seperate axiom jars and
> the combined axiom jar as dependancies 4 axiom jars were copied into
> the lib folder.
>
> 3.Once you get to use that lib it wasn't predictable where the axiom
> classes get picked up. ant build picked it from the combined jar and
> IDEA picked it up from the seperate jars
>
> So here is the outcome
>
> 1. All Axis guys should make sure (Specially when new modules are
> introduced) that the dependancies are made to the three seperate jars
> and not the combined one (for axiom)
>
> 2. If no one is using the combined axiom jar anymore we should not
> generate it as part of the build and remove any existing
> axiom-SNAPSHOT.jar from the repositories
>
> I hope this makes it clear about all this business in the axiom build :)
>
> Ajith
>
>
> On 8/26/06, Eran Chinthaka <ch...@opensource.lk> wrote:
>> Ajith Ranabahu wrote:
>> > 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 !
>>
>> I'm ok with for using/generating separate jars. But I can not understand
>> how this can answer your initial concern.
>>
>> I did a change in axiom, I think that being not reflected in the repo
>> was the problem, but that change affected both the api and impl(s). How
>> can separating those jars solve the problem?
>>
>> >
>> > Anyone has strong views about the combined jar ;)
>>
>> Hehe.
>>
>> -- Chinthaka
>>
>>
>>
>>
>
>
Re: [Axis2][Axiom]Axiom-***.jar not updated?
Posted by Eran Chinthaka <ch...@opensource.lk>.
+1.
Ajith Ranabahu wrote:
> Hi,
> What happened was this
>
> 1. Secpolicy module had axiom-combined jar as a dependency where as
> all other modules (I'm talking about maven modules in the Axis2 build)
> had the seperate Axiom jars.
>
> 2. When you do a create-lib it copies dependancies of all the modules
> to the lib folder. Since there were the three seperate axiom jars and
> the combined axiom jar as dependancies 4 axiom jars were copied into
> the lib folder.
>
> 3.Once you get to use that lib it wasn't predictable where the axiom
> classes get picked up. ant build picked it from the combined jar and
> IDEA picked it up from the seperate jars
>
> So here is the outcome
>
> 1. All Axis guys should make sure (Specially when new modules are
> introduced) that the dependancies are made to the three seperate jars
> and not the combined one (for axiom)
>
> 2. If no one is using the combined axiom jar anymore we should not
> generate it as part of the build and remove any existing
> axiom-SNAPSHOT.jar from the repositories
>
> I hope this makes it clear about all this business in the axiom build :)
>
> Ajith
>
>
> On 8/26/06, Eran Chinthaka <ch...@opensource.lk> wrote:
>> Ajith Ranabahu wrote:
>> > 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 !
>>
>> I'm ok with for using/generating separate jars. But I can not understand
>> how this can answer your initial concern.
>>
>> I did a change in axiom, I think that being not reflected in the repo
>> was the problem, but that change affected both the api and impl(s). How
>> can separating those jars solve the problem?
>>
>> >
>> > Anyone has strong views about the combined jar ;)
>>
>> Hehe.
>>
>> -- Chinthaka
>>
>>
>>
>>
>
>
Re: [Axis2][Axiom]Axiom-***.jar not updated?
Posted by Ajith Ranabahu <aj...@gmail.com>.
Hi,
What happened was this
1. Secpolicy module had axiom-combined jar as a dependency where as
all other modules (I'm talking about maven modules in the Axis2 build)
had the seperate Axiom jars.
2. When you do a create-lib it copies dependancies of all the modules
to the lib folder. Since there were the three seperate axiom jars and
the combined axiom jar as dependancies 4 axiom jars were copied into
the lib folder.
3.Once you get to use that lib it wasn't predictable where the axiom
classes get picked up. ant build picked it from the combined jar and
IDEA picked it up from the seperate jars
So here is the outcome
1. All Axis guys should make sure (Specially when new modules are
introduced) that the dependancies are made to the three seperate jars
and not the combined one (for axiom)
2. If no one is using the combined axiom jar anymore we should not
generate it as part of the build and remove any existing
axiom-SNAPSHOT.jar from the repositories
I hope this makes it clear about all this business in the axiom build :)
Ajith
On 8/26/06, Eran Chinthaka <ch...@opensource.lk> wrote:
> Ajith Ranabahu wrote:
> > 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 !
>
> I'm ok with for using/generating separate jars. But I can not understand
> how this can answer your initial concern.
>
> I did a change in axiom, I think that being not reflected in the repo
> was the problem, but that change affected both the api and impl(s). How
> can separating those jars solve the problem?
>
> >
> > Anyone has strong views about the combined jar ;)
>
> Hehe.
>
> -- Chinthaka
>
>
>
>
--
Ajith Ranabahu
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2][Axiom]Axiom-***.jar not updated?
Posted by Eran Chinthaka <ch...@opensource.lk>.
Ajith Ranabahu wrote:
> 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 !
I'm ok with for using/generating separate jars. But I can not understand
how this can answer your initial concern.
I did a change in axiom, I think that being not reflected in the repo
was the problem, but that change affected both the api and impl(s). How
can separating those jars solve the problem?
>
> Anyone has strong views about the combined jar ;)
Hehe.
-- Chinthaka
Re: [Axis2][Axiom]Axiom-***.jar not updated?
Posted by Ajith Ranabahu <aj...@gmail.com>.
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 <da...@gmail.com> wrote:
> Ajith,
>
> I think we should not generate/use the combined jar.
>
> -- dims
>
> On 8/25/06, Ajith Ranabahu <aj...@gmail.com> 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: axis-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> >
> >
>
>
> --
> Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
Ajith Ranabahu
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2][Axiom]Axiom-***.jar not updated?
Posted by Ajith Ranabahu <aj...@gmail.com>.
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 <da...@gmail.com> wrote:
> Ajith,
>
> I think we should not generate/use the combined jar.
>
> -- dims
>
> On 8/25/06, Ajith Ranabahu <aj...@gmail.com> 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: axis-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> >
> >
>
>
> --
> Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
Ajith Ranabahu
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: commons-dev-help@ws.apache.org
Re: [Axis2][Axiom]Axiom-***.jar not updated?
Posted by Davanum Srinivas <da...@gmail.com>.
Ajith,
I think we should not generate/use the combined jar.
-- dims
On 8/25/06, Ajith Ranabahu <aj...@gmail.com> 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: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: commons-dev-help@ws.apache.org
Re: [Axis2][Axiom]Axiom-***.jar not updated?
Posted by Davanum Srinivas <da...@gmail.com>.
Ajith,
I think we should not generate/use the combined jar.
-- dims
On 8/25/06, Ajith Ranabahu <aj...@gmail.com> 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: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org