If you have your own project with parent pom, where repositories are configured (or can be configured also in settings.xml), even in this case the tooling adds repositories to your project pom. Second issue, tooling adds dependencies on switchyard-* libraries even if you have them in your parent pom. In this case, it would be probably better to have choice to add dependencies or not (e.g. by some modal window, which shows you what will be added and you will have the choice to copy the content and add it to your parent pom, or accept the addition).
We'll definitely have to investigate this further.
The SwitchYard Eclipse tooling does not provide support for specifying a parent project when creating a new SwitchYard project. Because of this, there is no way to know, during project creation, that a parent pom might be used and that it might contain dependency and repository definitions. If we want to add the ability to specify a parent project during project creation, I think that should be a separate enhancement request and should reference this BZ. It should be noted that if a project is configured to use a parent project, which does declare dependencies, the SwitchYard tooling should pickup that the project supports any capabilities provided by those dependencies. The tooling should also prevent you from removing those capabilities since they are declared outside the project. Based on all of that, I'd like to mark this as WONTFIX.
The request related to the repository is contained in #965097. Updating this request to contain the enhancment to allow specification of a parent pom during project creation.
Closing as WONTFIX