Rebuild-jar-repository Error Failed To Set Javacmd

on RHEL v3.0 Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] Hi, There is a problem with the tomcat5 RPM, when you try and install it on RHEL v3.0, using the IBM v1.4.1 SDK as supplied by Redhat. An attempt to install, and an attempt to run, bombs out like so: [root at dungeon root]# service tomcat5 start Starting tomcat5: /usr/bin/rebuild-jar-repository: error: failed to set JAVACMD /usr/bin/rebuild-jar-repository: error: failed to set JAVACMD /usr/bin/rebuild-jar-repository: error: failed to set JAVACMD /usr/bin/rebuild-jar-repository: error: failed to set JAVACMD /usr/bin/rebuild-jar-repository: error: failed to set JAVACMD The $JAVA_HOME is set, but $JAVA_HOME/bin/java is a symbolic link, not an executable file, which is probably why it is failing. The rebuild-jar-repository script needs to be updated to detect symbolic links. It should not be necessary to be forced to use any jpackage provided SDK packages instead of vendor supplied packages, as vendor supplied packages are normally provided under a service level agreement. Regards, Graham -- Previous message: [JPackage-discuss] broken link on jpackage site Next message: [JPackage-discuss] tomcat5 won't install on RHEL v3.0 Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] More information about the JPackage-discuss mailing list

5 and RHEL v3.0 Date: Fri, 19 Mar 2004 00:23:41 +0200 Hi all, https://www.zarb.org/pipermail/jpackage-discuss/2004-March/004576.html I have been trying to get tomcat5 to work as shipped by jpackage.org under RHEL v3.0. Seems the script that is supposed to detect https://www.redhat.com/archives/redhat-list/2004-March/msg00774.html java doesn't work properly, saying the following: /usr/bin/rebuild-jar-repository: error: failed to set JAVACMD The JDK is the IBM v1.4.1 as shipped with RHEL v3.0. JAVA_HOME is set, and java is in the PATH, but the java detection still fails. Anyone had any joy with this? Regards, Graham -- Follow-Ups: Re: Tomcat 5 and RHEL v3.0 From: Daniel Carrillo [Date Prev][Date Next] [Thread Prev][Thread Next] [Thread Index] [Date Index] [Author Index]

here for a quick overview of the site http://stackoverflow.com/questions/7600028/maven-error-in-opening-zip-file-when-running-maven Help Center Detailed answers to any questions you might http://stackoverflow.com/questions/9689793/cant-execute-jar-file-no-main-manifest-attribute have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users rebuild-jar-repository error Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Maven : error in opening zip file when running maven up vote rebuild-jar-repository error failed 33 down vote favorite 7 [ERROR] error: error reading C:\Users\suresh\.m2\repository\org\jdom\jdom\1.1\jdom-1.1.jar; error in opening zip file [ERROR] error: error reading C:\Users\suresh\.m2\repository\javax\servlet\servlet-api\2.5\servlet-api-2.5.jar; error in opening zip file [ERROR] error: error reading C:\Users\suresh\.m2\repository\org\apache\cxf\cxf-rt-bindings-http\2.2.1\cxf-rt-bindings-http-2.2.1.jar; error in opening zip file [ERROR] error: error reading C:\Users\suresh\.m2\repository\org\codehaus\jra\jra\1.0-alpha-4\jra-1.0-alpha-4.jar; error in opening zip file [ERROR] error: error reading C:\Users\suresh\.m2\repository\org\apache\cxf\cxf-api\2.2.1\cxf-api-2.2.1.jar; error in opening zip file [ERROR] error: error reading C:\Users\suresh\.m2\repository\org\apache\cxf\cxf-common-utilities\2.2.1\cxf-common-utilities-2.2.1.jar; error in opening zip file [INFO] 44 errors How to resolve this error while running mvn clean install? And I see that, on to the repository path in my disk, starting from servlet, no packages are being created inside repository. maven share|improve this question edited May 3 at 11:30 R O M A N I A 12.8k116780 asked Sep 29 '11 at 15:53 UnKnown 5,67443147245 try: mvn -U clean install. The -U parameter fo

here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Can't execute jar- file: “no main manifest attribute” up vote 332 down vote favorite 68 I have installed an application, when I try to run it (it's an executable jar) nothing happens. When I run it from the commandline with: java -jar "app.jar" I get the following message: no main manifest attribute, in "app.jar" Normally, if I had created the program myself, I would have added a main class attribute to the manifest file. But in this case, since the file is from an application, i cannot do that. I also tried extracting the jar to see if I could find the main class, but there are to many classes and none of them has the word "main" in it's name. There must be a way to fix this because the program runs fine on other systems. java jar manifest main share|improve this question edited Jul 14 '15 at 13:29 Matthijs Wessels 3,07343376 asked Mar 13 '12 at 18:20 Ewoud 1,7852911 Look for main methods; you can't rely on class names. –Dave Newton Mar 13 '12 at 18:22 1 I know, but since I only have .class files I can't really see the methods. Or can I? –Ewoud Mar 13 '12 at 18:42 You aren't really typing the quotes, are you? In any case, there are a number of ways to see methods, include using javap. You might want to un-jar it and look to see if there's actually no manifest, though. –Dave Newton Mar 13 '12 at 19:37 Related: with dependencies: stackoverflow.com/a/23986765/360211 –weston Sep 13 '15 at 7:37 add a comment| 20 Answers 20 active oldest votes up vote 335 down vote First, it's kind of weird, to see you run java -jar "app" and not java -jar app.jar Second,