From timothy.selivanow at virtualxistenz.com Tue Dec 4 20:48:52 2007 From: timothy.selivanow at virtualxistenz.com (Timothy Selivanow) Date: Tue, 04 Dec 2007 12:48:52 -0800 Subject: [fedora-java] Eclipse error when doing a "Run As" in a java project Message-ID: <1196801332.3187.34.camel@denkiteki-penpen.easystreet.com> I'm seeing issues when trying to do a "Run" or "Run As". I went through the HelloWorld tutorial to make sure I'm not missing anything, and at the end of the tutorial when it says: To run your application, right-click on your class in the Package Explorer and select Run As > Java Application. The Console view should appear at the bottom and display the "Hello, world!" output. There is only "Open Run Dialog..." when I right click on the class and hover on "Run As". If I go through and add a configuration under "Java Application" (and add HelloWorld as the class) or just click the run button on the toolbar and choose "Java Application", I get the following error: Exception in thread "main" java.lang.NoSuchMethodError: main Error: A JNI error has occurred, please check your installation and try again What am I missing? --Tim _________________________________________________________________________________ / NEW YORK-- Kraft Foods, Inc. announced today that its board of \ | directors unanimously rejected the $11 billion takeover bid by Philip | | Morris and Co. A Kraft spokesman stated in a press conference that the | | offer was rejected because the $90-per-share bid did not reflect the | | true value of the company. | | Wall Street insiders, however, tell quite a different story. | | Apparently, the Kraft board of directors had all but signed the takeover | | agreement when they learned of Philip Morris' marketing plans for one of | | their major Middle East subsidiaries. To a person, the board voted to | | reject the bid when they discovered that the tobacco giant intended to | \ reorganize Israeli Cheddar, Ltd., and name the new company Cheeses of Nazareth. / --------------------------------------------------------------------------------- \ \ \ \ /\ ( ) .( o ). From jjohnstn at redhat.com Tue Dec 4 21:51:44 2007 From: jjohnstn at redhat.com (Jeff Johnston) Date: Tue, 04 Dec 2007 16:51:44 -0500 Subject: [fedora-java] Eclipse error when doing a "Run As" in a java project In-Reply-To: <1196801332.3187.34.camel@denkiteki-penpen.easystreet.com> References: <1196801332.3187.34.camel@denkiteki-penpen.easystreet.com> Message-ID: <4755CBF0.3000007@redhat.com> Timothy Selivanow wrote: > I'm seeing issues when trying to do a "Run" or "Run As". I went > through the HelloWorld tutorial to make sure I'm not missing anything, > and at the end of the tutorial when it says: > > To run your application, right-click on your class in the Package > Explorer and select Run As > Java Application. The Console view should > appear at the bottom and display the "Hello, world!" output. > > > There is only "Open Run Dialog..." when I right click on the class and > hover on "Run As". If I go through and add a configuration under "Java > Application" (and add HelloWorld as the class) or just click the run > button on the toolbar and choose "Java Application", I get the following > error: > > Exception in thread "main" java.lang.NoSuchMethodError: main > Error: A JNI error has occurred, please check your installation and try > again > > > What am I missing? > > Timothy, It appears you do not have a proper main method. You should have the following method in your HelloWorld.java file: public static void main(String[] args) { System.out.println("Hello World!"); } You would have gotten this when you created your New Class if you asked it to create your main method (there is a click box). If you right-click on the java file, you will be offered the option to run it as a Java Application. If you rename it to main2, for example, you will instead see "Open Run Dialog" offered. If you try and force this to be run via the dialog, you will get the error message you are seeing which is entirely expected. -- Jeff J. > > --Tim > _________________________________________________________________________________ > / NEW YORK-- Kraft Foods, Inc. announced today that its board of \ > | directors unanimously rejected the $11 billion takeover bid by Philip | > | Morris and Co. A Kraft spokesman stated in a press conference that the | > | offer was rejected because the $90-per-share bid did not reflect the | > | true value of the company. | > | Wall Street insiders, however, tell quite a different story. | > | Apparently, the Kraft board of directors had all but signed the takeover | > | agreement when they learned of Philip Morris' marketing plans for one of | > | their major Middle East subsidiaries. To a person, the board voted to | > | reject the bid when they discovered that the tobacco giant intended to | > \ reorganize Israeli Cheddar, Ltd., and name the new company Cheeses of Nazareth. / > --------------------------------------------------------------------------------- > \ > \ \ > \ /\ > ( ) > .( o ). > > -- > fedora-devel-java-list mailing list > fedora-devel-java-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-devel-java-list From timothy.selivanow at virtualxistenz.com Tue Dec 4 22:00:49 2007 From: timothy.selivanow at virtualxistenz.com (Timothy Selivanow) Date: Tue, 04 Dec 2007 14:00:49 -0800 Subject: [fedora-java] Eclipse error when doing a "Run As" in a java project In-Reply-To: <4755CBF0.3000007@redhat.com> References: <1196801332.3187.34.camel@denkiteki-penpen.easystreet.com> <4755CBF0.3000007@redhat.com> Message-ID: <1196805649.3187.38.camel@denkiteki-penpen.easystreet.com> On Tue, 2007-12-04 at 16:51 -0500, Jeff Johnston wrote: > Timothy, > > It appears you do not have a proper main method. You should have the > following method in your HelloWorld.java file: > > public static void main(String[] args) { > System.out.println("Hello World!"); > } > > You would have gotten this when you created your New Class if you asked > it to create your main method (there is a click box). > > If you right-click on the java file, you will be offered the option to > run it as a Java Application. If you rename it to main2, for example, > you will instead see "Open Run Dialog" offered. If you try and force > this to be run via the dialog, you will get the error message you are > seeing which is entirely expected. > > -- Jeff J. I had the method defined, but I had removed "String[] args" thinking that I didn't need to pass anything to it so I should take it out. Does this mean that main() needs at least that argument declaration to work properly? --Tim ________________________________________________________________________ / If you float on instinct alone, how can you calculate the buoyancy for \ | the computed load? | \ -- Christopher Hodder-Williams / ------------------------------------------------------------------------ \ \ \ \ /\ ( ) .( o ). From jjohnstn at redhat.com Tue Dec 4 22:07:54 2007 From: jjohnstn at redhat.com (Jeff Johnston) Date: Tue, 04 Dec 2007 17:07:54 -0500 Subject: [fedora-java] Eclipse error when doing a "Run As" in a java project In-Reply-To: <1196805649.3187.38.camel@denkiteki-penpen.easystreet.com> References: <1196801332.3187.34.camel@denkiteki-penpen.easystreet.com> <4755CBF0.3000007@redhat.com> <1196805649.3187.38.camel@denkiteki-penpen.easystreet.com> Message-ID: <4755CFBA.70509@redhat.com> Timothy Selivanow wrote: > On Tue, 2007-12-04 at 16:51 -0500, Jeff Johnston wrote: >> Timothy, >> >> It appears you do not have a proper main method. You should have the >> following method in your HelloWorld.java file: >> >> public static void main(String[] args) { >> System.out.println("Hello World!"); >> } >> >> You would have gotten this when you created your New Class if you asked >> it to create your main method (there is a click box). >> >> If you right-click on the java file, you will be offered the option to >> run it as a Java Application. If you rename it to main2, for example, >> you will instead see "Open Run Dialog" offered. If you try and force >> this to be run via the dialog, you will get the error message you are >> seeing which is entirely expected. >> >> -- Jeff J. > > > I had the method defined, but I had removed "String[] args" thinking > that I didn't need to pass anything to it so I should take it out. Does > this mean that main() needs at least that argument declaration to work > properly? > Yes. It is looking for that particular main signature. If you rename it don't make it public or static, all of these will cause the same problem. -- Jeff J. > > --Tim > ________________________________________________________________________ > / If you float on instinct alone, how can you calculate the buoyancy for \ > | the computed load? | > \ -- Christopher Hodder-Williams / > ------------------------------------------------------------------------ > \ > \ \ > \ /\ > ( ) > .( o ). > > -- > fedora-devel-java-list mailing list > fedora-devel-java-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-devel-java-list From francois-xavier.kowalski at hp.com Wed Dec 5 08:17:57 2007 From: francois-xavier.kowalski at hp.com (Francois-Xavier KOWALSKI) Date: Wed, 05 Dec 2007 09:17:57 +0100 Subject: [fedora-java] [Q] Autotools Eclipse plugin & build directory Message-ID: <47565EB5.4000800@hp.com> Hello fedora-devel-java, I am using the Autotools Plug-in version 0.9.5.2 from your Eclipse update site, from Eclipse 3.3.1.1 + CDT 4.0.1. When creating a new autotools project[1], the CDT build directory is hard-wired to ${project_loc}/build. Changing this value to some other (eg. in my case ${worksspace_loc}/_build) is ignored. As a result: 1. In case a project already has a "build" sub-directory, the autotools plugin enthusiastically damage the content of this sub-directory 2. It is not possible to use a single source tree ${project_loc} for several build-trees (for example to use several combinations of ./configure options) From my understanding, the plugin should use both ${project_loc} to run the autogen.sh tool, _and_ the GUI-set ${build_dir}to run the configure & make tools. Is this a missing feature or do I mis-understand something? Thanks --FiX [1] Or when migrating an existing CDT project, this is the same result. -- Francois-Xavier "FiX" KOWALSKI /_ __ Tel:+33 (0)4 76 14 63 27 HP OpenCall Software - EMTS / //_/ Fax:+33 (0)4 76 14 51 62 Media-Processing Engineering / http://www.hp.com/go/opencall i n v e n t From overholt at redhat.com Wed Dec 5 14:35:58 2007 From: overholt at redhat.com (Andrew Overholt) Date: Wed, 05 Dec 2007 09:35:58 -0500 Subject: [fedora-java] [Q] Autotools Eclipse plugin & build directory In-Reply-To: <47565EB5.4000800@hp.com> References: <47565EB5.4000800@hp.com> Message-ID: <4756B74E.2010106@redhat.com> Hi, Francois-Xavier KOWALSKI wrote: > When creating a new autotools project[1], the CDT build directory is > hard-wired to ${project_loc}/build. Changing this value to some other > (eg. in my case ${worksspace_loc}/_build) is ignored. As a result: Please file a bug at Red Hat bugzilla against eclipse-cdt (yes, it should probably have its own component). Thanks, Andrew From jjohnstn at redhat.com Wed Dec 5 19:06:54 2007 From: jjohnstn at redhat.com (Jeff Johnston) Date: Wed, 05 Dec 2007 14:06:54 -0500 Subject: [fedora-java] [Q] Autotools Eclipse plugin & build directory In-Reply-To: <47565EB5.4000800@hp.com> References: <47565EB5.4000800@hp.com> Message-ID: <4756F6CE.8010506@redhat.com> Francois-Xavier KOWALSKI wrote: > Hello fedora-devel-java, > > I am using the Autotools Plug-in version 0.9.5.2 from your Eclipse > update site, from Eclipse 3.3.1.1 + CDT 4.0.1. > > When creating a new autotools project[1], the CDT build directory is > hard-wired to ${project_loc}/build. Changing this value to some other > (eg. in my case ${worksspace_loc}/_build) is ignored. As a result: > > 1. In case a project already has a "build" sub-directory, the > autotools plugin enthusiastically damage the content of this > sub-directory > 2. It is not possible to use a single source tree ${project_loc} for > several build-trees (for example to use several combinations of > ./configure options) > Francois, changing the build directory is supported, but not via the ManagedMake settings. The configure tool has the build directory specified under Project->Properties->C/C++ Build->Settings->Tool Settings->Configure ->General->Build Directory The first configuration defaults to "build", but you can change it. You also get a different default per new configuration (buildx where x is a number). You may change each configuration manually to whatever local directory you want in the Tool Settings dialog. You can also create multiple configurations there and specify different Autotools configuration parameters to each CDT configuration. So, you can have one tree that builds arm-elf, mn10300-elf, etc.. You can name the CDT configurations and manage them in the Properties->C/C++ Build dialog (see top right button: Manage Configurations). > From my understanding, the plugin should use both ${project_loc} to run > the autogen.sh tool, _and_ the GUI-set ${build_dir}to run the configure > & make tools. > > Is this a missing feature or do I mis-understand something? > The plugin looks for configure and autogen.sh in the main project directory by default. autogen.sh is only used if there is no configure script to run. If autogen.sh runs configure and creates a new config.status, configure is not run again, otherwise, configure is automatically run after autogen.sh. The configure tool has a "Configure Tool Directory" option under General which allows you to specify a subdirectory (e.g. src) where configure is found. Autogen.sh tool options were added long after configure and ideally this option plus the build directory should be split out. For now, you can change the autogen.sh command to include a subdirectory (e.g. src/autogen.sh). This last feature won't work until 0.9.5.3 which is due out on the update site later today. The top-level Makefile is created in the build directory specified by the configure tool. -- Jeff J. From kwade at redhat.com Thu Dec 6 01:29:42 2007 From: kwade at redhat.com (Karsten Wade) Date: Wed, 05 Dec 2007 17:29:42 -0800 Subject: [fedora-java] FOP success Message-ID: <1196904582.25124.52.camel@erato.phig.org> Passing along one success report, from someone who knows what he's doing. Also, it sounds as if 'xmlto' is going to have FOP as an optional target, so we can test our full toolchain: https://bugzilla.redhat.com/show_bug.cgi?id=147472 -------- Forwarded Message -------- From: Jared Smith Reply-To: For participants of the Documentation Project To: For participants of the Documentation Project Subject: Re: [Fwd: fop built] Date: Wed, 05 Dec 2007 14:20:31 -0500 On Wed, 2007-11-28 at 17:46 -0800, Karsten Wade wrote: > Unleash the flying monkeys! > > I'll see about getting a Rawhide instance going in the next few weeks > for testing. Hereby letting all others interested in quality PDF > production from DocBook, here's a way to lend a hand - test the new FOP > build. Hot diggity dog! I finally got around to trying this out today, and I have to say this is a beautiful thing! Everything just worked! Wonderful! To give you some background, I've spent the past several weeks working on Docbook/FOP stuff for another project, and been fighting the whole Java stack the entire time. Karsten and Thomas (and anyone else who worked on this), please contact me offline and I'll find a way to buy you a pizza. (Now if I could just get this other project finished, so that I can work on Fedora docs...) -Jared Smith -- Karsten Wade, Developer Community Mgr. Dev Fu : http://developer.redhatmagazine.com Fedora : http://quaid.fedorapeople.org gpg key : AD0E0C41 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From francois-xavier.kowalski at hp.com Wed Dec 12 22:52:45 2007 From: francois-xavier.kowalski at hp.com (Francois-Xavier KOWALSKI) Date: Wed, 12 Dec 2007 23:52:45 +0100 Subject: [fedora-java] [Q] Autotools Eclipse plugin & build directory In-Reply-To: <4756F6CE.8010506@redhat.com> References: <47565EB5.4000800@hp.com> <4756F6CE.8010506@redhat.com> Message-ID: <4760663D.7010109@hp.com> Jeff Johnston wrote: > Francois-Xavier KOWALSKI wrote: > >> Hello fedora-devel-java, >> >> I am using the Autotools Plug-in version 0.9.5.2 from your Eclipse >> update site, from Eclipse 3.3.1.1 + CDT 4.0.1. >> >> When creating a new autotools project[1], the CDT build directory is >> hard-wired to ${project_loc}/build. Changing this value to some other >> (eg. in my case ${worksspace_loc}/_build) is ignored. As a result: >> >> 1. In case a project already has a "build" sub-directory, the >> autotools plugin enthusiastically damage the content of this >> sub-directory >> 2. It is not possible to use a single source tree ${project_loc} for >> several build-trees (for example to use several combinations of >> ./configure options) >> Hello Jeff, Sorry for coming back to you so late: your answer was automatically sorted to some mail folder... I just rediscovered it :-[ thanks for answering & providing me solutions for both aspects of my problem. I will take a look at this 0.9.5.3 update as soon as I will have fixed this !@#$%^ of Eclipse update that keeps trying to locate a non-existent Europa Update Site. br. --FiX > > Francois, changing the build directory is supported, but not via the > ManagedMake settings. > > The configure tool has the build directory specified under > > Project->Properties->C/C++ Build->Settings->Tool Settings->Configure > ->General->Build Directory > > The first configuration defaults to "build", but you can change it. You > also get a different default per new configuration (buildx where x is a > number). You may change each configuration manually to whatever local > directory you want in the Tool Settings dialog. You can also create > multiple configurations there and specify different Autotools > configuration parameters to each CDT configuration. So, you can have > one tree that builds arm-elf, mn10300-elf, etc.. You can name the CDT > configurations and manage them in the Properties->C/C++ Build dialog > (see top right button: Manage Configurations). > > >> From my understanding, the plugin should use both ${project_loc} to run >> the autogen.sh tool, _and_ the GUI-set ${build_dir}to run the configure >> & make tools. >> >> Is this a missing feature or do I mis-understand something? >> >> > > The plugin looks for configure and autogen.sh in the main project > directory by default. autogen.sh is only used if there is no configure > script to run. If autogen.sh runs configure and creates a new > config.status, configure is not run again, otherwise, configure is > automatically run after autogen.sh. The configure tool has a "Configure > Tool Directory" option under General which allows you to specify a > subdirectory (e.g. src) where configure is found. Autogen.sh tool > options were added long after configure and ideally this option plus the > build directory should be split out. For now, you can change the > autogen.sh command to include a subdirectory (e.g. src/autogen.sh). > This last feature won't work until 0.9.5.3 which is due out on the > update site later today. > > The top-level Makefile is created in the build directory specified by > the configure tool. > > -- Jeff J. > > -- Francois-Xavier "FiX" KOWALSKI /_ __ Tel:+33 (0)4 76 14 63 27 HP OpenCall Software - EMTS / //_/ Fax:+33 (0)4 76 14 51 62 Media-Processing Engineering / http://www.hp.com/go/opencall i n v e n t From mcepl at redhat.com Sat Dec 15 09:37:05 2007 From: mcepl at redhat.com (Matej Cepl) Date: Sat, 15 Dec 2007 10:37:05 +0100 Subject: [fedora-java] openfire packaging Message-ID: <1rjc35x3n5.ln2@ppp1053.in.ipex.cz> Hi, did anybody try packaging of OpenFire (XMPP Java server; http://www.igniterealtime.org/downloads/index.jsp)? I tried their tarball http://www.igniterealtime.org/downloads/download-landing.jsp?file=openfire/openfire_3_4_2.tar.gz and it works pretty well with IcedTea from Rawhide (the RPM includes Sun JRE). Source code is http://www.igniterealtime.org/downloads/download-landing.jsp?file=openfire/openfire_src_3_4_2.tar.gz I would try it, but it seems a little overwhelming task for me (who knows almost nothing about Java) to package such huge daemon. Best, Mat?j Cepl From bruno at wolff.to Tue Dec 18 22:53:03 2007 From: bruno at wolff.to (Bruno Wolff III) Date: Tue, 18 Dec 2007 16:53:03 -0600 Subject: [fedora-java] Packaging standards for java programs? Message-ID: <20071218225303.GA11365@wolff.to> I want to try my hand at packing a java game (Colossus) for Fedora. I am not a java programmer, but the game is pretty simple to build use ant. However, I am not sure where things should get installed or if there is anything special I should do to make an executable (instead of having people running java -jar). Is there some documentation on suggestions or standards for packing java applications that I can read to get more information on how to do this? From ihok at hotmail.com Thu Dec 20 21:51:20 2007 From: ihok at hotmail.com (Jack Tanner) Date: Thu, 20 Dec 2007 21:51:20 +0000 (UTC) Subject: [fedora-java] eclipse on f8 Message-ID: It seems like f8 eclipse is heading for an update, but staying at 3.3.0. http://koji.fedoraproject.org/koji/buildinfo?buildID=28594 Any chance we could have 3.3.1 instead? I'd be happy to test this if that made a difference: http://koji.fedoraproject.org/koji/buildinfo?buildID=26944 From overholt at redhat.com Thu Dec 20 22:29:12 2007 From: overholt at redhat.com (Andrew Overholt) Date: Thu, 20 Dec 2007 17:29:12 -0500 Subject: [fedora-java] eclipse on f8 In-Reply-To: References: Message-ID: <20071220222912.GA23851@redhat.com> * Jack Tanner [2007-12-20 17:15]: > It seems like f8 eclipse is heading for an update, but staying at 3.3.0. > > http://koji.fedoraproject.org/koji/buildinfo?buildID=28594 Yup. > Any chance we could have 3.3.1 instead? Not at this time. I recently tried to do a 3.3.1.1 update but it caused more problems than it was worth. If you have time to look into why upgrading from 3.3.0 to 3.3.1.1 requires the use of -clean, I'd greatly appreciate it :) Andrew -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: