You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by bo...@werken.com on 2002/11/30 03:07:08 UTC

[maven-bug] Closed: (MAVEN-165) project.xml and forehead.conf refer to different xerces

Message:

   The following issue has been closed.

   Resolver: dion gillard
       Date: Fri, 29 Nov 2002 8:07 PM

Fixed today by changing forehead.conf to 2.0.2
---------------------------------------------------------------------
View the issue:

  http://jira.werken.com/secure/ViewIssue.jspa?key=MAVEN-165


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MAVEN-165
    Summary: project.xml and forehead.conf refer to different xerces
       Type: Bug

     Status: Closed
   Priority: Blocker
 Resolution: FIXED

 Time Spent: Unknown
   Estimate: 0 minutes

    Project: maven
  Component: core
   Versions:
             1.0-beta-8

   Assignee: Jason van Zyl
   Reporter: Aslak Hellesøy

    Created: Fri, 29 Nov 2002 7:31 AM
    Updated: Fri, 29 Nov 2002 8:07 PM

Description:
jakarta-turbine-maven/project.xml and
jakarta-turbine-maven/src/bin/forehead.conf refer to a different xerces.
project.xml says 2.0.2 (so 2.0.2 is downloaded), but forehead.conf says
2.2.1 which isn't found, and Forehead tries to make a URL out of it and
crashes on the line where it tries to do a new URL( line ).

    protected void loadFileOrUrl(String line,
                                 ForeheadClassLoader loader) throws
MalformedURLException
    {
        URL url = null;

        File file = new File( line );

        if ( file.exists() )
        {
            url = file.toURL();
        }
        else
        {
            url = new URL( line );
        }

        loader.addURL( url );
    }

The line variable has the value of a non-existant file (xerces-2.2.1.jar).

Updating project.xml to use xerces 2.2.1 fixes this bug.


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

If you think it was sent incorrectly contact one of the administrators:
   http://jira.werken.com/Administrators.jspa

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