You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@geronimo.apache.org by de...@geronimo.apache.org on 2004/10/04 21:36:32 UTC

[jira] Commented: (GERONIMO-356) tomcat-plan.xml : Missing Dependency mx4j/jars/mx4j-2.0.1.jar

The following comment has been added to this issue:

     Author: Jeremy Boynes
    Created: Mon, 4 Oct 2004 12:35 PM
       Body:
There should be no need for the dependency in the plan as these classes will be provided by the parent configurations.

I don't use Eclipse, but in Idea I set up libraries for each module to ensure the right jars are available for running it inside the IDE.
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/GERONIMO-356?page=comments#action_53682

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/GERONIMO-356

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: GERONIMO-356
    Summary: tomcat-plan.xml : Missing Dependency mx4j/jars/mx4j-2.0.1.jar
       Type: Task

     Status: Unassigned
   Priority: Major

    Project: Apache Geronimo
 Components: 
             buildsystem
             Tomcat
   Versions:
             1.0-M3

   Assignee: 
   Reporter: Ralf Barkow

    Created: Mon, 4 Oct 2004 12:18 PM
    Updated: Mon, 4 Oct 2004 12:35 PM

Description:
Eclipse reported an error in line 88 of TomcatGBean.java: 

    "The type javax.management.MBeanRegistration cannot be resolved.
     It is indirectly referenced from required .class files."


The error disappeared after adding 

    MAVEN_REPO/mx4j/jars/mx4j-2.0.1.jar

as classpath variable entry to the geronimo-tomcat project in my eclipse workspace.  

So, I think there is a dependency missing in tomcat-plan.xml
(see attached patch).  



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira