Eclispe files created in wrong project when an AndroMDA project uses a master pom

Description

This one is related to Bug ANDROMDA-714:
https://andromda.atlassian.net/browse/ANDROMDA-714

We upgraded to Maven 3 and unfortunality getFile() doesn't return null anymore for master/super poms. So the question is again: "how to distinguish AndroMDA pom project and master pom project" ... thinking about a solution for quite some time now but haven't found that ONE-OF-KIND attribute for the AndroMDA pom.

Environment

AndroMDA 3.4-SNAPSHOT + Maven 3

Assignee

Former user

Reporter

Oliver Saggau

Labels

None

Components

Affects versions

Priority

Critical
Configure