Upgrade to Axis2 1.4.1

[Tammo van Lessen <tv...@gmail.com>]

Hi devs,

I just upgraded our trunk to Axis2 1.4.1. As aligning Axis2 dependencies
with Ode's dependencies is quite a pain, I decided to do a small
refactoring in the Rakefile so that the Axis dependencies are now so to
say a first class citizen. I think this is reasonable as Axis is the IMO
most important IL implementation and also the one that has most external
dependencies.

So I added a AXIS2_DEPS (which perhaps better reads AXIS2_FULL) which
defines all Axis2 dependencies that are found in their war distribution.
Later, in the Ode dependencies, I replaced all direct dependencies by
links to the version declared in Axis2. That way, our dependencies are
always aligned with Axis2. If we don't want/need this behavior for
certain dependencies, we can simply replace the lookup by a direct
artifact spec.

So, to update the dependencies, simply go through the AXIS2_DEPS list
and insert/updated dependencies according to Axis2.

If new dependencies are added to Ode, first check whether they are also
in Axis2.

I'm not really convinced to base Ode's dependency management completely
on Axis2 but I believe maintaining Ode is way easier that way.

What do you think?

Cheers,
  Tammo

Re: Upgrade to Axis2 1.4.1

[Matthieu Riou <ma...@offthelip.org>]

On Thu, Aug 28, 2008 at 3:10 PM, Alexis Midon <mi...@intalio.com> wrote:

> On Wed, Aug 27, 2008 at 11:13 AM, Tammo van Lessen <tvanlessen@gmail.com
> >wrote:
>
> > Hi devs,
> >
> > I just upgraded our trunk to Axis2 1.4.1. As aligning Axis2 dependencies
> > with Ode's dependencies is quite a pain, I decided to do a small
> > refactoring in the Rakefile so that the Axis dependencies are now so to
> > say a first class citizen. I think this is reasonable as Axis is the IMO
> > most important IL implementation and also the one that has most external
> > dependencies.
> >
> > So I added a AXIS2_DEPS (which perhaps better reads AXIS2_FULL) which
> > defines all Axis2 dependencies that are found in their war distribution.
> > Later, in the Ode dependencies, I replaced all direct dependencies by
> > links to the version declared in Axis2. That way, our dependencies are
> > always aligned with Axis2. If we don't want/need this behavior for
> > certain dependencies, we can simply replace the lookup by a direct
> > artifact spec.
> >
> > So, to update the dependencies, simply go through the AXIS2_DEPS list
> > and insert/updated dependencies according to Axis2.
> >
> > If new dependencies are added to Ode, first check whether they are also
> > in Axis2.
> >
> > I'm not really convinced to base Ode's dependency management completely
> > on Axis2 but I believe maintaining Ode is way easier that way.
> >
>
> well, this is just a build file. It doesn't look like an issue to me.
>
>
> >
> > What do you think?
> >
>
> I can't see any wrong with that. it makes axis2 dependencies clearly
> visible. To me it has many advantages: centralized dep. in one place, save
> some typing, prevent from removing axi2 dep. by accident...
>

+1

And if it gets painful for some unsuspected reason, we can always tweak it,
it's not Maven.

Matthieu


>
> Alexis
>
>
>
> > Cheers,
> >   Tammo
> >
>

Re: Upgrade to Axis2 1.4.1

[Alexis Midon <mi...@intalio.com>]

On Wed, Aug 27, 2008 at 11:13 AM, Tammo van Lessen <tv...@gmail.com>wrote:

> Hi devs,
>
> I just upgraded our trunk to Axis2 1.4.1. As aligning Axis2 dependencies
> with Ode's dependencies is quite a pain, I decided to do a small
> refactoring in the Rakefile so that the Axis dependencies are now so to
> say a first class citizen. I think this is reasonable as Axis is the IMO
> most important IL implementation and also the one that has most external
> dependencies.
>
> So I added a AXIS2_DEPS (which perhaps better reads AXIS2_FULL) which
> defines all Axis2 dependencies that are found in their war distribution.
> Later, in the Ode dependencies, I replaced all direct dependencies by
> links to the version declared in Axis2. That way, our dependencies are
> always aligned with Axis2. If we don't want/need this behavior for
> certain dependencies, we can simply replace the lookup by a direct
> artifact spec.
>
> So, to update the dependencies, simply go through the AXIS2_DEPS list
> and insert/updated dependencies according to Axis2.
>
> If new dependencies are added to Ode, first check whether they are also
> in Axis2.
>
> I'm not really convinced to base Ode's dependency management completely
> on Axis2 but I believe maintaining Ode is way easier that way.
>

well, this is just a build file. It doesn't look like an issue to me.


>
> What do you think?
>

I can't see any wrong with that. it makes axis2 dependencies clearly
visible. To me it has many advantages: centralized dep. in one place, save
some typing, prevent from removing axi2 dep. by accident...

Alexis



> Cheers,
>   Tammo
>