Re: JPackage-discuss Digest, Vol 64, Issue 11

Hi August,

There are some pre-built 'tomcat-native' rpms available in Fedora extras
and EPEL (for RHEL, Centos and derivatives).

Last I checked these were for version 1.0.18 not 1.0.20 but I just used
the same spec file from the source rpms and rebuilt it with 1.0.20
(without the patch since its already in the source in version 1.0.20)

Regards,

Brett

On Fri, 2010-06-11 at 12:00 +0200, [email protected]
wrote:
> Send JPackage-discuss mailing list submissions to
> 	[email protected]
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://www.zarb.org/mailman/listinfo/jpackage-discuss
> or, via email, send a message with subject or body 'help' to
> 	[email protected]
> 
> You can reach the person managing the list at
> 	[email protected]
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of JPackage-discuss digest..."
> 
> 
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email 
> ______________________________________________________________________
> Today's Topics: 1. Your Bugzilla bug list needs attention. ([email protected]) 2. using APR with jpackage tomcats (August Simonelli)
> e-mail message attachment
> > -------- Forwarded Message --------
> > From: [email protected]
> > Reply-to: Discussion about JPackage project
> > <[email protected]>
> > To: jpackage-discuss-/[email protected]
> > Subject: [JPackage-discuss] Your Bugzilla bug list needs attention.
> > Date: Fri, 11 Jun 2010 00:04:37 +0200 (CEST)
> > 
> > [This e-mail has been automatically generated.] You have one or more bugs assigned to you in the Bugzilla bug tracking system (https://www.jpackage.org/bugzilla/) that require attention. All of these bugs are in the NEW orREOPENED state, and have not been touched in 7 days or more. You need to take a look at them, and decide on an initial action. Generally, this means one of three things: (1) You decide this bug is really quick to deal with (like, it's INVALID), and so you get rid of it immediately. (2) You decide the bug doesn't belong to you, and you reassign it to someone else. (Hint: if you don't know who to reassign it to, make sure that the Component field seems reasonable, and then use the "Reassign bug to default assignee of selected component" option.) (3) You decide the bug b
 elongs to you, but you can't solve it this moment. Just use the "Accept bug" command. To get a list of all NEW/REOPENED bugs, you can use this URL (bookmark it if you like!): https://www.jpa
 ckage.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=REOPENED&assigned_to=jpackage-discuss-/[email protected] Or, you can use the general query page, at https://www.jpackage.org/bugzilla/query.cgi Appended below are the individual URLs to get to all of your NEW bugs that haven't been touched for 7 days or more. You will get this message once a day until you've dealt with these bugs! Feature list for JPP 5.0 -> https://www.jpackage.org/bugzilla/show_bug.cgi?id=20 %post dependencies should be "Requires(post)" -> https://www.jpackage.org/bugzilla/show_bug.cgi?id=134 Wrong test for %{fontdir} value -> https://www.jpackage.org/bugzilla/show_bug.cgi?id=135 mailcap.bak file referred i.s.o. mailcap -> https://www.jpackage.org/bugzilla/show_bug.cgi?id=136 Support parallel install of multiple version
 s of a package -> https://www.jpackage.org/bugzilla/show_bug.cgi?id=143 JabRef package -> https://www.jpackage.org/bugzilla/show_bug.cgi?id=163 JCalendar: Java date chooser bean for graphica
 lly picking a date -> https://www.jpackage.org/bugzilla/show_bug.cgi?id=164 need a uniform way to specify per-user and per-app SDKs and SPIs -> https://www.jpackage.org/bugzilla/show_bug.cgi?id=171 need dependency-resolving classpath-creation script -> https://www.jpackage.org/bugzilla/show_bug.cgi?id=172 Upgrade jfreechart to 1.0.3 -> https://www.jpackage.org/bugzilla/show_bug.cgi?id=177 jgoodies-looks package -> https://www.jpackage.org/bugzilla/show_bug.cgi?id=181 Package for NetBeans Platform 5.0 -> https://www.jpackage.org/bugzilla/show_bug.cgi?id=197 Update blackdown 1.4.2 to update 03 and amd64 -> https://www.jpackage.org/bugzilla/show_bug.cgi?id=207 java3d 1.4.0-01 package submission -> https://www.jpackage.org/bugzilla/show_bug.cgi?id=225 JEdit does not work at all after the upgr
 ade on FC5 -> https://www.jpackage.org/bugzilla/show_bug.cgi?id=226 build-classpath and build-jar-repository silently fail with invalid path -> https://www.jpackage.org/bugzilla/show_bug.cgi
 ?id=239 NetBeans 6.0 Platform spec file -> https://www.jpackage.org/bugzilla/show_bug.cgi?id=240 xml-commons-jaxp-1.3-apis Obsoletes: is too vague. -> https://www.jpackage.org/bugzilla/show_bug.cgi?id=266 yum depencies error Fedora Core 6 -> https://www.jpackage.org/bugzilla/show_bug.cgi?id=281 rpm name conflicts with game 'crimson fields' -> https://www.jpackage.org/bugzilla/show_bug.cgi?id=290 jedit will not start on fedora 10 -> https://www.jpackage.org/bugzilla/show_bug.cgi?id=310 [PATCH] fop fails if JAVACMD_OPTS is set -> https://www.jpackage.org/bugzilla/show_bug.cgi?id=313 gnu-crypto RPM build without gcj support requires gcj-compat packages -> https://www.jpackage.org/bugzilla/show_bug.cgi?id=320 circular build dependencies -> https://www.jpackage.org/bugzilla/show_bug.cgi?id=321
 
> e-mail message attachment
> > -------- Forwarded Message --------
> > From: August Simonelli <[email protected]>
> > Reply-to: Discussion about JPackage project
> > <[email protected]>
> > To: jpackage-discuss <[email protected]>
> > Subject: [JPackage-discuss] using APR with jpackage tomcats
> > Date: Fri, 11 Jun 2010 09:18:52 +1000
> > 
> > Hi All, Just want to check if my logic is right here. I'm using the tomcat6 packages from jpackage. I'd like to use with APR with them. Setting this up with a src tomcat is pretty well documented and easy. For jpackage do i need to do anything different? I was going to 1. grab the tomcat src matching the jpackage tomcat version i have 2. install apr-devel rpm 3. unpack the tomcat-native tarball from the tomcat src's bin 4. build as normal (ie as per the tomcat doc) so i have apr libraries in /usr/local/apr/lib that i can just point at with LD_LIBRARY_PATH There's not a "jpackage way" i would be better following (ie there's not a jpackage package for the tomcat native sources is there)? Thanks, August
> _______________________________________________ JPackage-discuss mailing list [email protected] https://www.zarb.org/mailman/listinfo/jpackage-discuss

-- 
Best Regards,

Brett Delle Grazie

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________