[ https://issues.jboss.org/browse/JBDS-1819?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-1819: ------------------------------------------- so wait....I'm confused here ;) Thought we were talking about the existing project example feature - now its about adding a new copy of the quickstarts into project examples? And now reading that SOA-2954 have requested to remove the files that make them importable into JBDS is just weird. If SOA-P team do not wish to have eclipse metadata in their projects then they need to wait for JBDS 5 and move to maven pom.xml which can then be read and understood by other IDE's. Until then its going to be a gigantic mess if all or even just some quickstarts should do this. The intent of the PRD & TAG-16 is about making the SOA-P examples work with JBDS/JBT, not about JBDS making a fork or making a fork for JBDS. Of course to start taking a few as Len suggests and adjust is a way forward to get started but to have all working requires that those writing and maintaining the tests are responsible for maintaining these so there aren't a fork of the bundled ones. So questions just to clarify what is happening here since this is not really looking like a good split to me at this point: Brian - how are these quickstarts getting their dependencies - there is no maven repo for them or do they all survive fine with just a server definition ? Or are you just using examples that are just "xml" ? Are they somehow automatically converted - I think you mentioned something about a script that extracted something out from the "common" things in the soa quickstarts build.xml ? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira