You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cactus-dev@jakarta.apache.org by ca...@jakarta.apache.org on 2004/08/25 21:45:20 UTC

[jira] Commented: (CACTUS-80) tools.jar not found from within Eclipse

The following comment has been added to this issue:

     Author: Vincent Massol
    Created: Wed, 25 Aug 2004 12:44 PM
       Body:
For the record, the code to be fixed is the following:

    protected final File getToolsJar() throws FileNotFoundException
    {
        String javaHome = System.getProperty("java.home"); 
        File toolsJar = new File(javaHome, "../lib/tools.jar");
        if (!toolsJar.isFile())
        {
            throw new FileNotFoundException(toolsJar.getAbsolutePath());
        }
        return toolsJar;
    }   



---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/CACTUS-80?page=comments#action_37463

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/CACTUS-80

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: CACTUS-80
    Summary: tools.jar not found from within Eclipse
       Type: Improvement

     Status: Unassigned
   Priority: Major

    Project: Cactus
 Components: 
             Ant Integration
   Fix Fors:
             1.7
   Versions:
             1.5

   Assignee: 
   Reporter: Simon Gibbs

    Created: Fri, 28 Nov 2003 5:09 PM
    Updated: Wed, 25 Aug 2004 12:44 PM
Environment: Operating System: Other
Platform: Other

Description:
This is specifically concerning the cactus ant tasks run from within Eclipse. 
This Bug was raised by request after a detailed discussion in Cactus Users.

As I understand it Eclipse isn't playing by the rules and is running Ant from 
within a JRE JVM instance rather than a JVM anchored to the SDK, with access to 
tools.jar. This is exasperated by some code within Cactus 
(AbstractJavaContainer according to Google) that makes various assumptions 
regarding the location of the file. Result is that tools.jar cannot be found.

For your analysis I include comparative output from my buildfile launched from 
the commandine and from Eclipse. Clearly my build is still not working but as 
far as I can tell that is another issue I will have to reasearch.

Eclipse:

      [cactus] -----------------------------------------------------------------
      [cactus] Running tests against Tomcat 4.1.29
      [cactus] -----------------------------------------------------------------
      [cactus] Deleting 4 files from C:\DOCUME~1\SIMONG~1.TRO\LOCALS~1
\Temp\cactus\tomcat4x
      [cactus] Deleted 2 directories from C:\DOCUME~1\SIMONG~1.TRO\LOCALS~1
\Temp\cactus\tomcat4x
      [cactus] Couldn't find tools.jar (needed for JSP compilation)
You must either set location or path on <pathelement>
	at org.apache.tools.ant.types.Path.list(Path.java:309)
	at org.apache.tools.ant.types.Path.list(Path.java:320)
	at org.apache.tools.ant.types.Path.addExisting(Path.java:260)
	at org.apache.tools.ant.types.Path.concatSystemClasspath(Path.java:551)
	at org.apache.tools.ant.types.CommandlineJava.size
(CommandlineJava.java:346)
	at org.apache.tools.ant.types.CommandlineJava.getCommandline
(CommandlineJava.java:248)
	at org.apache.tools.ant.types.CommandlineJava.describeCommand
(CommandlineJava.java:311)
	at org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:138)
	at org.apache.tools.ant.taskdefs.Java.execute(Java.java:108)
	at 
org.apache.cactus.integration.ant.container.tomcat.AbstractCatalinaContainer.inv
okeBootstrap(AbstractCatalinaContainer.java:214)
	at 
org.apache.cactus.integration.ant.container.tomcat.Tomcat4xContainer.startUp
(Tomcat4xContainer.java:98)
	at org.apache.cactus.integration.ant.container.ContainerRunner$1.run
(ContainerRunner.java:179)
	at java.lang.Thread.run(Thread.java:536)
      [cactus] BUILD FAILED: file:H:/Finance/Finance 
Projects/Development/Finance Reporting App/tomcatProject/build.xml:139: Failed 
to start the container after more than [60000] ms. Trying to connect to the 
[http://localhost:8080/reportingapp/ServletRedirector?Cactus_Service=RUN_TEST] 
test URL yielded a [-1] error code. Please run in debug mode for more details 
about the error.


Command Line:

   [cactus] -----------------------------------------------------------------
   [cactus] Running tests against Tomcat 4.1.29
   [cactus] -----------------------------------------------------------------
   [cactus] Deleting 5 files from C:\DOCUME~1\SIMONG~1.TRO\LOCALS~1\Temp\cactus\
tomcat4x
   [cactus] Deleted 8 directories from C:\DOCUME~1\SIMONG~1.TRO\LOCALS~1\Temp\ca
ctus\tomcat4x

BUILD FAILED
file:H:/Finance/Finance%20Projects/Development/Finance%20Reporting%20App/tomcatP
roject/build.xml:140: Failed to start the container after more than [60000] ms.
Trying to connect to the [http://localhost:8080/reportingapp/ServletRedirector?C
actus_Service=RUN_TEST] test URL yielded a [-1] error code. Please run in debug
mode for more details about the error.


---------------------------------------------------------------------
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


---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org