Yeah - The Tomcat RPM on JPackage has all that init script stuff built in as well.
What I have in mind is a catchall mojo. It should work in any build - for any build requirements. JPackage requirements are that the entire build has to be repeated by the RPM. So it would embed a mvn build to rebuild the source and place it in the spec BuildRoot location. It's a little weird that way. We build the RPM, while we are executing a build, and then when the RPM is installed, it executes the build again. When it executes the build again, it puts the files in locations that the build normally puts them. Then this has to be mapped to an FHS file layout. This has to be a manually configured map... So everything is reshuffled in the BuildRoot, or links are generated. I have to figure out exactly how they are doing it still. Anyways - As you might be suspecting - I need to clarify some stuff - but the mojo(s) should be catchall, so that everyone can use it. Thus it may borrow some code from our stuff, codehaus, and introduce new stuff. Who knows, maybe it will be all brand new stuff. I mainly just wanted to post codehaus, so that they are aware. Cheers, - Ole --- Alex Karasulu <[EMAIL PROTECTED]> wrote: > Ole, > > Make sure you don't overlook the fact that this > daemon plugin is more > than just an RPM generator. It's got specific > layout requirements in > mind and it also adds the daemon jsvc native > executable to the rpm along > with an init script. > > Sounds though that you are trying to consolidate > some efforts between > multiple maven plugin implementations. The other > guys may not be > interested in what we have done here for RPMs of > libs or non-server > applications. > > Alex > > Ole Ersoy wrote: > > Wow - That's terrific. > > > > I'm going through the following sequence just to > get > > my bearings (Sorry if I'm being repetitive - Just > want > > to make sure I set the context properly): > > > > Understand how the Tomcat RPM was done > > - This means understanding how the Tomcat build > file > > layout maps to the FHS file layout used in the > > JPackage RPM ... So I can understand how > everything > > was linked using the new FHS file structure. > > - Understanding the updating process used for > > configuration files (Including jakarta daemon jsvc > / > > unix wrapper / log rotate configuration > configuration, > > etc.) > > - Run permissions / file ownership > > - Run level configuration / startup / shutdown > scripts > > - etc. > > > > I want to get this into a nice clean little > document. > > > > Bastiaan once this is done I'd love to get your > ideas > > put inserted. > > > > Incidentally - Our rpm packaging mojo here: > > > > > http://svn.apache.org/repos/asf/directory/trunks/daemon/plugin > > > > is different from this one right? > > > > http://mojo.codehaus.org/rpm-maven-plugin/pom.html > > > > I'm sending out an email suggesting that JPackage > host > > one right after this mail. I think JPackage would > be > > the logical home, since they are maintaining the > FHS > > process around building the packages anyways.... > > > > Side note, just so everyone understands, JPackages > are > > just RPMS built so that they fit the FHS standard. > > > The JPackage group are doing this by hand / > manually. > > They have a utilities rpm for helping with the > shell > > scripting. > > > > Thoughts? > > > > OK - Back to documenting. > > > > Cheers, > > - Ole > > > > --- Alex Karasulu <[EMAIL PROTECTED]> wrote: > > > >> Ole, > >> > >> If you intend to use jpackage see if you can add > the > >> functionality > >> straight into the daemon rpm here: > >> > >> > > > http://svn.apache.org/repos/asf/directory/trunks/daemon/plugin > >> Basically this daemon plugin is a dual purpose > >> plugin. It makes your > >> java app into a daemon on UNIX and a Windows > Service > >> on windows > >> platforms using jakarta daemon jsvc and procrun > >> respectively. > >> > >> The neat thing about this plugin is that it does > >> that and generates > >> installers for your server application as well as > >> RPM packages. > >> > >> It's the RPM part we want to replace so it uses > >> jpackage instead of the > >> rpmbuild executable. That should be easy to do. > >> > >> Thanks, > >> Alex > >> > >> P.S. Bastiaan also had some ideas for improving > this > >> plugin. Perhaps > >> you guys can work together on improving our > >> packaging/installer > >> generating plugin. > >> > >> Bastiaan Bakker wrote: > >>> On Tue, 2006-10-24 at 11:56 +0200, Emmanuel > >> Lecharny wrote: > >>>> Hi Bastiaan, > >>>> > >>>> I have created another JIRA, > >>>> > >> > https://issues.apache.org/jira/browse/DIRSERVER-765, > >> which is related > >>>> to RPM creation using jpackage > >> (www.jpackage.org). > >>> AH, great, a jpackage based RPM is even better. > >>> > >>>> Ole is trying to use it to create valid RPM. > >>>> > >>>> Feel free to add any comment to this JIRA, we > >> will use it to track any > >>>> progress on this task. > >>>> > >>> OK. > >>> > >>>> Emmanuel > >>>> > >>>> PS: can you use the dev list instead of sending > >> mails directly to me? > >>>> Some other committer may help you when I'm not > >> online ! > >>> Heh, in your last comment on DIRSERVER-749 you > >> told me to contact you if > >>> needed, so I did... ;-) > >>> But I'll go back to the dev list for discussion > on > >> 765. > >>> Bastiaan > >>> > >>> > >>>> On 10/24/06, Bastiaan Bakker > >> <[EMAIL PROTECTED]> wrote: > >>>> Hi Emmanuel, > >>>> > >>>> Now that ApacheDS 1.0 has been released > >> hopefully you have a > >>>> bit of time > >>>> again to go through the RPM packaging > >> patch in DIRSERVER-749 > >>>> with me. > >>>> When would be convienent? > >>>> > >>>> Regards, > >>>> > >>>> Bastiaan > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> -- > >>>> Cordialement, > >>>> Emmanuel Lécharny > >>> > >> > > > > > > __________________________________________________ > > Do You Yahoo!? > > Tired of spam? Yahoo! Mail has the best spam > protection around > > http://mail.yahoo.com > > > > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
