<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
<br>hello Florian<br><br>> Well, the model RPM uses is - as far as I understand - a bit different <br>> from what most web applications do. RPM puts files to a fixed place on <br>> the file system. If $JBOSS_HOME is a dynamically set variable RPM won't <br>> be that good in dealing with it. If it is something you define once for <br>> all users of the RPM you should be fine.<br><br>$JBOSS_HOME will be set to the _SAME_ location on every server.<br><br>$JBOSS_HOME is really /var/lib/jboss-4.2.3.GA<br><br>however i have a symbolic link set to the specific version of jboss. everything refers to the symbolic link.<br><br>example:<br><br>ln -s /var/lib/jboss-4.2.3.G /var/lib/jboss /var/lib/jboss<br><br>root@PrimexAMP ~ > cat .bashrc | grep JBOSS_HOME<br>export
JBOSS_HOME=/var/lib/jboss<br><br><br><br><br>> <br>> Same with the version numbers. RPM packages with the same name are <br>> supposed to be one line of updates. So if you have foo-1.0 installed it <br>> is going to be updated with foo-2.0 even automatically (if you configure <br>> you system accordingly). If you want it to be a real choice you <br>> typically include the major version into the package name:<br>> <br>> foo1-1.0.0 that is updated to foo1-1.0.1<br>> and foo2-2.0.0 that is updated to foo2-2.0.1 or foo2-2.1.0<br>> <br><br>are you saying that i cannot use my existing version number scheme?<br><br>right now our ant / java build environment supports this kind of versioning scheme:<br><br>if i were to tag and build the code right now i would produce this:<br><br>PWEL-EJB-2.5.0.9/<br><br>which would build PWEL-EJB.jar<br><br>i was hoping to package this jar file in to a single rpm named:<br><br>pwel-ejb-2.5.0.9.rpm<br><br>is this a reasonable approach ?<br><br><br><br><br>> If foo1 and foo2 contain the same files you should set a conflict <br>> between them.<br><br>ok - you lost me here.<br><br>probably my largest use case will be the supplanting or replacement of jar files in the jboss deployment directory.<br><br>example 1:<br><br>pwel-ejb-2.5.0.9.rpm is installed on the server.<br><br>pwel-ejb-2.5.0.9.rpm has as single jar file in it - PWEL-EJB.jar<br><br>this file would be deployed to:<br><br>$JBOSS_HOME/server/default/deploy/<br><br>and over write ANY other file with that SAME name.<br><br>this is the way jboss works - you simply drop the new jar file in to the /deploy directory and jboss does the rest.<br><br>this is a simple use case - but an important one for me.<br><br>example 2: <br><br>pwel-ejb-2.5.0.9.rpm is installed on the server.<br>
<br>
pwel-ejb-2.5.0.9.rpm has:<br> <br> 1) a jar file ( PWEL-EJB.jar) <br> 2) a mysql database script.<br> 3) a shell (bash) script to run the database script<br>
<br>
the jar file would be deployed to:<br>
<br>
$JBOSS_HOME/server/default/deploy/<br>
<br>
and over write ANY other file with that SAME name.<br>
<br>rpm would invoke the shell script which in turn would run the database script.<br><br><br>does all of this make sense from an rpm perspective ?<br><br><br>thank you,<br>mark<br><br><br> </body>
</html>