Re: tomcat 5.5.22 and jakarta-commons-modeler

Ok if I don't hear any complaints soon I'm going to move
jakarta-commons-modeler 2.0 to the main repo as an upgrade to 1.1
(i.e. only 2.0 will be in the repo).
Jason

On 2/27/07, Jason Corley <jason.corley@...> wrote:
> Just doing a quick grep for modeler through my CVS checkout yields the
> following list of packages that use jakarta-commons-modeler:
>
>     eclipse
>     geronimo11
>     jakarta-commons-jelly-tags-jmx
>     jboss4
>     jonas
>     tomcat5
>
> So those of you who have worked on these packages, do you know if
> jakarta-commons-modeler 2.0 will break these?  Will we need to keep
> both of them in the repo, or can we just upgrade?
> Jason
>

Your Bugzilla buglist needs attention.

[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  or  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 ),
    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 belongs to you, but you can't solve it this moment.
    Just use the "Accept bug" command.

To get a list of all / 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  bugs
that haven't been touched for a week or more.

noarch eclipse-ecj only package in devel

All,
I've uploaded an eclipse-ecj only noarch package into the 1.7 devel
repo.  It's based on the JPackage 3.1.2 eclipse package, but much
smaller and simpler.  I had hoped to use the SRPM linked to by Andrew
Overholt earlier but alas it was nowhere to be found at this
significantly later date.  The package lacks the gcj bits but should
be sufficient for testing purposes.  The question now is how does our
user base feel about eclipse being dropped from jpackage altogether in
favor of this small noarch ecj only package.
Jason

Re: noarch eclipse-ecj only package in devel

Hi,

* Jason Corley <jason.corley@...> [2007-03-02 14:38]:
> I've uploaded an eclipse-ecj only noarch package into the 1.7 devel
> repo.  It's based on the JPackage 3.1.2 eclipse package, but much
> smaller and simpler.  I had hoped to use the SRPM linked to by Andrew
> Overholt earlier but alas it was nowhere to be found at this
> significantly later date.

I couldn't find the exact one I put up back then (stupid
people.redhat.com disk limitations forced me to delete it), but I've put
one that we considered for Fedora 7 up here:

http://www.overholt.ca/eclipse/ecj-3.2.1-1.fc7.src.rpm

I'm sure it's very similar to what you did, Jason, but just in case you
wanted to compare to see how bad mine was ;).  The one thing that's
important to note is that gcj is now using ecj's bytecode compiler in
its frontend.  As such, it'd be great if Fedora and JPackage didn't
stomp on each other's ecj / eclipse-ecj packages/jars.  Perhaps JPackage
can just stick with the name ecj instead of eclipse-ecj and name the
jars similarly?

Andrew

_______________________________________________
JPackage-discuss mailing list
JPackage-discuss@...
https://www.zarb.org/mailman/listinfo/jpackage-discuss

Your Bugzilla buglist needs attention.

[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  or  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 ),
    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 belongs to you, but you can't solve it this moment.
    Just use the "Accept bug" command.

To get a list of all / 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  bugs
that haven't been touched for a week or more.

Cannot rebuild JDK 6

Hi,

I've a problem with rebuilding JPackage's JDK 6.

So, I've been reading the following page :
http://www.jpackage.org/installation.php

* In the past, I used to rebuild the "nosrc" method, but unfortunately,
the "nosrc" file for "java-1.6.0" is missing in :
ftp://jpackage.hmdc.harvard.edu/JPackage/1.7/generic/RPMS.non-free/
Is that normal? If not, it would be a valuable upload.

* So I switched to the "compat" method. I downloaded
java-1.6.0-sun-compat-1.6.0-1jpp.i586.rpm from the same directory, but
when I try to install this file, rpm complains about a missing "jdk"
dependency ("jdk = 2000:1.6.0-fcs is needed"). Does that mean that I
have to install Sun's RPM before? If so, I think you should write it
clearly in installation.php because it's not so obvious. If not, what
should I do to resolve this dependency?

Thanks for reading and have a nice day,

Grégoire

Cannot rebuild JDK 6

Hi,

I've a problem with rebuilding JPackage's JDK 6.

So, I've been reading the following page :
http://www.jpackage.org/installation.php

* In the past, I used to rebuild the "nosrc" method, but unfortunately,
the "nosrc" file for "java-1.6.0" is missing in :
ftp://jpackage.hmdc.harvard.edu/JPackage/1.7/generic/RPMS.non-free/
Is that normal? If not, it would be a valuable upload.

* So I switched to the "compat" method. I downloaded
java-1.6.0-sun-compat-1.6.0-1jpp.i586.rpm from the same directory, but
when I try to install this file, rpm complains about a missing "jdk"
dependency ("jdk = 2000:1.6.0-fcs is needed"). Does that mean that I
have to install Sun's RPM before? If so, I think you should write it
clearly in installation.php because it's not so obvious. If not, what
should I do to resolve this dependency?

Thanks for reading and have a nice day,

Grégoire

Re: FC6 Java/Tomcat5 Install Problem

Issue resolved. Tomcat now runs.
Solution summary: Removed Jakarta packages and reinstalled them from the
jpackage-generic repository.

Solution details:

Jason recommended " You'll need to remove those and use yum to install only
from jpackage repositories (--enablerepos=)"

Where I interpret the word, "those" above to refer to the list of jpp
packages found using this command:
rpm -qa --qf "%{NAME} %{RELEASE}\n" |awk '/jpp/ && !/jpackage-utils/ {print
$1}'

After a fresh install of fedora core 6, it still doesn't make sense to me to
remove all those packages along with their dependencies and reinstall from
the Jpackage repository especially since that repository does not have all
the packages that would be removed.
In an attempt to isolate the problem I decided to only remove the Jakarta
and Tomcat packages. Tomcat's logfile, /var/log/tomcat5/catalina.out pointed
to a java.lang.NoClassDefFoundError in
org/apache/commons/modeler/BaseModelMBean which I believe is in the
jakarta-commons-modeler package. I used rpm's --nodep command line variable
even though posts I've read, advise against it.

I edited /etc/yum.repos.d *.repos files. I verified each files' "enabled"
variable was set to zero just to make sure I install only from Jpackage
repository.

I removed only the following:

Your Bugzilla buglist needs attention.

[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  or  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 ),
    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 belongs to you, but you can't solve it this moment.
    Just use the "Accept bug" command.

To get a list of all / 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  bugs
that haven't been touched for a week or more.

Your Bugzilla buglist needs attention.

[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  or  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 ),
    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 belongs to you, but you can't solve it this moment.
    Just use the "Accept bug" command.

To get a list of all / 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  bugs
that haven't been touched for a week or more.