Community
Participate
Working Groups
A recent discussion on the Oomph newsgroup about Maven project import included some treatment of the question of filtering out the target/ folder from the workspace. This seems quite sensible to me, as a Papyrus workspace that has most of the Papyrus plug-ins in it generates a *lot* of resources in the target/ folders for the workspace to track, that it doesn't need to. Probably EGit operations are considerably slowed by this. It would be great to add resource filters to all of the source projects in the Papyrus repo to filter out the Maven target directory: <filteredResources> <filter> <id>1450887687761</id> <name></name> <type>10</type> <matcher> <id>org.eclipse.ui.ide.multiFilter</id> <arguments>1.0-name-matches-true-false-target</arguments> </matcher> </filter> </filteredResources>
Some thoughts: - EGit shouldn't be slowed since target are in .gitignore - This kind of filter is *required* to work with RcpTT projects (otherwise you keep having false duplicate errors/warnings) - the best would probably to add maven nature to the projects, then the tooling should automatically filter the directory like the bin one for java projects It's still a good idea.
