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/02/02 10:10:18 UTC

[maven-bug] Closed: (MAVEN-240) jdepend-2.2.jar is located in /lib for no apparent reason

Message:

   The following issue has been closed.

   Resolver: Ben Walding
       Date: Sun, 2 Feb 2003 3:10 AM

Done and Done.

Moved the DVSLPathTool.getPackagePath routine to JDeveloper plugin (as it was the only one that used it).  Should really be in JDepend plugin and exposed as a tag, but YAGNI applies - and it would have been harder to do.

Updated it to use jdepend 2.3, which also fixes a with source code analysis it seems
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MAVEN-240
    Summary: jdepend-2.2.jar is located in /lib for no apparent reason
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: FIXED

 Time Spent: Unknown
   Estimate: 2 hours

    Project: maven
  Component: None

   Assignee: Ben Walding
   Reporter: Ben Walding

    Created: Sat, 1 Feb 2003 6:39 AM
    Updated: Sun, 2 Feb 2003 3:10 AM

Description:
The bootstrap installs jdepend-2.2.jar to $MAVEN_HOME/lib.

This jar overrides all jars specified by plugins and as such should be removed from this location.  The jdepend java command will need to be updated to add the appropriate jdepend library to it's launch classpath.


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