mevenide

Paths to maven dependencies hard-coded.

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: ECLIPSE-0.4
  • Fix Version/s: ECLIPSE-0.4.1
  • Component/s: mevenide-eclipse
  • Labels:
    None
  • Environment:
    Windows XP SP2, Java 1,4,2_06, Maven 1.1-beta1, Mevenide 0.4.0
  • Number of attachments :
    1

Description

Mevenide has paths hard-coded when it looks for the various dependices required to run Maven. Inserting a new version of Maven with different dependencies (i.e. the new 1.1-beta1) causes Mevenide to fail.

A more dynamic method of locating dependencies (i.e. listing the %MAVEN_HOME%/lib folder and dynamically adding all JARs from there) would be preferable and allow users to update Maven without having to wait for a new version of Mevenide.

  1. Text File
    stacktrace.txt
    20/Jul/05 5:03 AM
    0.6 kB
    Ricardo Gladwell

Activity

People

  • Assignee:
    Unassigned
    Reporter:
    Ricardo Gladwell
Vote (1)
Watch (2)

Dates

  • Created:
    Updated: