[New Package Freeze Upstream] maven2-2.0.7

i was about to file an issue for this, myself. maven is rapidly supplanting ant because it's a complete project management system.

I'd also like to see a package for maven.

This is actually the first piece of software I wanted that I haven't found in the package repo.

+1

Now that Java is OpenSource, having a Maven2 package is a must !

Let's embrace Java! ... and maven is becoming a standard nowadays...

I'd also love to see this packaged

maven2 is now in the Debian NEW queue

This would require following
https://wiki.ubuntu.com/FreezeExceptionProcess

I took a quick test to compile maven2 in gutsy and it would need some work to get it done in time:

rebuild:
jtidy (in the archive, needs a rebuild - initial build failed, but works now)
plexus-classworlds (in the archive, needs a rebuild - initial build failed, but works now)
plexus-component-api (in the archive, needs a rebuild - dep-wait libplexus-classworlds-java)
plexus-interactivity-api (in the archive, needs a rebuild - dep-wait libplexus-component-api-java)
plexus-container-default (in the archive, needs a rebuild - dep-wait libclassworlds-java)
wagon (in the archive, needs a rebuild because - dep-wait jtidy)

sync:
maven-ant-helper (3) (not in the archive, needs sync)
doxia (1.0-alpha-7-1) (not in the archive, needs sync)
modello (1.0-alpha-8-1) (not in the archive, needs sync)
plexus-i18n (1.0-beta-7+svn6675-1) (not in the archive, needs sync)
plexus-velocity (1.1.6-1) (not in the archive, needs sync)

classworlds (1.0.1-1.1 --> 1.1-alpha-2-1 (binaries never been built, no rdepends, good candidate for sync; required by plexus-container-default)
bouncycastle 1.33-4 --> 1.37-1 (rdepends only libbcpg-java-gcj, good candidate for sync)
plexus-interactivity-api (1.0-alpha-6-1 --> 1.0-alpha-6-2, sync required; maven2 binary dependency)

As soon as I saw the news about maven2 being uploaded to debian I downloaded the dsc file (couldn't find the deb) and successfully made the deb using packages from ubuntu or packages from debian when no equivalent existed on Ubuntu, so it's possible to add maven2 to ubuntu, but some dependencies are needed also. Upgrades to existent packages are not necessary.

I double the request for maven being made available for ubuntu. Go, go, go ;-)

R. A. Rivas Diaz,

classworlds in ubuntu FTBFS, the related Debian bug is http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=397566. At least that needs to get fixed first, but sync should be safe because libbcpg-java has only libbcpg-java-gcj as reverse depends.

plexus-interactivity-api (1.0-alpha-6-2) is a strict dependency of maven2 binary, so it needs a sync too.

You could ask one of the motu-uvf members if this effort is still possible for gutsy and how to proceed. You probably need to make separate requests for each package that is NEW or needs a sync, but it's better to ask from someone who knows things better. I'd like to see maven2 in gutsy too.

In my opinion it is to late for this magnitude of change. All of those new packages would need manual review by archive admins before they could be accepted. This looks like a very good feature improvement for Hardy Herron (Gutsy +1), but introducing this magnitude of new package review late in the cycle would be disruptive to the other late release cycle work that the archive admins have to do.

This package set would be a good candidate for a PPA archive if someone was interested in setting that up.

Also, for a UVFe, Confirmed means approved. Setting back to New.

@Scott,

I initially thought on building it onto my PPA, but I'm relatively new to the inner workings of Debian/Ubuntu packages. If someone is kind enough to point me on the right directions I'd be pleased to get Maven kicking on Ubuntu.

Also if clear instructions are provided I could do my best to get it working on a unstable deb repository or whatnot.

I'm not completely familiar with PPA usage. I'd recommend asking on the
#launchpad IRC channel as it's part of their system.

http://help.launchpad.net/PPAQuickStart

In complete agreement with ScottK for this one.

We release in 4 weeks. Even if we did approve this, there's no way the archive admins would have time to review this.

Let's grab this for hardy.

I am fairly new to using Ubuntu. Does this mean that we won't see a maven2 package available via apt-get until the hardy release? Isn't that 6-7 months away?

Yes, although once it's in the Hardy archive, it could be requested to be added to gutsy-backports and available that way significantly sooner.

Scott,

Is there a way to go to Hardy already. I'm really interested on pursuing this.

For know everyone is working on getting gutsy ready (especially for this damn hardware thrown on the market the last few months).
Hardy development will start at an open kickoff meeting at the end of October (in the campus hotel of a certain US university I believe), we won't see even an alpha for some time.
But an extract-and-set-a-softlink package that can be installed manually so easily is really far from a reason to go beyond a distro's bleeding edge ;-))
Besides, I am almost sure we will see a maven package in a PPA soon after gutsy's final release.

I've uploaded maven2 (and the missing dependencies) in to my PPA for Gutsy users. Packages are from Debian unstable.
If anyone is interested to have maven2 for Feisty, do say so and I'll try to do that as well.

PPA repository is:
deb http://ppa.launchpad.net/mlind/ubuntu gutsy main
deb-src http://ppa.launchpad.net/mlind/ubuntu gutsy main

Thanks Matti for publishing your packages ;-)

I'd like to nominate this package for gutsy backports.

TIA, Wolfgang

Mlind, your packages work great! Thanks a lot.

Possible to import perhaps for Hardy? Mlind ?

There is no package for maven in Ubuntu so I am marking it Invalid for Gutsy Backports.

But, please, please, please add this package at least to hardy.

  TIA,

    Wolfgang

The package freeze for Hardy is a ways off still, isn't it? It's a bit odd marking this as invalid now when you don't know for sure that it won't ultimately wind up in Hardy. Are you guaranteeing that it won't be in Hardy?

maven2 + dependencies are already in Hardy repository. maven2 is currently in manual dep-wait mode and won't be build until one of the buildd admins poke it or new version gets uploaded. If someone needs it for hardy now, go into #ubuntu-devel and ask someone to re-try the package.

Just for the record Maven 2.0.8 was released on November 27, 2007 http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=13139

maven2 has reached hardy

The following packages have unmet dependencies:
  pbuilder-satisfydepends-dummy: Depends: libclassworlds-java which is a virtual package.
                                 Depends: libdoxia-java which is a virtual package.
                                 Depends: libmodello-java which is a virtual package.
                                 Depends: libplexus-container-default-java which is a virtual package.
                                 Depends: libplexus-interactivity-api-java which is a virtual package.
                                 Depends: libwagon-java which is a virtual package.
                                 Depends: maven-ant-helper which is a virtual package.

I don't really know if there are any new policies here, but with so many unmet dependancies, I don't think we can backport it for the moment, except if someone were to backport all these packages...

"invalid" still isn't the appropriate resolution because it's a valid request. resolve as "wontfix" if you don't feel like fixing this so it can be revisited later.

and the obvious solution is to backport the deps as well, since none of them are in the ubuntu toolchain

Missing dependencies have rdepends only for maven2, other maven2 dependency if I remember correctly, so this is a safe backport.

Dependencies that are in the Gutsy archive, but were built on a development stage that resulted FTBFS (these build fine now):
jtidy
plexus-classworlds
plexus-component-api
plexus-container-default
plexus-interactivity-api
wagon

Packages that would require backporting:
plexus-velocity
plexus-i18n
doxia
modello
maven-ant-helper
maven2

Packages that should be backported even though in the archive:
wagon (see Debian bug #449188)

This would make 6+1 packages to backport. I can help by submitting bugs of each dependency that needs backporting if necessary.

Ok, I have a question. Is this bug the request to backport maven2 to gutsy? I tried to submit a new bug request for the backport, and this is the one I found. It seems to me that most of the comments are geared towards putting maven2 in Hardy. Do I need to create another request, or will this comment serve as a reminder that we want maven2 backported to gutsy? :)

Thanks,

Ok, based on mlind's comments, looks like this is a 7-package backport?

No need to (in fact, for the love of my Firefox plese don't) file 7 separate backport bugs. Instead, please proceed with testing each of the 7 packages to backport, including *what version was tested* for each.

Thanks.

libclassworlds-java 1.1-final-1 requires backporting maven-ant-helper >=3, that builds fine, but because of backport renaming, it doesn't want to compile

libdoxia-java 1.0-alpha-7-1 requires libwagon-java, libplexus-i18n-java, libmodello-java and libplexus-velocity-java

libmodello-java 1.0-alpha-8-1 requires libplexus-container-default-java, libplexus-container-default-java-doc and maven-ant-helper

libplexus-container-default-java 1.0-alpha-9-stable-1-2 requires libclassworlds-java, maven-ant-helper

libplexus-interactivity-api-java 1.0-alpha-6-2 requires libplexus-component-api-java and libplexus-component-api-java-doc

libwagon-java 1.0-beta-2-2 requires libjtidy-java, libjtidy-java-doc, libplexus-classworlds-java, libplexus-classworlds-java-doc, libplexus-component-api-java, libplexus-component-api-java-doc, libplexus-interactivity-api-java, libplexus-interactivity-api-java-doc

libplexus-i18n-java 1.0-beta-7+svn6675-1 requires maven-ant-helper and libplexus-container-default-java

libplexus-velocity-java 1.1.6-1 requires libplexus-container-default-java

libplexus-component-api-java 1.0+svn6316-1 requires libplexus-classworlds-java, libplexus-classworlds-java-doc

libplexus-classworlds-java 1.2+svn5720-1 builds without help, which is a bit of a miracle.

I'll sum all the results in a following commentary as it will help me too to help what we need to do

Built succesfully :
libplexus-classworlds-java 1.2+svn5720-1
libplexus-component-api-java 1.0+svn6316-1
libplexus-interactivity-api-java 1.0-alpha-6-2
libjtidy-java 7+svn20070309-1

Need to be modified in order to work with backported maven :
libclassworlds-java 1.1-final-1
libmodello-java 1.0-alpha-8-1
libplexus-container-default-java 1.0-alpha-9-stable-1-2
libplexus-i18n-java 1.0-beta-7+svn6675-1

After these modifications have been done, the backports will need to be done following these steps :
1 - maven-ant-helper 3, libplexus-classworlds-java 1.2+svn5720-1, libplexus-component-api-java 1.0+svn6316-1, libplexus-interactivity-api-java 1.0-alpha-6-2, libjtidy-java 7+svn20070309-1
2 - libclassworlds-java 1.1-final-1 (and -doc)
3 - libplexus-container-default-java (and -doc)
4 - libmodello-java 1.0-alpha-8-1, libplexus-velocity-java 1.1.6-1, libplexus-i18n-java
5 - libwagon-java 1.0-beta-2-2
6 - libdoxia-java 1.0-alpha-7-1

And finally, maven2.

Jdong, if you could do the magic for the packages to modify and backport them with maven, I would then be able to do all the following steps (and hope all go well)

Some of the required packages are already in Gutsy archive, but have FTBFS previously. Is it possible to give back these packages ?

FYI: Maven 2.0.9 has been released upstream.