Maven Integration for Eclipse

endless loop when parent/child projects using the same artifactId

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Minor Minor
  • Resolution: Unresolved
  • Affects Version/s: 0.0.11
  • Fix Version/s: None
  • Component/s: Dependency Resolver
  • Labels:
    None
  • Environment:
    maven2eclispe-0.0.11-dev
  • Number of attachments :
    1

Description

my eclipse workspace took up a tiny 150MB with the 0.0.10 release. I now have to bump eclipse up to over 1GB in order to even run without getting OutOfMemory errors.
I think the culprit is in the maven2 builder. It's constantly reading the pom files over and over again until eclipse crashes.

Activity

Hide
Eugene Kuleshov added a comment -

A clue how to reproduce that would be really handy. Please see http://docs.codehaus.org/display/M2ECLIPSE/How+To+Report+Issues

Show
Eugene Kuleshov added a comment - A clue how to reproduce that would be really handy. Please see http://docs.codehaus.org/display/M2ECLIPSE/How+To+Report+Issues
Hide
Niklas Ekman added a comment -

Eclipse project where this error occurs.

Show
Niklas Ekman added a comment - Eclipse project where this error occurs.
Hide
Niklas Ekman added a comment -

I attached a Eclipse project where this error occurs. I don't know if it's the same problem, but Eclipse goes into a loop and eventually the memory is out. The problem in this project is that when a multi-module project is defined and one of the modules artifactId is the same as the parents artifactId (clearly an error) Eclipse starts to eat memory.

Show
Niklas Ekman added a comment - I attached a Eclipse project where this error occurs. I don't know if it's the same problem, but Eclipse goes into a loop and eventually the memory is out. The problem in this project is that when a multi-module project is defined and one of the modules artifactId is the same as the parents artifactId (clearly an error) Eclipse starts to eat memory.
Hide
Eugene Kuleshov added a comment -

Niklas, thanks for the test project. This is indeed an interesting test case. You are right about the endless loop, and we need to somehow recover from that.

Show
Eugene Kuleshov added a comment - Niklas, thanks for the test project. This is indeed an interesting test case. You are right about the endless loop, and we need to somehow recover from that.
Hide
Igor Fedorenko added a comment -

This problem is still present in 0.9.4.

Show
Igor Fedorenko added a comment - This problem is still present in 0.9.4.

People

Vote (0)
Watch (1)

Dates

  • Created:
    Updated: