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

Ascending order - Click to sort in descending order
Hide
Permalink
Tim Clemons added a comment -

Any known workarounds for getting the maven-1.1-beta series working with Mevenide?

Show
Tim Clemons added a comment - Any known workarounds for getting the maven-1.1-beta series working with Mevenide?
Hide
Permalink
Milos Kleint added a comment -

on a branch I have updated the mevenide common libraries and the mevenide for netbeans ui to be able to work with maven 1.1beta. once it's final we will release a new version of mevenide using m1.1. not sure the libraries will be backward compatible then however (working with maven 1.0.2 version of POM and jars)

Show
Milos Kleint added a comment - on a branch I have updated the mevenide common libraries and the mevenide for netbeans ui to be able to work with maven 1.1beta. once it's final we will release a new version of mevenide using m1.1. not sure the libraries will be backward compatible then however (working with maven 1.0.2 version of POM and jars)
Hide
Permalink
Faron Dutton added a comment -

The provided stack trace indicates a problem with Forehead not with MevenIDE. MevenIDE uses Forehead to dynamically locate the needed JARs, just as you suggested. Since I am currently using Maven 1.1 B2 with Eclipse 3.0 and MevenIDE 0.4.0, I suspect that the issue is either the Maven version (I have beta 2 not beta 1) or the whitespace in your path (I have none; d:/cygwin/usr/local/maven-1.1-beta-2).

Show
Faron Dutton added a comment - The provided stack trace indicates a problem with Forehead not with MevenIDE. MevenIDE uses Forehead to dynamically locate the needed JARs, just as you suggested. Since I am currently using Maven 1.1 B2 with Eclipse 3.0 and MevenIDE 0.4.0, I suspect that the issue is either the Maven version (I have beta 2 not beta 1) or the whitespace in your path (I have none; d:/cygwin/usr/local/maven-1.1-beta-2).

People

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

Dates

  • Created:
    Updated: