[ http://issues.apache.org/jira/browse/GRFT-91?page=comments#action_12422584 ] Jukka Zitting commented on GRFT-91: -----------------------------------
> "maven eclipse" doesnt work for multiprojects. "maven -Dgoal=eclipse multiproject:goal" should do that. I can also make a more explicit "maven allEclipse" goal for that if you like. The problem with the precreated Eclipse project files is that if you make inherently local modification (like set the project dependency mentioned above, enable the Eclipse Checkstyle plugin, etc.), you'll need to change normal svn usage patterns. When run in the project folder, "svn status" will report the Eclipse files as modified, "svn diff > latest-changes.patch" will include the local Eclipse changes, "svn commit" will break things for others, etc. Even Eclipse will flag the project as modified even if you've made no other changes to it. > Remove Eclipse .project and .classpath files from svn > ----------------------------------------------------- > > Key: GRFT-91 > URL: http://issues.apache.org/jira/browse/GRFT-91 > Project: Graffito > Issue Type: Improvement > Components: Project Build > Environment: Eclipse > Reporter: Jukka Zitting > Priority: Minor > > Some of the Graffito subprojects in svn contain Eclipse .project and > .classpath files presumably to simplify opening of the projects in Eclipse. > While this is a nice feature, it is also quite troublesome because it a) > duplicates information from project.xml, and b) interferes with svn > operations when the user wants to modify the project settings in Eclipse. > For example after checking out the entire Graffito trunk I imported all the > subprojects to Eclipse and replaced library dependencies to other Graffito > subproject jars with project dependencies to the actual subprojects. This > makes it very easy to navigate Graffito sources, but of course marks all > .classpath files managed in svn as modified. > It would be good to remove the .project and .classpath files from svn, > especially since they can be easily generated using "maven eclipse" from the > Maven Eclipse plugin. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
