From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Q4oa8-0006iZ-LQ for garchives@archives.gentoo.org; Wed, 30 Mar 2011 06:08:41 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4F1EB1C0A8 for ; Wed, 30 Mar 2011 06:08:40 +0000 (UTC) Received: from mail-ww0-f53.google.com (mail-ww0-f53.google.com [74.125.82.53]) by pigeon.gentoo.org (Postfix) with ESMTP id 430E71C089 for ; Wed, 30 Mar 2011 05:11:57 +0000 (UTC) Received: by wwj40 with SMTP id 40so1016727wwj.10 for ; Tue, 29 Mar 2011 22:11:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=a1mUpVKajVNEApfLKLRjb8UDvxWDh6UARbQ+9Yzk+D8=; b=b/7ZfYPl2X1yqbXYFrGsF5WtLFfy7WrikIRS0XqC4/w27d5OPGQjwLsXqTfiUUO09U 1qlLX4w8FebtFmXJePqbF9zQnzJMQsEPEsiwV2xCXWKHjORZSpYhU/EuaJVG8LWCcgwc VxqiTPpcV3qyNJYL6T3fBtQ+dydt/5iytFMRQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=N4Br848237sevSb5ULnWL3dBAkKNYAAswISKPBMv6t+j21j0AaqcC/+QyipI3kfPCt +RyzORf09Hc+l2vjFT1+vwNRLINtyTiJKLAr8jPMhW8Tic24zeN4MQcekzLzOmrUT1Dd rQEUf79lmI7hk20emDTtel2Lb05MChdqkuDnA= Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-soc@lists.gentoo.org Reply-to: gentoo-soc@lists.gentoo.org MIME-Version: 1.0 Received: by 10.217.6.202 with SMTP id y52mr208238wes.42.1301461914560; Tue, 29 Mar 2011 22:11:54 -0700 (PDT) Received: by 10.216.36.141 with HTTP; Tue, 29 Mar 2011 22:11:54 -0700 (PDT) In-Reply-To: <1720E82E-2E96-4B08-BD53-EEF092200AE7@gmail.com> References: <1720E82E-2E96-4B08-BD53-EEF092200AE7@gmail.com> Date: Wed, 30 Mar 2011 10:41:54 +0530 Message-ID: Subject: Re: [gentoo-soc] [GSoC] Maven integration for Gentoo ebuilds From: Kasun Gajasinghe To: "gentoo-soc@lists.gentoo.org" Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: X-Archives-Hash: db9cdc6272cb1507adfcb7c69774be4c On Tue, Mar 29, 2011 at 8:41 PM, Kasun Gajasinghe wrote: > > > On 29 Mar 2011, at 09:37, Serkan Kaba wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> On 29-03-2011 06:47, Kasun Gajasinghe wrote: >>> >>> I'd like to know how the dependencies will be handled by maven based >>> ebuilds. Can you let me know the difference between dependencies >>> specified in Maven's POM file, and ebuild's dependencies? Are both >>> should be same? Since, Maven's POM contains the unique artifacts IDs >>> (with the combination of groupId, artifactId, version) which points to >>> a _binary_ jar, how should the developers who write _ebuilds_ specify >>> it? I got to know that dependencies are also ebuilds under gentoo i.e. >>> no binaries. >> >> POM dependencies can be too restrictive sometimes, like depending on a >> specific version. We should be depending on any version (or sometimes >> with >=,<=) as long as the package compiles and runs fine with it. > > I've come across a package called JPackage which does the job of retrieving > a jar from /usr/share/java and return it to use by maven. It neglects the > version numbers as well. > > >>> I've been going through the Ralph's (nick: sera ) suggested eclass >>> [1]. It turned out to be very useful. (sera, I got your name from [1], >>> hope it's correct! :) ). Because maven offline building is the biggest >>> issue Gentoo is currently facing, As Petteri suggested, I've been >>> going through to see how other distributions handle this. I see that >>> both in sera's eclass and in Debian's MavenRepoSpec [2], that they >>> specify a variable which points to a maven local-repository location. >>> Ralph's eclass specified MAVEN_REPO_DIR="${T}/maven-repo/" while >>> Debian has REPO=/usr/share/maven-repo. Since the file-system will be >>> read-only for ebuilds, and ebuilds should be built offline, what's the >>> purpose of this? >> >> We then still need to add symlinks to jars during build time in there >> which is an "access violation" in sand box > > Ok. Then the viable option is to have to generate the maven directory > structure inside a folder named ${T}/maven-repo. We can do the symlinking > through that, and we won't face any access violation since the writing > happens in the sandbox. > Ubuntu too have proposed a similar solution. I'm away from my machine, I'll > provide the links to it as well as for the JPackage soon if it you all may > want to check it out! For the JPackage see [1]. [1] doesn't give a formatted output though. Properly formatted version is to [2] Ubuntu's maven support specification is at [3]. I've started writing a proposal. I'll upload it to melange, when it comes to a good state. [1] http://www.jpackage.org/cgi-bin/viewvc.cgi/jpackage/src/jpackage-utils/doc/jpackage-1.5-policy.xhtml?revision=1.2&view=markup [2] http://dl.dropbox.com/u/4783109/gentoo-maven-integration/read/%5Bjpackage%5D%20Contents%20of%20%20src%20jpackage-utils%20doc%20jpackage-1.5-policy.html [3] https://wiki.ubuntu.com/JavaTeam/Specs/MavenSupportSpec Thanks, --Kasun > > Thanks, > Kasun > >> >> - -- >> Sincerely, >> Serkan KABA >> Gentoo Developer >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v2.0.17 (GNU/Linux) >> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ >> >> iEYEARECAAYFAk2RWvIACgkQRh6X64ivZaLfkgCfVF99iZaa6Pa+dTlC4cjuLvZd >> ILkAn34OooCvrNy6uu9yEg4bua/q7X6G >> =staW >> -----END PGP SIGNATURE----- >> > > -- ~~~*******'''''''''''''*******~~~ Kasun Gajasinghe, University of Moratuwa, Sri Lanka. Blog: http://kasunbg.blogspot.com Twitter: http://twitter.com/kasunbg