Re: maven-repo, ivy, javahelper, fosdem

[Ludovic Claude <ludovic.claude54@googlemail.com>]

Hello,

Thomas Koch a écrit :
> Hi,
> 
> I started a packaging hadoop[1] and tried to use ivy. Thereby a couple of 
> questions / difficulties arised.
> 
> Ivy spits some errors on me, already asked upstream for help[2], but maybe 
> someone of you could also help.
> 
> I'm packaging a hadoop dependency, libxmlenc-java[3]. It doesn't come with a 
> pom.xml. Is there any automation/template to help me create a pom?
> Do you have an example of how to use mh_install* with debhelper? 
> Is there still a need for javahelper if I can also use mh_installjar?
> Shouldn't javahelper and maven_repo_helper be merged?

javahelper and maven-repo-helper should be harmonized as much as
possible, I need to look into this, and learn more about debhelper 7.
I think that you need to add 2 actions on a post install hook:
- mh_linkjar to create links to the jars installed in /usr/share/java by
jh_installlibs into /usr/share/maven-repo
- mh_installpoms to install the POM files into the Maven repository

> Shouldn't there be a policy that all java stuff should also be published to 
> /usr/share/maven-repo?

The policy should mention that this repository now exists, but it should
not be mandatory to install libraries there. Of course, when you package
a project built with Maven that's missing the required POM and jar files
in the Maven repository, it's more work on you.

> Shouldn't there be a policy that all packages should have a "debian" version 
> in the debian maven repo?

There should be something like that, yes, but with some freedom left on
the packager:
- use debian version if the library has a nice history of keeping
backwards compatibility
- use versions such as 1.x or 2.x if there are several major versions
with incompatibilities, but backwards compatibility is maintained within
the same version line.
- use the full version (1.1.4) if there is a known issue which makes a
specific version of the library usable. I used that for libitext1-java
because libdoxia required a very specific version of that library to work.

> The ivysettings.xml[4] I built for hadoop seems pretty standard to me and I'd 
> propose to include the resolvers part in maven-repo-helper or somewhere alike.
> 
Good idea, I will include it. Please file a bug report on that package.

> There'll be a Java Devroom at FOSDEM. Should we meet their to discuss Debian-
> Java stuff?[5]
> 
I'm still thinking about it, but Brussels is not too far and quite nice
for a week-end, so maybe.

> [1] http://git.debian.org/?p=users/thkoch-guest/hadoop.git
> [2] http://mail-archives.apache.org/mod_mbox/hadoop-common-
> user/201001.mbox/%3C201001071048.50372.thomas@koch.ro%3E
> [3] http://git.debian.org/?p=pkg-java/libxmlenc-java.git
> [4] http://git.debian.org/?p=users/thkoch-
> guest/hadoop.git;a=blob;f=debian/ivysettings.xml
> [5] http://wiki.debian.org/Java/DevJam/2010/FosdemProposedTalks
> 
> Thanks for any help,
> 
> Thomas Koch, http://www.koch.ro
> 
>