Comment 18 for bug 427539

Hi,

Also, I tried earlier in the cycle to get the maven package in a good shape, and this is the mail exchange I had with ttx:
fabrice wrote:

> > As spoken in irc, I've been trying to get the maven packages in a good
> > shape. You can see in my ppa (1), the actual status of the 'required'
> > packages to build (or try to build) the maven packages, at least the
> > maven-plugin-tools one.

Hey Fabrice,

Thanks for your efforts on this. From a release schedule perspective, we
are one week before Karmic feature freeze and adding support now for a
new build system (and syncing 21 packages in the process) is not a good
idea. Furthermore from a Ubuntu server perspective, we are looking for
some stability in the Java infrastructure as we do last-minute
pre-freeze work on adding new software that depends on it. FWIW, we are
considering a Java library update freeze for the next cycle (that would
occur roughly one month before feature freeze) to enforce this required
stability.

That's why I recommended keeping all the new maven goodness out of
karmic and let it mature in Debian unstable, so that it's ready for the
karmic+1 sync/merge period.

The interest of having maven support is to enable packaging stuff that
depends on maven, which won't be done for karmic anyway. It sounds right
to enable the stack at the very beginning of the karmic+1 cycle to
potentially allow for maven-based packaging during that cycle.

> > For the moment, I have 21 packages, but as Onkar told me, we shouldn't
> > sync for the moment packages outside the 'maven' world that uses
> > maven-repo-helper:

Yes, that's what I told Onkar: I don't really mind syncing new packages
since they won't interfere with anything (even if I fail to see a good
reason to do so one week before featurefreeze)...

> > [...]
> > As you can see, 6 packages are required for the moment, to have a chance
> > to build maven-plugin-tools (and still misses some, as it still FTBFS
> > for the moment).
> >
> > So my question is: is it worth trying to sync all the maven packages, as
> > they will FTBFS without that at least 6 non maven packages? Or there is
> > some magic that can be applied to the packages that required this ones
> > so that they can build without the updated version of this 6 packages?
> > Or the maven packages will stays as-is?

...but if there is no point in syncing this part without also updating
the non-maven packages, or worse, if it creates FTBFS in the process,
then I don't see why we would sync it incompletely. And I would just
concentrate on testing it/improving it in unstable in the next months
and make sure it's ready for sync at the opening of karmic+1.

-- Thierry Carrez Ubuntu server team