headers
jpackage | 2 Oct 2006 00:08
Favicon

Your Bugzilla buglist needs attention.

[This e-mail has been automatically generated.]

You have one or more bugs assigned to you in the Bugzilla 
bugsystem (https://www.jpackage.org/bugzilla/) that require
attention.

All of these bugs are in the NEW or REOPENED 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
    owner of selected component" option.)
(3) You decide the bug belongs 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.jpackage.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=REOPENED&assigned_to=jpackage-discuss-/hcidOUDYf1g9hUCZPvPmw <at> public.gmane.org

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
(Continue reading)

Permalink | Reply | 0 comments |
headers
Fernando Nasser | 2 Oct 2006 21:48
Picon
Favicon

Re: running multiple instances of tomcat5 on the same machine

So, as it seems that there are no objections, I will incorporate this 
contribution to our JPP 1.7 tomcat5 RPM tomorrow.

Fernando

Permaine Cheung wrote:
> Hi,
>
> I was trying to start multiple instances of tomcat on the same 
> machines simultaneously, I don't see an easy way to do it with the 
> current init script, so I tried to add that capability to it.
> With this patch, a user can start another tomcat service by creating a 
> second service by the following:
> 1. create a symlink for the new service in /etc/init.d/ to 
> /etc/init.d/tomcat5
> 2. create a sysconfig file for the new service in 
> /etc/sysconfig/≤service-name>, which name has to match with the 
> symlink created in the above step, edit this new file to update the 
> values for CATALINA_HOME, JASPER_HOME,, CATALINA_TMPDIR, 
> JAVA_ENDORSED_DIRS, CATALINA_PID and CONNECTOR_PORT (a new variable). 
> If this file does not exist, the original /etc/tomcat/tomcat5.conf 
> will be used.
> 3. create a new logrotate file for the new service by copying the one 
> from tomcat5 and updating the log file location, which should be 
> /var/log/≤service-name>.
> 4. start or stop the service by: service <service-name> start/stop
>
> When a new CATALINA_HOME is specified, I tried to copy the existing 
> /usr/share/tomcat5 to the new one, I'm not sure if that's the best 
> thing to do, but do not know of a better way.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Saba, Mitch | 2 Oct 2006 20:34
Picon
Favicon

Bring back the old site!

Don't like the new look and feel.  Not very user friendly.

Mitch Saba
Permalink | Reply | 2 comments |
headers
Jason Corley | 2 Oct 2006 23:44
Picon

Re: Bring back the old site!

Well you're the first person to complain (including all of the
JPackage committers) but to each their own.  The old site is still
available as a package browser (listed as Our Browser <version>) in
the Download section of the left hand menu.
    http://www.jpackage.org/browser/browse.php
Jason

On 10/2/06, Saba, Mitch <mitch.saba@...> wrote:
> Don't like the new look and feel.  Not very user friendly.
>
> Mitch Saba
>
> _______________________________________________
> JPackage-discuss mailing list
> JPackage-discuss@...
> https://www.zarb.org/mailman/listinfo/jpackage-discuss
>
Permalink | Reply | 1 comment |
headers
jpackage | 3 Oct 2006 00:08
Favicon

Your Bugzilla buglist needs attention.

[This e-mail has been automatically generated.]

You have one or more bugs assigned to you in the Bugzilla 
bugsystem (https://www.jpackage.org/bugzilla/) that require
attention.

All of these bugs are in the NEW or REOPENED 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
    owner of selected component" option.)
(3) You decide the bug belongs 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.jpackage.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=REOPENED&assigned_to=jpackage-discuss-/hcidOUDYf1g9hUCZPvPmw <at> public.gmane.org

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
(Continue reading)

Permalink | Reply | 0 comments |
headers
David Walluck | 3 Oct 2006 01:18
Favicon

Re: Bring back the old site!


Jason Corley wrote:
> Well you're the first person to complain (including all of the
> JPackage committers) but to each their own.  The old site is still
> available as a package browser (listed as Our Browser <version>) in
> the Download section of the left hand menu.
>     http://www.jpackage.org/browser/browse.php

Yeah, but on the other hand, repoview is IMO worse than our home grown
stuff for finding packages, yet it's the first choice listed. I mean,
it's organized/sorted by group, and it's unlikely anybody cares about that.

--
Sincerely,

David Walluck
<david@...>
Permalink | Reply | 0 comments |
headers
David Walluck | 3 Oct 2006 22:58
Favicon

Re: [JPackage-announce] [RPM (1.7)] tomcat5-5.5.17-7jpp


Permaine Cheung wrote:

>  <at>  <at>  -167,7 +258,7  <at>  <at> 
>          start
>          ;;
>    condrestart)
> -        if [ -f /var/run/tomcat5.pid ] ; then
> +        if [ -f /var/run/{$NAME}.pid ] ; then
>                  stop
>                  start
>          fi

Really? Or $NAME?

--
Sincerely,

David Walluck
<david@...>
Permalink | Reply | 1 comment |
headers
Permaine Cheung | 3 Oct 2006 23:04
Picon
Favicon

Re: [JPackage-announce] [RPM (1.7)] tomcat5-5.5.17-7jpp

Thanks for catching that, I have $NAME in other places. I'll wait to see 
if there's any other comment and upload another set of rpm tomorrow.

Cheers,
Permaine

David Walluck wrote:

>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>Permaine Cheung wrote:
>
>  
>
>> <at>  <at>  -167,7 +258,7  <at>  <at> 
>>         start
>>         ;;
>>   condrestart)
>>-        if [ -f /var/run/tomcat5.pid ] ; then
>>+        if [ -f /var/run/{$NAME}.pid ] ; then
>>                 stop
>>                 start
>>         fi
>>    
>>
>
>Really? Or $NAME?
>
>- --
(Continue reading)

Permalink | Reply | 0 comments |
headers
Peter Reilly | 4 Oct 2006 00:06
Picon

Fwd: Ant 1.7.0?

---------- Forwarded message ----------
From: jpackage-discuss-owner@... <jpackage-discuss-owner@...>
Date: Oct 3, 2006 10:57 PM
Subject: Re: Ant 1.7.0?
To: peter.kitt.reilly@...

The message's content type was not explicitly allowed

---------- Forwarded message ----------
From: "Peter Reilly" <peter.kitt.reilly@...>
To: jpackage-discuss@...
Date: Tue, 3 Oct 2006 22:50:14 +0100
Subject: Re: Ant 1.7.0?
Hi,

> Will Tatam has updated the package for us and I have uploaded it to JPP
>
> 1.7 'devel'.
>
> However, I had to disabl the manifest-only subpackage so I could build
> and uploaded it to JPP 1.7 devel, as those JARs are no longer being
> generated.  Lets see if someone can figure out why the MANIFEST-only
>
> JARs are not generated anymore in Ant 1.7.0.
>

This is due a change in the jar task, it will not make MANIFEST-only files if
the attribute "whenmanifestonly"="skip". This attribute is now used in
ant's  build.xml.
It can be overridden by setting the property
(Continue reading)

Permalink | Reply | 4 comments |
headers
jpackage | 4 Oct 2006 00:08
Favicon

Your Bugzilla buglist needs attention.

[This e-mail has been automatically generated.]

You have one or more bugs assigned to you in the Bugzilla 
bugsystem (https://www.jpackage.org/bugzilla/) that require
attention.

All of these bugs are in the NEW or REOPENED 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
    owner of selected component" option.)
(3) You decide the bug belongs 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.jpackage.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=REOPENED&assigned_to=jpackage-discuss-/hcidOUDYf1g9hUCZPvPmw <at> public.gmane.org

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
(Continue reading)

Permalink | Reply | 0 comments |

Gmane