sipXconfig maven2 based build

[Damian Krzeminski <damian (at) pingtel.com>]

Michael Steinmann wrote:
> Damian Krzeminski wrote:
> > As a part of effort of cleaning dependencies and making sipXconfig build
> > more distro independent (it is java after all) I am experimenting with
> > maven2 based build.
>
> Not sure about 'more distro independent'. I couldn't find maven2
> packages for most of the distros I've been packaging for lately.
>
>
> Debian
> - no deb, lots of missing dependencies
> - Debian ITP has been deleted because of inactivity for more than 600 days
>   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=188782
>   http://people.debian.org/~avdyk/maven.html
>
> Ubuntu
> - no deb
>
> Gentoo
> - maven2 only in testing
>   http://packages.gentoo.org/search/?sstring=maven
>
> OpenSuSE
> - nothing found
>
>
> While it's perfectly possible for developers and a 'manual' packager to
> install build dependency packages by hand, this is not so for the
> automatic build process used by the major distros. A package needs to
> have all of its build dependencies available to the distro build host
> when the source package is dumped into it.
>
> Relying on unsupported tools makes it extremely difficult (if not
> impossible) to get the package into the distro. A package relying on ten
>  or so unsupported Java packages will never make it into Debian Sarge.
>
>
> If we want to support sipX on more distros in the future we probably
> need to draw a sheet with current and future build and runtime
> dependencies in order to be able to track them and make informed choices
> about whether or not we want to introduce them. This would also make it
> more efficient to push and track the progress of build dependencies
> inclusion in the different distros.
>
>
> --
> mike

I fully agree with everything you said in last paragraph. Since you 
tracking this project for more than a year now, I think you will admit 
that it did get easier to build and install.

I would not dream about making build process worse. I think that too 
many sipX developers and users know where I live by now :-)
(also see: http://sipxconfig.blogspot.com/2006/01/new-hope-ie-maven2.html)

I'd like to clarify something about maven. If we have maven based build 
(and this is quite a big if still), maven will be the only sipXconfig 
dependency. Maven is for java what auto tools + yum/apt/yast are for 
C/C++ based software.

At the moment to compile sipXconfig you have to install and download 
about various 10 packages. In addition we distribute quite a few .jars 
in the lib directory. If we switch to maven, there will be only maven 
package.

While I did check that support for maven is planned in jpackage which 
will take care of many distros and as you pointed out, I am not really 
worried about it much.
Even without native package maven is extremely easy to install - see my 
last e-mail.

Anyway, make/ant based build does not go anywhere without developers 
community approval. If maven build proves to be no easier that what we 
have today, you will not hear about it again.

Damian

_______________________________________________
sipx-dev mailing list
sipx-dev (at) list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-dev