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 2003/03/07 14:35:14 UTC

[maven-bug] New comment: (MAVEN-313) linkcheck plugin fails for any project that has nekohtml as a dependency

The following comment has been added to this issue:

     Author: Ben Walding
    Created: Fri, 7 Mar 2003 7:35 AM
       Body:
Most of the fixes for this are complete, just waiting to see if anyone else has any more problems.

1) Switched from httpunit to commons-httpclient and explicitly call jtidy.
2) Use dom4j xpath expressions to extract //a/@href and //img/@src items and check their validity.  I'm sure this list will need to be expanded.
3) The plugin is a lot noisier than it used to be.  As it stabilises I'll disable the debug messages.
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MAVEN-313
    Summary: linkcheck plugin fails for any project that has nekohtml as a dependency
       Type: Bug

     Status: In Progress
   Priority: Major

 Time Spent: Unknown
   Estimate: 1 hour

    Project: maven
  Component: None
   Versions:
             1.0-beta-9

   Assignee: Ben Walding
   Reporter: Ben Walding

    Created: Wed, 5 Mar 2003 5:53 AM
    Updated: Fri, 7 Mar 2003 7:33 AM

Description:
For any project that has nekohtml as a dep (eg cactus plugin), linkcheck fails when parsing html.  This is caused by it erroneously using the nekohtml parser (used by httpunit).

nekohtml is used even when using httpunit 1.5.2, and forcing jtidy to be used.

Waiting on jason to finish upgrading maven to classworlds before I try and fix this.  It may be fixed by the upgrade.


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