Showing messages 1 through 3 of 3.

• java via yum
  2005-06-21 23:29:27  Timothy M. O'Brien | [Reply | View]
  
  
  Replying to this post way too late. But, a word to the wise, stay as far away from jpackage as you can, as you will rue the day you got into that mess.
  
  For one, the jpackage RPMs are not updated with any kind of frequency, and unless you are looking to involve yourself and actually learn how to create RPM specs, you are going to just be out of luck on a number of levels.
  
  Second, the directory structures and proliferation of symbolic links to things like jars (which all have fun filenames like [junit.jar] with those wacky brackets). Test 1, install Tomcat 5 through jpackage, use it for a few months, then try to upgrade to a version not in the Jpackage RPM repository. Possible, but nasty. FHS compliant, but annoying as anything.
  
  Third, installing Java via the RPM from Sun is easy enough, sure it isn't being managed by yum, but
  
  Fourth, shared jars are kind of a PITA when it comes to classloader issues. Sharing commons-beanutils with a common install just because you can doesn't make sense.
  
  Go ahead, try it, you'll see - jpackage will make you wish you had just downloaded tgz and followed the simple instructions.
  

• java via yum
  2004-05-26 12:53:45  ChrisHuntley [Reply | View]
  
  
  Actually, the sun JDK is in the "non-free" section of jpackage. You have to create your own rpm by combining the jpackage "source" rpm with Sun's binary installer.
  
  It's not too painful, but its certainly not as simple as
  
  yum install j2sdk
  
  You'll have to repeat the process for all the standard extensions like JavaMail and such.
  
  Try
  
  yum install tomcat4
  
  to see what I mean.

• java via yum
  2004-05-22 11:33:33  Chris DiBona | [Reply | View]
  
  
  I knew it had to be true, thanks Mark!
  

  
  Chris