From mefoster at gmail.com Mon Nov 2 10:04:10 2009 From: mefoster at gmail.com (Mary Ellen Foster) Date: Mon, 2 Nov 2009 10:04:10 +0000 Subject: [fedora-java] Importing packages from jpackage -- version? Message-ID: I've got a bunch of packages basically ready to import from JPackage into Fedora. One thing I'm wondering, though: what should the version of the imported packages be? Assume that the jpackage version is 0:1.5.5-2 (most jpackage packages have Epoch: 0). If there's a newer version of the library (often the case) -- say 2.1 -- it's pretty straightforward: the Fedora package will become 2.1-1 (no Epoch). As I understand it, that means that anyone who currently has the jpackage version will be silently upgraded to the Fedora version, which is probably good. If there's not a newer version, though, I'm not sure what to do: 1.5.5-1 (it's the first Fedora package)? 1.5.5-2 (same as jpackage)? 1.5.5-3 (provide a clean upgrade path? And what if the jpackage one has a non-zero Epoch? Thanks for any advice, MEF -- Mary Ellen Foster -- http://www.macs.hw.ac.uk/~mef3/ Interaction Lab -- http://www.macs.hw.ac.uk/InteractionLab School of Mathematical and Computer Sciences, Heriot-Watt University Heriot-Watt University is a Scottish charity registered under charity number SC000278 From akurtako at redhat.com Mon Nov 2 10:14:35 2009 From: akurtako at redhat.com (Alexander Kurtakov) Date: Mon, 2 Nov 2009 12:14:35 +0200 Subject: [fedora-java] Importing packages from jpackage -- version? In-Reply-To: References: Message-ID: <200911021214.36107.akurtako@redhat.com> > I've got a bunch of packages basically ready to import from JPackage > into Fedora. One thing I'm wondering, though: what should the version > of the imported packages be? > > Assume that the jpackage version is 0:1.5.5-2 (most jpackage packages > have Epoch: 0). If there's a newer version of the library (often the > case) -- say 2.1 -- it's pretty straightforward: the Fedora package > will become 2.1-1 (no Epoch). As I understand it, that means that > anyone who currently has the jpackage version will be silently > upgraded to the Fedora version, which is probably good. Yes, that's the right thing to do. > > If there's not a newer version, though, I'm not sure what to do: > 1.5.5-1 (it's the first Fedora package)? 1.5.5-2 (same as jpackage)? > 1.5.5-3 (provide a clean upgrade path? I personally prefer to provide clean upgrade path i.e. 1.5.5-3 . > > And what if the jpackage one has a non-zero Epoch? And same here we should try to get jpackage packages updated whenever we provide newer package/integrate the package in Fedora so we should use the jpp package Epoch. There maybe others that will disagree with me but this the way to go if we want our users to update to our (Fedora packages) with minimal effort. Alex > > Thanks for any advice, > > MEF > From overholt at redhat.com Mon Nov 2 13:36:38 2009 From: overholt at redhat.com (Andrew Overholt) Date: Mon, 2 Nov 2009 08:36:38 -0500 Subject: [fedora-java] [giallu@gmail.com: transaction warnings with Java packages] Message-ID: <20091102133637.GB2180@redhat.com> ----- Forwarded message from Gianluca Sforna ----- > Date: Mon, 2 Nov 2009 11:31:22 +0100 > From: Gianluca Sforna > To: For testers of Fedora Core development releases > > Subject: transaction warnings with Java packages > > I tried installing bootchart on my rawhide system and it seems there's > something fishy during the transaction; here's a snippet: > > Running Transaction > Installing : jakarta-commons-cli-1.1-5.fc12.x86_64 1/2 > /usr/bin/rebuild-gcj-db: line 6: /usr/bin/gcj-dbtool: Permission denied > /usr/bin/rebuild-gcj-db: line 6: /usr/bin/gcj-dbtool: Permission denied > dirname: missing operand > Try `dirname --help' for more information. > mkdir: missing operand > Try `mkdir --help' for more information. > /usr/bin/rebuild-gcj-db: line 13: /usr/bin/gcj-dbtool: Permission denied > xargs: /usr/bin/gcj-dbtool: Permission denied > /usr/bin/rebuild-gcj-db: line 6: /usr/bin/gcj-dbtool: Permission denied > Installing : bootchart-0.9-11.fc12.x86_64 2/2 > /sbin/grubby --update-kernel=/boot/vmlinuz-2.6.31.5-96.fc12.x86_64 > --args=init=/sbin/bootchartd > /usr/bin/rebuild-gcj-db: line 6: /usr/bin/gcj-dbtool: Permission denied > /usr/bin/rebuild-gcj-db: line 6: /usr/bin/gcj-dbtool: Permission denied > dirname: missing operand > Try `dirname --help' for more information. > mkdir: missing operand > Try `mkdir --help' for more information. > /usr/bin/rebuild-gcj-db: line 13: /usr/bin/gcj-dbtool: Permission denied > xargs: /usr/bin/gcj-dbtool: Permission denied > /usr/bin/rebuild-gcj-db: line 6: /usr/bin/gcj-dbtool: Permission denied > > > I looked in bugzilla but I didn't find it reported. Maybe I'm the only > one seeing this? > > > > > -- > Gianluca Sforna > > http://morefedora.blogspot.com > http://www.linkedin.com/in/gianlucasforna > > -- > fedora-test-list mailing list > fedora-test-list at redhat.com > To unsubscribe: > https://www.redhat.com/mailman/listinfo/fedora-test-list ----- End forwarded message ----- From caolanm at redhat.com Mon Nov 2 13:42:11 2009 From: caolanm at redhat.com (=?ISO-8859-1?Q?Caol=E1n?= McNamara) Date: Mon, 02 Nov 2009 13:42:11 +0000 Subject: [fedora-java] [giallu@gmail.com: transaction warnings with Java packages] In-Reply-To: <20091102133637.GB2180@redhat.com> References: <20091102133637.GB2180@redhat.com> Message-ID: <1257169331.5568.31050.camel@Vain> On Mon, 2009-11-02 at 08:36 -0500, Andrew Overholt wrote: > ----- Forwarded message from Gianluca Sforna ----- > > /usr/bin/rebuild-gcj-db: line 6: /usr/bin/gcj-dbtool: Permission denied > > /usr/bin/rebuild-gcj-db: line 6: /usr/bin/gcj-dbtool: Permission denied There was a similar report recently for OOo, i.e. https://bugzilla.redhat.com/show_bug.cgi?id=532239 i.e. permission denied on a lot of gij/libgcj related things. C. From fnasser at redhat.com Mon Nov 2 14:51:45 2009 From: fnasser at redhat.com (Fernando Nasser) Date: Mon, 02 Nov 2009 09:51:45 -0500 Subject: [fedora-java] Importing packages from jpackage -- version? In-Reply-To: <200911021214.36107.akurtako@redhat.com> References: <200911021214.36107.akurtako@redhat.com> Message-ID: <4AEEF201.9010500@redhat.com> Alexander Kurtakov wrote: >> I've got a bunch of packages basically ready to import from JPackage >> into Fedora. One thing I'm wondering, though: what should the version >> of the imported packages be? >> >> Assume that the jpackage version is 0:1.5.5-2 (most jpackage packages >> have Epoch: 0). If there's a newer version of the library (often the >> case) -- say 2.1 -- it's pretty straightforward: the Fedora package >> will become 2.1-1 (no Epoch). As I understand it, that means that >> anyone who currently has the jpackage version will be silently >> upgraded to the Fedora version, which is probably good. >> > > Yes, that's the right thing to do. > > >> If there's not a newer version, though, I'm not sure what to do: >> 1.5.5-1 (it's the first Fedora package)? 1.5.5-2 (same as jpackage)? >> 1.5.5-3 (provide a clean upgrade path? >> > > I personally prefer to provide clean upgrade path i.e. 1.5.5-3 . > The original idea, when the 'jpp' was dropped, was to add a '.NN' so we know the last sync point. So it would actually be 1.5.5-2.1 > >> And what if the jpackage one has a non-zero Epoch? >> > > And same here we should try to get jpackage packages updated whenever we > provide newer package/integrate the package in Fedora so we should use the jpp > package Epoch. > > There maybe others that will disagree with me but this the way to go if we > want our users to update to our (Fedora packages) with minimal effort. > > Alex > >> Thanks for any advice, >> >> MEF >> >> > > -- > fedora-devel-java-list mailing list > fedora-devel-java-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-devel-java-list > > From fedora at matbooth.co.uk Mon Nov 2 15:03:07 2009 From: fedora at matbooth.co.uk (Mat Booth) Date: Mon, 2 Nov 2009 15:03:07 +0000 Subject: [fedora-java] Importing packages from jpackage -- version? In-Reply-To: <4AEEF201.9010500@redhat.com> References: <200911021214.36107.akurtako@redhat.com> <4AEEF201.9010500@redhat.com> Message-ID: <9497e9990911020703v636474bft36e4446b44f17725@mail.gmail.com> 2009/11/2 Fernando Nasser : > Alexander Kurtakov wrote: >>> >>> I've got a bunch of packages basically ready to import from JPackage >>> into Fedora. One thing I'm wondering, though: what should the version >>> of the imported packages be? >>> >>> Assume that the jpackage version is 0:1.5.5-2 (most jpackage packages >>> have Epoch: 0). If there's a newer version of the library (often the >>> case) -- say 2.1 -- it's pretty straightforward: the Fedora package >>> will become 2.1-1 (no Epoch). As I understand it, that means that >>> anyone who currently has the jpackage version will be silently >>> upgraded to the Fedora version, which is probably good. >>> >> >> Yes, that's the right thing to do. >> >> >>> >>> If there's not a newer version, though, I'm not sure what to do: >>> 1.5.5-1 (it's the first Fedora package)? 1.5.5-2 (same as jpackage)? >>> 1.5.5-3 (provide a clean upgrade path? >>> >> >> I personally prefer to provide clean upgrade path i.e. 1.5.5-3 . >> > > The original idea, when the 'jpp' was dropped, ?was to add a '.NN' so we > know the last sync point. > > So it would actually be > > 1.5.5-2.1 > > I think that went out the window when the mass rebuilds indiscriminately incremented the release number. -- Mat Booth A: Because it destroys the order of the conversation. Q: Why shouldn't you do it? A: Posting your reply above the original message. Q: What is top-posting? From mefoster at gmail.com Mon Nov 2 19:44:13 2009 From: mefoster at gmail.com (Mary Ellen Foster) Date: Mon, 2 Nov 2009 19:44:13 +0000 Subject: [fedora-java] Soprano/Sesame2: first batch of packages up for review Message-ID: Dear all, I'm currently working on getting the Sesame2 backend for Soprano building from source on Fedora (see http://www.openrdf.org/ for details on Sesame). This involves a lot of dependencies, mostly because Sesame depends on Spring -- see https://fedoraproject.org/wiki/MaryEllenFoster/SopranoSesame for the gory details. I've just put up an initial set of leaf-node packages for review. All of these are imported from JPackage (http://www.jpackage.org), so hopefully the reviews won't take too long. All of the review bugs are linked from https://fedoraproject.org/wiki/MaryEllenFoster/SopranoSesame#Current_review_requests Thanks for anyone who can do a review, and I'm willing to review other outstanding packages (especially Java ones) in return. MEF -- Mary Ellen Foster -- http://www.macs.hw.ac.uk/~mef3/ Interaction Lab -- http://www.macs.hw.ac.uk/InteractionLab School of Mathematical and Computer Sciences, Heriot-Watt University Heriot-Watt University is a Scottish charity registered under charity number SC000278 From mefoster at gmail.com Mon Nov 2 20:35:10 2009 From: mefoster at gmail.com (Mary Ellen Foster) Date: Mon, 2 Nov 2009 20:35:10 +0000 Subject: [fedora-java] Re: Soprano/Sesame2: first batch of packages up for review In-Reply-To: References: Message-ID: 2009/11/2 Mary Ellen Foster : > I'm currently working on getting the Sesame2 backend for Soprano > building from source on Fedora (see http://www.openrdf.org/ for > details on Sesame). This involves a lot of dependencies, mostly > because Sesame depends on Spring -- see > https://fedoraproject.org/wiki/MaryEllenFoster/SopranoSesame for the > gory details. Argh ... I work on this for a while, finally decide to send something out to the world, and then immediately realise that (a) Sesame2 might not actually crucially depend on Spring at all -- it's only in one sub-package, and (b) many of the packages I did work on actually had existing review requests and/or were previously in Fedora and were retired (thanks to Jason Tibbitts for pointing me at those). So please hold off on the list for now; I'll probably be modifying things shortly. Argh again ... :) MEF -- Mary Ellen Foster -- http://www.macs.hw.ac.uk/~mef3/ Interaction Lab -- http://www.macs.hw.ac.uk/InteractionLab School of Mathematical and Computer Sciences, Heriot-Watt University Heriot-Watt University is a Scottish charity registered under charity number SC000278 From greno at verizon.net Fri Nov 6 16:49:42 2009 From: greno at verizon.net (Gerry Reno) Date: Fri, 06 Nov 2009 11:49:42 -0500 Subject: [fedora-java] maven2: Non existent: org.apache.maven.toolchain.ToolchainManager Message-ID: <4AF453A6.3030602@verizon.net> I am building Axis2 on F12 using maven2. When I run mvn install, I get errors like this: Non existent: org.apache.maven.toolchain.ToolchainManager Can someone shed some light on what is missing here? This is with maven2 2.0.8 rpm install. -Gerry From orion at cora.nwra.com Fri Nov 6 22:13:08 2009 From: orion at cora.nwra.com (Orion Poplawski) Date: Fri, 06 Nov 2009 15:13:08 -0700 Subject: [fedora-java] maven2: Non existent: org.apache.maven.toolchain.ToolchainManager In-Reply-To: <4AF453A6.3030602@verizon.net> References: <4AF453A6.3030602@verizon.net> Message-ID: <4AF49F74.10207@cora.nwra.com> On 11/06/2009 09:49 AM, Gerry Reno wrote: > I am building Axis2 on F12 using maven2. When I run mvn install, I get > errors like this: > Non existent: org.apache.maven.toolchain.ToolchainManager > > Can someone shed some light on what is missing here? This is with maven2 > 2.0.8 rpm install. > Looks like toolchains may have been introduced in 2.0.9. Looks like maven2 is pretty out of date in Fedora. Website mentions 2.0.10, 2.1.0, and 2.2.1. -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA/CoRA Division FAX: 303-415-9702 3380 Mitchell Lane orion at cora.nwra.com Boulder, CO 80301 http://www.cora.nwra.com From greno at verizon.net Fri Nov 6 22:40:11 2009 From: greno at verizon.net (Gerry Reno) Date: Fri, 06 Nov 2009 17:40:11 -0500 Subject: [fedora-java] maven2: Non existent: org.apache.maven.toolchain.ToolchainManager In-Reply-To: <4AF49F74.10207@cora.nwra.com> References: <4AF453A6.3030602@verizon.net> <4AF49F74.10207@cora.nwra.com> Message-ID: <4AF4A5CB.3000606@verizon.net> Orion Poplawski wrote: > On 11/06/2009 09:49 AM, Gerry Reno wrote: >> I am building Axis2 on F12 using maven2. When I run mvn install, I get >> errors like this: >> Non existent: org.apache.maven.toolchain.ToolchainManager >> >> Can someone shed some light on what is missing here? This is with maven2 >> 2.0.8 rpm install. >> > > Looks like toolchains may have been introduced in 2.0.9. > > Looks like maven2 is pretty out of date in Fedora. Website mentions > 2.0.10, 2.1.0, and 2.2.1. > Yes, I just read the maven2 toolchain webpage. maven2 2.0.9 is the minimum to support toolchains. So we're SOL as far as Fedora. -Gerry From overholt at redhat.com Fri Nov 6 23:17:26 2009 From: overholt at redhat.com (Andrew Overholt) Date: Fri, 6 Nov 2009 18:17:26 -0500 Subject: [fedora-java] maven2: Non existent: org.apache.maven.toolchain.ToolchainManager In-Reply-To: <4AF4A5CB.3000606@verizon.net> References: <4AF453A6.3030602@verizon.net> <4AF49F74.10207@cora.nwra.com> <4AF4A5CB.3000606@verizon.net> Message-ID: <20091106231726.GB2933@redhat.com> * Gerry Reno [2009-11-06 17:40]: >> Looks like maven2 is pretty out of date in Fedora. Website mentions >> 2.0.10, 2.1.0, and 2.2.1. >> > Yes, I just read the maven2 toolchain webpage. maven2 2.0.9 is the > minimum to support toolchains. So we're SOL as far as Fedora. A few of us (dbhole, akurtakov, myself) are planning on trying to get 2.2.1 in shape for F-13. We know we're way out of date, but we're better off with 2.0.8 in F-12 than we were with 2.0.4 in F-11. We'll send a message here when we are starting and need some help. Andrew From greno at verizon.net Fri Nov 6 23:43:53 2009 From: greno at verizon.net (Gerry Reno) Date: Fri, 06 Nov 2009 18:43:53 -0500 Subject: [fedora-java] maven2: Non existent: org.apache.maven.toolchain.ToolchainManager In-Reply-To: <20091106231726.GB2933@redhat.com> References: <4AF453A6.3030602@verizon.net> <4AF49F74.10207@cora.nwra.com> <4AF4A5CB.3000606@verizon.net> <20091106231726.GB2933@redhat.com> Message-ID: <4AF4B4B9.7050900@verizon.net> Andrew Overholt wrote: > * Gerry Reno [2009-11-06 17:40]: > >>> Looks like maven2 is pretty out of date in Fedora. Website mentions >>> 2.0.10, 2.1.0, and 2.2.1. >>> >>> >> Yes, I just read the maven2 toolchain webpage. maven2 2.0.9 is the >> minimum to support toolchains. So we're SOL as far as Fedora. >> > > A few of us (dbhole, akurtakov, myself) are planning on trying to get > 2.2.1 in shape for F-13. We know we're way out of date, but we're > better off with 2.0.8 in F-12 than we were with 2.0.4 in F-11. > > We'll send a message here when we are starting and need some help. > > Andrew > > Thanks Andrew. How in the world did Fedora get so far back on maven2, axis2, and other apache packages? Shuttlesworth already has Eucalyptus (cloud computing) in Ubuntu which is what I've been trying to find a way to achieve with Fedora. But even the basic toolset that you need: maven2, axis2, axis2c, rampartc, is nowhere to be found in Fedora. So right now I'm forced to do all this with a whole bunch of tarball installs which is something that is insanity really when you're trying to work from an upgradeable package set. At the very least could some effort be put into getting us maven2 2.0.9 in F12? I think that way at least some progress could be made. As far as axis2, I've given up the jpackage rube-goldberg approach and am looking at something much simpler and easy-to-use. The last jpackage spec file I looked at had something like 2000 lines in it. If that doesn't tell you something is wrong with an approach, nothing will. Anyway, I'm trying to have no more than about 100 lines in the spec file so that a mere mortal human could understand the thing and maintain it. And I'm afraid that if we have to wait until F13 to get cloud computing going with Fedora we will have missed the entire boat by then. -Gerry From orion at cora.nwra.com Sat Nov 7 05:06:38 2009 From: orion at cora.nwra.com (Orion Poplawski) Date: Fri, 6 Nov 2009 22:06:38 -0700 (MST) Subject: [fedora-java] maven2: Non existent: org.apache.maven.toolchain.ToolchainManager In-Reply-To: <4AF4B4B9.7050900@verizon.net> References: <4AF453A6.3030602@verizon.net> <4AF49F74.10207@cora.nwra.com> <4AF4A5CB.3000606@verizon.net> <20091106231726.GB2933@redhat.com> <4AF4B4B9.7050900@verizon.net> Message-ID: <3560.97.124.128.38.1257570398.squirrel@www.cora.nwra.com> On Fri, November 6, 2009 4:43 pm, Gerry Reno wrote: > As far as axis2, I've given up the > jpackage rube-goldberg approach and am looking at something much simpler > and easy-to-use. The last jpackage spec file I looked at had something > like 2000 lines in it. If that doesn't tell you something is wrong with > an approach, nothing will. Anyway, I'm trying to have no more than about > 100 lines in the spec file so that a mere mortal human could understand > the thing and maintain it. I've found starting from "scratch" with the templates on the java packaging page reasonably straightforward. Maybe referring to the jpackage spec to help determine dependencies. -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA/CoRA Division FAX: 303-415-9702 3380 Mitchell Lane orion at cora.nwra.com Boulder, CO 80301 http://www.cora.nwra.com From overholt at redhat.com Sat Nov 7 13:55:42 2009 From: overholt at redhat.com (Andrew Overholt) Date: Sat, 7 Nov 2009 08:55:42 -0500 Subject: [fedora-java] maven2: Non existent: org.apache.maven.toolchain.ToolchainManager In-Reply-To: <4AF4B4B9.7050900@verizon.net> References: <4AF453A6.3030602@verizon.net> <4AF49F74.10207@cora.nwra.com> <4AF4A5CB.3000606@verizon.net> <20091106231726.GB2933@redhat.com> <4AF4B4B9.7050900@verizon.net> Message-ID: <20091107135542.GA7819@redhat.com> * Gerry Reno [2009-11-06 18:44]: > How in the world did Fedora get so far back on maven2, axis2, and > other apache packages? What was there was good enough and no one needed anything newer? No one working on it can certainly allow things to fall behind. Thanks for your interest in this area, Gerry. Andrew From oget.fedora at gmail.com Sun Nov 8 08:09:26 2009 From: oget.fedora at gmail.com (Orcan Ogetbil) Date: Sun, 8 Nov 2009 03:09:26 -0500 Subject: [fedora-java] Re: What's the deal with geronimo-specs? In-Reply-To: References: Message-ID: On Wed, Oct 21, 2009 at 9:23 AM, Mary Ellen Foster wrote: > 2009/10/21 Mary Ellen Foster : >> In the course of some other Java stuff, I noticed that the >> geronimo-specs package doesn't include Maven depmaps >> (https://bugzilla.redhat.com/show_bug.cgi?id=530088). I then decided >> to take a look at the actual SRPM itself to see how hard it would be >> to add things, and it looks like it's actually *very* old (version >> 1.0M2, released in August 2004) and it doesn't actually build from >> source any more on Rawhide (errors about javax.transaction.*). >> >> What's this package for, anyway? Would it hurt anything to package the >> 2.1.4 version (March 2009) instead? > > p.s. -- It looks like jpackage has a *much* newer package > (http://jpackage.org/browser/rpm.php?jppversion=5.0&id=7845) that > might be worth importing. I'll check that out now ... > > MEF > I made some research on this. Apparently we will need to import (at least) the following packages from jpackage to update our geronimo-specs: maven-release excalibur-avalon-framework excalibur-avalon-logkit mojo-maven2-plugin-idlj jacorb >= 0:2.3.0-17 mockobjects >= 0:0.09 mockobjects-jdk1.4-j2ee1.4 >= 0:0.09 ws-scout It smells like a lot of work. Who wants to team up for this? Orcan PS: I need the geronimo-specs updated to 1.2 in order to package this: https://sourceforge.net/projects/lmappletserver/ From mefoster at gmail.com Sun Nov 8 08:38:12 2009 From: mefoster at gmail.com (Mary Ellen Foster) Date: Sun, 8 Nov 2009 08:38:12 +0000 Subject: [fedora-java] Re: What's the deal with geronimo-specs? In-Reply-To: References: Message-ID: 2009/11/8 Orcan Ogetbil : > I made some research on this. Apparently we will need to import (at > least) the following packages from jpackage to update our > geronimo-specs: > maven-release I think this is just maven2-plugin-release (different name in Fedora). > excalibur-avalon-framework > excalibur-avalon-logkit These are already there, just without the "excalibur-" prefix. > mojo-maven2-plugin-idlj > jacorb >= 0:2.3.0-17 > mockobjects >= 0:0.09 > mockobjects-jdk1.4-j2ee1.4 >= 0:0.09 > ws-scout These probably do actually need to be imported ... MEF -- Mary Ellen Foster -- http://www.macs.hw.ac.uk/~mef3/ Interaction Lab -- http://www.macs.hw.ac.uk/InteractionLab School of Mathematical and Computer Sciences, Heriot-Watt University Heriot-Watt University is a Scottish charity registered under charity number SC000278 From oget.fedora at gmail.com Sun Nov 8 09:22:28 2009 From: oget.fedora at gmail.com (Orcan Ogetbil) Date: Sun, 8 Nov 2009 04:22:28 -0500 Subject: [fedora-java] Re: What's the deal with geronimo-specs? In-Reply-To: References: Message-ID: On Sun, Nov 8, 2009 at 3:38 AM, Mary Ellen Foster wrote: > 2009/11/8 Orcan Ogetbil: >> I made some research on this. Apparently we will need to import (at >> least) the following packages from jpackage to update our >> geronimo-specs: > >> maven-release > > I think this is just maven2-plugin-release (different name in Fedora). > >> excalibur-avalon-framework >> excalibur-avalon-logkit > > These are already there, just without the "excalibur-" prefix. > This is good news. >> mojo-maven2-plugin-idlj >> jacorb >= 0:2.3.0-17 >> mockobjects >= 0:0.09 >> mockobjects-jdk1.4-j2ee1.4 >= 0:0.09 >> ws-scout > > These probably do actually need to be imported ... > This is bad news. I checked these packages and some of them have at least 4-5 levels of dependencies that need to be imported. Some are really large packages and they need a lot of work to get Fedorized. Phew... Orcan From fedora at matbooth.co.uk Sun Nov 8 13:11:49 2009 From: fedora at matbooth.co.uk (Mat Booth) Date: Sun, 8 Nov 2009 13:11:49 +0000 Subject: [fedora-java] Eclipse plugin build failures on F13 Message-ID: <9497e9990911080511m2e125543ja6ae1c78e9cd0c57@mail.gmail.com> Hi, Looks like there's been a regression in F13, because this builds perfectly on F12: http://koji.fedoraproject.org/koji/taskinfo?taskID=1794704 This is the interesting part of the build log: /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.5.1.R35x_20090820/scripts/build.xml:35: The following error occurred while executing this line: /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.5.1.R35x_20090820/scripts/build.xml:91: The following error occurred while executing this line: /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.5.1.R35x_20090820/templates/package-build/customTargets.xml:19: The following error occurred while executing this line: java.io.FileNotFoundException: /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.5.1.R35x_20090820/scripts/${eclipse.pdebuild.scripts}/genericTargets.xml (No such file or directory) Why is ${eclipse.pdebuild.scripts} not defined? -- Mat Booth A: Because it destroys the order of the conversation. Q: Why shouldn't you do it? A: Posting your reply above the original message. Q: What is top-posting? From overholt at redhat.com Mon Nov 9 12:56:56 2009 From: overholt at redhat.com (Andrew Overholt) Date: Mon, 9 Nov 2009 07:56:56 -0500 Subject: [fedora-java] Eclipse plugin build failures on F13 In-Reply-To: <9497e9990911080511m2e125543ja6ae1c78e9cd0c57@mail.gmail.com> References: <9497e9990911080511m2e125543ja6ae1c78e9cd0c57@mail.gmail.com> Message-ID: <20091109125655.GA10831@redhat.com> > Why is ${eclipse.pdebuild.scripts} not defined? That variable is defined as an extension by the org.eclipse.pde.build bundle. If it's not defined, that bundle isn't being loaded. I do see that it got installed according to root.log but since it's in dropins, there's no diagnosis (awesome, I know). The next step is to see if we can duplicate locally. Please file a bug so we can track this. Thanks, Mat. Andrew From fedora at matbooth.co.uk Mon Nov 9 20:50:29 2009 From: fedora at matbooth.co.uk (Mat Booth) Date: Mon, 9 Nov 2009 20:50:29 +0000 Subject: [fedora-java] Eclipse plugin build failures on F13 In-Reply-To: <20091109125655.GA10831@redhat.com> References: <9497e9990911080511m2e125543ja6ae1c78e9cd0c57@mail.gmail.com> <20091109125655.GA10831@redhat.com> Message-ID: <9497e9990911091250y75547768rd34c9333dcc81890@mail.gmail.com> 2009/11/9 Andrew Overholt : >> Why is ${eclipse.pdebuild.scripts} not defined? > > That variable is defined as an extension by the org.eclipse.pde.build > bundle. ?If it's not defined, that bundle isn't being loaded. ?I do see > that it got installed according to root.log but since it's in dropins, > there's no diagnosis (awesome, I know). ?The next step is to see if we > can duplicate locally. ?Please file a bug so we can track this. ?Thanks, > Mat. > > Andrew > Done: https://bugzilla.redhat.com/show_bug.cgi?id=533935 I tried some local builds with the current F13 build of eclipse but couldn't get it to fail, which is a little disconcerting... -- Mat Booth A: Because it destroys the order of the conversation. Q: Why shouldn't you do it? A: Posting your reply above the original message. Q: What is top-posting? From dbhole at redhat.com Thu Nov 12 16:35:49 2009 From: dbhole at redhat.com (Deepak Bhole) Date: Thu, 12 Nov 2009 11:35:49 -0500 Subject: [fedora-java] What does the maven "groupId" mean? In-Reply-To: References: Message-ID: <20091112163549.GB5050@redhat.com> * Mary Ellen Foster [2009-10-22 10:31]: > Looking more closely at my current /etc/maven/maven2-depmap.xml file, > I notice a range of conventions for what fragments are called. Here > are a few examples: > Hi Mary, The target of the mapping contains a groupid, artifactid and version. The former two are used to determine where on the file system the jar is located. The convention is detailed in the readme: http://fedoraproject.org/wiki/Java/JPPMavenReadme Cheers, Deepak > For jakarta-commons-lang (from Fedora): > > > lang > lang > 2.3 > > > JPP > jakarta-commons-lang > 2.3 > > > > For jakarta-commons-logging (from JPackage): > > > commons-logging > commons-logging > 1.1 > > > JPP > commons-logging > 1.1 > > > > For ant (from Fedora): > > > org.apache.ant > ant > 1.7.1 > > > JPP > ant > 1.7.1 > > > > For aqute-bindlib (from Fedora): > > > biz.aQute > bndlib > 0.0.363 > > > JPP > aqute-bndlib > 0.0.363 > > > > So should the groupId be the package name, the full project name, the > sub-project name, or what? And what's the role of the "JPP" part in > all of this? There seem to be several different conventions going on > ... > > Thanks for any light you can shed, > > MEF > > -- > Mary Ellen Foster -- http://www.macs.hw.ac.uk/~mef3/ > Interaction Lab -- http://www.macs.hw.ac.uk/InteractionLab > School of Mathematical and Computer Sciences, Heriot-Watt University > > Heriot-Watt University is a Scottish charity registered under charity > number SC000278 > > -- > fedora-devel-java-list mailing list > fedora-devel-java-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-devel-java-list From dbhole at redhat.com Thu Nov 12 18:59:04 2009 From: dbhole at redhat.com (Deepak Bhole) Date: Thu, 12 Nov 2009 13:59:04 -0500 Subject: [fedora-java] jdepend-maven-plugin In-Reply-To: <870180fe0910231505y51c09a99p5bc871c5d8719a57@mail.gmail.com> References: <870180fe0910231505y51c09a99p5bc871c5d8719a57@mail.gmail.com> Message-ID: <20091112185903.GC5258@redhat.com> * Jerry James [2009-10-23 18:06]: > I'm still trying to get jakarta-commons-lang to build with maven > (F-12+ only). I'm getting closer, but I'm having a problem with a > missing jdepend-maven-plugin. This plugin is referred to in at least > two F-12 poms, namely: > > /usr/share/maven2/default_poms/JPP-commons-parent.pom > /usr/share/maven2/default_poms/JPP.codehaus-mojo.pom > > Both of those poms are supplied by the maven2-common-poms package. > The problem is that I can't find a package that supplies > jdepend-maven-plugin. Does it even exist in Fedora? The plugin doesn't exist in Fedora. The error was not encountered before because none of the jakarta* packages use maven to build (at least afaik). The issue is that commons-parent serves as a common parent for all new jakarta* packages using maven to build. The jdepend plugin is used when the maven reporting target is called. There are 2 ways to fix the problem 1. The right way - Add jdepend plugin to Fedora 2. The "This needed to be done yesterday" way - supply your own parent pom (with no jdepend) in a custom repo Cheers, Deepak > -- > Jerry James > http://www.jamezone.org/ > > -- > fedora-devel-java-list mailing list > fedora-devel-java-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-devel-java-list From adam at spicenitz.org Fri Nov 13 16:11:07 2009 From: adam at spicenitz.org (Adam Goode) Date: Fri, 13 Nov 2009 11:11:07 -0500 Subject: [fedora-java] review request for jai-imageio-core Message-ID: <4AFD851B.5010906@spicenitz.org> Hi, I've packaged jai-imageio-core for Fedora, minus the forbidden parts. With this package, ImageIO.read() and ImageIO.write() will now work with BMP, GIF, PCX, PNM, raw (not RAW), TIFF, PCX, and WBMP. Does someone want to review this package? It's at https://bugzilla.redhat.com/show_bug.cgi?id=536944 Thanks, Adam -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 260 bytes Desc: OpenPGP digital signature URL: From M.E.Foster at hw.ac.uk Mon Nov 16 21:33:04 2009 From: M.E.Foster at hw.ac.uk (Mary Ellen Foster) Date: Mon, 16 Nov 2009 21:33:04 +0000 Subject: [fedora-java] Is GCJ still really necessary? Message-ID: What's the benefit of doing the GCJ AOT-compilation steps as defined in https://fedoraproject.org/wiki/Packaging/GCJGuidelines? Doesn't everyone just use OpenJDK these days? It adds a bunch of extra stuff to every Java spec file and makes all java packages arch-specific instead of noarch, which always feels a bit weird ... MEF -- Mary Ellen Foster -- http://www.macs.hw.ac.uk/~mef3/ Interaction Lab -- http://www.macs.hw.ac.uk/InteractionLab School of Mathematical and Computer Sciences, Heriot-Watt University Heriot-Watt University is a Scottish charity registered under charity number SC000278 From oget.fedora at gmail.com Mon Nov 16 21:41:29 2009 From: oget.fedora at gmail.com (Orcan Ogetbil) Date: Mon, 16 Nov 2009 16:41:29 -0500 Subject: [fedora-java] Is GCJ still really necessary? In-Reply-To: References: Message-ID: On Mon, Nov 16, 2009 at 4:33 PM, Mary Ellen Foster wrote: > What's the benefit of doing the GCJ AOT-compilation steps as defined > in https://fedoraproject.org/wiki/Packaging/GCJGuidelines? Doesn't > everyone just use OpenJDK these days? It adds a bunch of extra stuff > to every Java spec file and makes all java packages arch-specific > instead of noarch, which always feels a bit weird ... > > MEF > Ah the famous topic :) I think the latest explanation for the AOT bits were that they are still needed in ppc* architectures because openjdk is still slow on those machines. I don't know if this has changed since. But from F-13 on, I expect that we will drop the AOT bit requirement since ppc* won't be primary architectures anymore. Orcan From ahughes at redhat.com Tue Nov 17 00:53:36 2009 From: ahughes at redhat.com (Andrew John Hughes) Date: Tue, 17 Nov 2009 00:53:36 +0000 Subject: [fedora-java] Is GCJ still really necessary? In-Reply-To: References: Message-ID: <20091117005336.GE20005@rivendell.middle-earth.co.uk> On 16:41 Mon 16 Nov , Orcan Ogetbil wrote: > On Mon, Nov 16, 2009 at 4:33 PM, Mary Ellen Foster wrote: > > What's the benefit of doing the GCJ AOT-compilation steps as defined > > in https://fedoraproject.org/wiki/Packaging/GCJGuidelines? Doesn't > > everyone just use OpenJDK these days? It adds a bunch of extra stuff > > to every Java spec file and makes all java packages arch-specific > > instead of noarch, which always feels a bit weird ... > > > > MEF > > > > Ah the famous topic :) > > I think the latest explanation for the AOT bits were that they are > still needed in ppc* architectures because openjdk is still slow on > those machines. > > I don't know if this has changed since. But from F-13 on, I expect > that we will drop the AOT bit requirement since ppc* won't be primary > architectures anymore. > > Orcan > > -- > fedora-devel-java-list mailing list > fedora-devel-java-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-devel-java-list AOT is still beneficial with some applications, even on non-ppc architectures -- ecj being the prime example. -- Andrew :) Free Java Software Engineer Red Hat, Inc. (http://www.redhat.com) Support Free Java! Contribute to GNU Classpath and the OpenJDK http://www.gnu.org/software/classpath http://openjdk.java.net PGP Key: 94EFD9D8 (http://subkeys.pgp.net) Fingerprint = F8EF F1EA 401E 2E60 15FA 7927 142C 2591 94EF D9D8 From lkundrak at v3.sk Tue Nov 17 11:15:48 2009 From: lkundrak at v3.sk (Lubomir Rintel) Date: Tue, 17 Nov 2009 12:15:48 +0100 Subject: [fedora-java] IntelliJ IDEA for Fedora 13 Message-ID: <1258456548.6820.124.camel@localhost.localdomain> Hi Everyone, as you may or may not know, we started and effort to get IntelliJ IDEA Community Edition packaged for Fedora 13 [1]. I'm wondering if you find it useful? If you do, you could help us and your help would really be appreciated. This Friday, FESCo [2] will decide whether it's noteworthy enough to be accepted as Fedora 13 feature. If you think so it might be a good idea to have a short look at brainstorming page [3] and add your ideas there. Also you're welcome to join the feature team, hopefully you'll find everything you need on the feature page [1]. [1] https://fedoraproject.org/wiki/Features/IntelliJ_IDEA [2] https://fedoraproject.org/wiki/Development/SteeringCommittee [3] https://fedoraproject.org/wiki/Talk:Features/IntelliJ_IDEA Regards, Lubo -- Flash is the Web2.0 version of blink and animated gifs. -- Stephen Smoogen From aph at redhat.com Tue Nov 17 11:36:45 2009 From: aph at redhat.com (Andrew Haley) Date: Tue, 17 Nov 2009 11:36:45 +0000 Subject: [fedora-java] Is GCJ still really necessary? In-Reply-To: References: Message-ID: <4B028ACD.8020908@redhat.com> Orcan Ogetbil wrote: > On Mon, Nov 16, 2009 at 4:33 PM, Mary Ellen Foster wrote: >> What's the benefit of doing the GCJ AOT-compilation steps as defined >> in https://fedoraproject.org/wiki/Packaging/GCJGuidelines? Doesn't >> everyone just use OpenJDK these days? It adds a bunch of extra stuff >> to every Java spec file and makes all java packages arch-specific >> instead of noarch, which always feels a bit weird ... > > Ah the famous topic :) > > I think the latest explanation for the AOT bits were that they are > still needed in ppc* architectures because openjdk is still slow on > those machines. > > I don't know if this has changed since. But from F-13 on, I expect > that we will drop the AOT bit requirement since ppc* won't be primary > architectures anymore. And Shark, the LLVM-based JIT for OpenJDK, is getting close to prime time. See http://icedtea.classpath.org/wiki/ZeroSharkFaq Andrew. From mlists at juma.me.uk Tue Nov 17 11:53:33 2009 From: mlists at juma.me.uk (Ismael Juma) Date: Tue, 17 Nov 2009 11:53:33 +0000 Subject: [fedora-java] IntelliJ IDEA for Fedora 13 In-Reply-To: <1258456548.6820.124.camel@localhost.localdomain> References: <1258456548.6820.124.camel@localhost.localdomain> Message-ID: <1258458813.8216.108.camel@localhost.localdomain> Hi Lubo, On Tue, 2009-11-17 at 12:15 +0100, Lubomir Rintel wrote: > as you may or may not know, we started and effort to get IntelliJ IDEA > Community Edition packaged for Fedora 13 [1]. Very cool. > I'm wondering if you find it useful? Even though I am an Eclipse user, I would still say definitely. > This Friday, FESCo [2] will decide whether it's noteworthy enough to be > accepted as Fedora 13 feature. If you think so it might be a good idea > to have a short look at brainstorming page [3] and add your ideas there. I think so. This may not be apparent to people outside of the Java community, bit IntelliJ IDEA has an excellent reputation in those circles. It's considered by many to be the best IDE available (although this refers to the proprietary version). This is obviously subjective and I can't comment from personal experience as I haven't used it enough. Also, I've heard from many users that it has the best Scala support. Best, Ismael From mlists at juma.me.uk Tue Nov 17 11:56:19 2009 From: mlists at juma.me.uk (Ismael Juma) Date: Tue, 17 Nov 2009 11:56:19 +0000 Subject: [fedora-java] Is GCJ still really necessary? In-Reply-To: <4B028ACD.8020908@redhat.com> References: <4B028ACD.8020908@redhat.com> Message-ID: <1258458979.8216.110.camel@localhost.localdomain> On Tue, 2009-11-17 at 11:36 +0000, Andrew Haley wrote: > And Shark, the LLVM-based JIT for OpenJDK, is getting close to > prime time. See http://icedtea.classpath.org/wiki/ZeroSharkFaq Very nice. Out of curiosity, are there plans to try to get Shark to pass the Java SE 6 TCK? Best, Ismael From aph at redhat.com Tue Nov 17 13:26:24 2009 From: aph at redhat.com (Andrew Haley) Date: Tue, 17 Nov 2009 13:26:24 +0000 Subject: [fedora-java] Is GCJ still really necessary? In-Reply-To: <1258458979.8216.110.camel@localhost.localdomain> References: <4B028ACD.8020908@redhat.com> <1258458979.8216.110.camel@localhost.localdomain> Message-ID: <4B02A480.6010107@redhat.com> Ismael Juma wrote: > On Tue, 2009-11-17 at 11:36 +0000, Andrew Haley wrote: >> And Shark, the LLVM-based JIT for OpenJDK, is getting close to >> prime time. See http://icedtea.classpath.org/wiki/ZeroSharkFaq > > Very nice. Out of curiosity, are there plans to try to get Shark to pass > the Java SE 6 TCK? Yes, as soon as it's done. Andrew. From overholt at redhat.com Tue Nov 17 13:43:31 2009 From: overholt at redhat.com (Andrew Overholt) Date: Tue, 17 Nov 2009 08:43:31 -0500 Subject: [fedora-java] IntelliJ IDEA for Fedora 13 In-Reply-To: <1258456548.6820.124.camel@localhost.localdomain> References: <1258456548.6820.124.camel@localhost.localdomain> Message-ID: <20091117134331.GB2185@redhat.com> Hi, * Lubomir Rintel [2009-11-17 06:16]: > as you may or may not know, we started and effort to get IntelliJ IDEA > Community Edition packaged for Fedora 13 [1]. I'm wondering if you find > it useful? I can't say I'll have time to help but more packages depending on the things Eclipse does will surely be better for us. Andrew From dbhole at redhat.com Tue Nov 17 20:52:43 2009 From: dbhole at redhat.com (Deepak Bhole) Date: Tue, 17 Nov 2009 15:52:43 -0500 Subject: [fedora-java] Status of maven 2.2.1 update in rawhide Message-ID: <20091117205242.GC13169@redhat.com> Hi Everyone, Sorry for the cross-list posting, but the matter is of interest to both lists afaict, as I have seen messages related to maven on both. As some of you might know, we intend to put maven 2.2.1 in rawhide. The new maven will be a completely re-written rpm, one that should be a lot easier to maintain, and much more stable. All progress related to this upgrade is now on the wiki: https://fedoraproject.org/wiki/MavenUpdate Updates/new packages for dependencies will be a significant effort. Once we (Andrew Overholt, Alexander Kurtakov and myself) start work on that, we will need all the help we can get :) So if you are interested in helping, or just tracking progress -- that is the page to subscribe to/check out! I'll send one more mail to this list when work on dependencies starts. Cheers, Deepak From mefoster at gmail.com Tue Nov 24 11:40:15 2009 From: mefoster at gmail.com (Mary Ellen Foster) Date: Tue, 24 Nov 2009 11:40:15 +0000 Subject: [fedora-java] Update on the build-Sesame-from-source progress Message-ID: Hello! I've continued working on the process of getting Sesame to build from source (http://www.openrdf.org/). After a bit of a false step, it turns out that the one monster horrible package that pulled in most of the dependencies is only used in one subpackage, which -- I hope! -- isn't needed for the Sesame backend of Soprano that was the motivation for this whole undertaking. I *WILL* follow through on the review requests I put up as part of that initial effort, though -- don't worry, Java people! :) So anyway, I now have a SRPM of Sesame that builds locally on my computer after building and installing all of the dependencies. There are still a fair number of dependencies to get in, but the individual packages are mostly pretty straightforward. There are also a few packages already in Fedora which need a minor update so that Sesame can build against them. I've summarised my progress here: https://fedoraproject.org/wiki/MaryEllenFoster/SopranoSesame#The_new_stuff At this point, I really need to give the review requests that I filed earlier a bit of love before spamming the review queue again (there are 16 packages that need to be reviewed before Sesame can be built). I'd like to review any Java-based packages that are out there in return -- is there any way to find such packages short of searching for "java" in the review requests? MEF -- Mary Ellen Foster -- http://www.macs.hw.ac.uk/~mef3/ Interaction Lab -- http://www.macs.hw.ac.uk/InteractionLab School of Mathematical and Computer Sciences, Heriot-Watt University Heriot-Watt University is a Scottish charity registered under charity number SC000278 From overholt at redhat.com Tue Nov 24 14:21:46 2009 From: overholt at redhat.com (Andrew Overholt) Date: Tue, 24 Nov 2009 09:21:46 -0500 Subject: [fedora-java] Update on the build-Sesame-from-source progress In-Reply-To: References: Message-ID: <20091124142146.GB2127@redhat.com> > I'd like to review any Java-based packages that are out there in > return -- is there any way to find such packages short of searching > for "java" in the review requests? Not that I know of but we're going to have a bunch of new packages for the new version of maven so perhaps we could swap? Andrew From otto_rey at yahoo.com.ar Thu Nov 26 01:37:11 2009 From: otto_rey at yahoo.com.ar (Otto Rey) Date: Wed, 25 Nov 2009 17:37:11 -0800 (PST) Subject: [fedora-java] Proposed: Java-Gnome 4 In-Reply-To: References: Message-ID: <401265.60879.qm@web52407.mail.re2.yahoo.com> FYI: https://fedoraproject.org/wiki/Features/Java-Gnome4 Saludos Yahoo! Cocina Encontra las mejores recetas con Yahoo! Cocina. http://ar.mujer.yahoo.com/cocina/