[ http://jira.andromda.org/browse/MAVEN-68?page=comments#action_15890 ]
Oliver Saggau commented on MAVEN-68: ------------------------------------ I think it's a bad idead to check whether the master/super pom has no modules, because we use master/super poms which do. Instead of checking firstParent.getModules().isEmpty() it should check for firstParent.getFile() != null > Eclispe files not created when an AndroMDA Project uses a master pom > -------------------------------------------------------------------- > > Key: MAVEN-68 > URL: http://jira.andromda.org/browse/MAVEN-68 > Project: Maven Plugins > Type: Bug > Components: APP > Environment: AndroMDA 3.3 + Maven 2.0.8 > Reporter: Olivier THIERRY > Assignee: Chad Brandon > Priority: Critical > Attachments: EclipseMojo.java.diff > > When you create a company master pom (for example to ensure all projects use > same dependencies, same repositories, etc ...) and that you use this master > pom as parent for AndroMDA projects, running "eclipse" goal for andromdapp > maven plugin, you may have problems with .classpath and .project files not > being written with a NPE. More informations on this topic : > http://galaxy.andromda.org/forum/viewtopic.php?t=4407 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.andromda.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p
