headers
Ville Skyttä | 3 Jan 2003 00:48
Picon
Picon
Favicon

Re: Tomcat LE builds

> I see on www.jpackage.org that you packaged tomcat4 into RPMs. Thank you
> for this very useful public service, but I have one request. I normally
> use the "le" versions of tomcat4 from http://jakarta.apache.org/builds,
> which does not require a host of other libraries which I do not use in
> my application. I would like to see the "le" versions available on
> www.jpackage.org, as it seems to take some time for Apache to release
> RPMs themselves.

Thanks for your feedback, Terence, but please use the jpackage-discuss
mailing list in the future.  See <http://www.jpackage.org/contacts.php>
for more information.

I don't actually know that much of the JPackage Tomcat RPMs, Henri Gomez
usually builds them.  Henri also builds the official jakarta.apache.org
Tomcat RPMs, so the JPackage and Jakarta ones should be usually well in
sync.

However, when 4.1.18 was released, Henri was unavailable (IIRC he will
still be for a week or so); I only rolled a quick one since it's a
security update.  I'm sure the LE RPMs will be available from
jakarta.apache.org as soon as he's back.

--

-- 
\/ille Skyttä
ville.skytta at iki.fi
Permalink | Reply | 0 comments |
headers
Ville Skyttä | 3 Jan 2003 08:07
Picon
Picon
Favicon

Re: RPMS for Non-Free and TomCat4-4.1.18

> I am trying to install your RPM for Tomcat4 version 4.1.18 so that I 
> can use uPortal and there is no RPMs for some of the files and 
> Tomcat4 will not install until it finds them.

Ben, please use the JPackage mailing lists for all project-related
discussion.

For legal reasons, we cannot provide binary RPMs of everything.  See
<http://www.jpackage.org/rebuilding.php> for rebuilding instructions.

Be more specific about the problem and see my yesterday's post at
<http://lists.zarb.org/pipermail/jpackage-discuss/2003-January/000096.html>
for a info about Tomcat RPM status.

--

-- 
\/ille Skyttä
ville.skytta at iki.fi
Permalink | Reply | 0 comments |
headers
Guillaume Rousse | 5 Jan 2003 00:00
Picon

Re: JNDI and javadoc121.zip

Le Mardi 31 Décembre 2002 16:31, Matt Helmick a écrit :
> Dear Mr. Rousse,
>
> When attempting to install the JPackage for JNDI, I could not find the
> source file on Sun's site, "javadoc121.zip" that was noted in the spec
> file and it doesn't seem to be able to install without it.
I guess Sun once again changed their website :-(

> Is there a workaround or am I just doing something wrong?
Just apply this patch to the spec, you won't have javadoc available, but at 
least you'll have the binary.

> By the way, thanks for your work on several of the JPackages, I have
> installed a few already.
>
> It is the last source I need to compile to run Tomcat, so I am kind of
> anxious!
You should use jpackage-discuss for any jpackage question, instead of my 
personal adress, answers generally comes faster :-)
--

-- 
Software bugs are impossible to detect by anybody except the end user. 
	-- Murphy's Computer Laws n°10
Attachment (jndi.spec.patch): text/x-diff, 1291 bytes
Permalink | Reply | 1 comment |
headers
Matt Helmick | 5 Jan 2003 01:12
Picon

Re: Re: JNDI and javadoc121.zip

Apologies, I will keep my questions isolated to the JPackage-discuss 
list from now on.  Thanks for the new spec.

Guillaume Rousse wrote:

>Le Mardi 31 Décembre 2002 16:31, Matt Helmick a écrit :
>  
>
>>Dear Mr. Rousse,
>>
>>When attempting to install the JPackage for JNDI, I could not find the
>>source file on Sun's site, "javadoc121.zip" that was noted in the spec
>>file and it doesn't seem to be able to install without it.
>>    
>>
>I guess Sun once again changed their website :-(
>
>  
>
>>Is there a workaround or am I just doing something wrong?
>>    
>>
>Just apply this patch to the spec, you won't have javadoc available, but at 
>least you'll have the binary.
>
>  
>
>>By the way, thanks for your work on several of the JPackages, I have
>>installed a few already.
>>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Victor Lewis | 8 Jan 2003 17:29

Tomcat4.1 LE

I understand from a previous post that the gentleman who usually packages
Tomcat is unavailable and that is the reason for the LE (the one which runs
with JDK 1.4) is missing.  Might anyone out there have a copy of an old
Tomcat 4.1 LE build (i.e. prior to 4.1.18) which could be used in the
interim by those of us who would prefer an old LE build to none.

Thanks,
  Victor

Victor Lewis, Director of Software Development
New Course Analytics
Makers of ProCourse ROI Software
919-403-3770 www.procourse.com 

ProCourse is the industry's first true ROI tool. ProCourse can isolate the
effects of business interventions such as training from the total business
impact. ProCourse not only identifies which interventions are working, but
also optimizes the impact of those interventions, adding significant revenue
to your bottom line. You can view a Flash demo of ProCourse here:
<http://www.procourse.com/demo/>

This message (including any attachments) contains confidential information
intended for a specific individual and purpose, and is protected by law. If
you are not the intended recipient, you should delete this message and are
hereby notified that any disclosure, copying, or distribution of this
message, or the taking of any action based on it, is strictly prohibited.
Permalink | Reply | 1 comment |
headers
Henri Gomez | 8 Jan 2003 18:09
Picon

Re: Tomcat4.1 LE

Victor Lewis wrote:
> I understand from a previous post that the gentleman who usually packages
> Tomcat is unavailable and that is the reason for the LE (the one which runs
> with JDK 1.4) is missing.  Might anyone out there have a copy of an old
> Tomcat 4.1 LE build (i.e. prior to 4.1.18) which could be used in the
> interim by those of us who would prefer an old LE build to none.

Uploaded today the 4.1.18 full and le to jakarta site ;-)
Permalink | Reply | 0 comments |
headers
Brad Smith | 10 Jan 2003 23:48

Tomcat4 & SDK 1.4.1


Greetings -

I use apt-get to retrieve packages from jpackage and other sources. I
recently installed tomcat4 4.1.18 using --force to skip over the jaas
and jndi requirements as I have Sun's SDK 1.4.1 installed. I find now,
however, that apt-get complains about the missing dependancies (jaas and
jndi) and basically fails to do anymore processing. I know there are new
packages on some other sites that I would like to update with apt-get
but am currently blocked.

As I see it I have a couple of options:

1. Uninstall the tomcat4 rpms and use the full rpms directly from
Jakarta.
2. Install jaas and jndi packages even though they are redundant with
current java SDK on this system.
3. Wait until the JPackage team offer a solution.

I looked for some command-line toggles for apt-get to override the
missing dependencies issue but could not find one (ie ignore-missing did
not do anything).

Am I missing anything?

Thanks,

Brad
(Continue reading)

Permalink | Reply | 9 comments |
headers
Victor Lewis | 10 Jan 2003 23:57

Re: Tomcat4 & SDK 1.4.1

I got along fine by getting the Tomcat4-LE RPM from the Jakarta site and
installing that, it does not deepened on those packages which are already in
1.4.

Another note, I had some headless problems with 1.4.1 and had to fall back
to 1.4.0_03.

-Victor

----- Original Message -----
From: "Brad Smith" <bgsmith@...>
To: <jpackage-discuss@...>
Sent: Friday, January 10, 2003 5:48 PM
Subject: [Jpackage-discuss] Tomcat4 & SDK 1.4.1
Permalink | Reply | 0 comments |
headers
Doug Collinge | 11 Jan 2003 00:29

Re: Tomcat4 & SDK 1.4.1

Apropos of this,  why can't the non-free packages simply do nothing at 
all except advertise what the product provides?  Take the Sun j2sdk 
1.4.1 for example.  Get it from Sun, install it however Sun thinks it 
should install,  and now install the non-free package.  It checks to see 
if sun j2sdk 1.4.1 is installed in the expected place, loads the 
dependencies that j2sdk 1.4.1 satisfies into the rpm database, and then 
exits.

This strategy would remove all that futzing around with building rpms 
you have to do now, which is a stumbling block for the common klutz like 
me.  What's more, when you update from j2sdk 1.4.1 to j2sdk 1.4.1_01, 
there isn't really anything to do as  long as the sdk ends up in the 
same place. With symlinks or whatever.

It seems to me that this would work ok with all the non-free software.  
You can't install it with urpmi or apt-get but you can't do that now 
either unless you or someone else has built them already.

Brad Smith wrote:

>Greetings -
>
>I use apt-get to retrieve packages from jpackage and other sources. I
>recently installed tomcat4 4.1.18 using --force to skip over the jaas
>and jndi requirements as I have Sun's SDK 1.4.1 installed. I find now,
>however, that apt-get complains about the missing dependancies (jaas and
>jndi) and basically fails to do anymore processing. I know there are new
>packages on some other sites that I would like to update with apt-get
>but am currently blocked.
>
(Continue reading)

Permalink | Reply | 7 comments |
headers
Keith Irwin | 11 Jan 2003 08:50

Axis / Eclipse

Folks--

Any particular reasons apache Axis (the preferred SOAP implementation in
java) and eclipse, the IDE, aren't packged up for the web site?

Keith
Permalink | Reply | 3 comments |

Gmane