[ https://issues.jboss.org/browse/JBIDE-14428?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-14428: --------------------------------------- {quote} import maven project that already have arquillian in pom.xml. {quote} We wouldn't need to change a maven project that already has arquillian in the pom.xml file (except adding the Arquillian nature). Arquillian Eclipse checks if there is the org.jboss.arquillian.core:arquillian-core-api artifact and, if so, it doesn't change pom.xml. Do we need to use some other way if a project already has arquillian in the pom.xml? Could you please attach an example of such a project (pom.xml)? {quote} Now the maven2Builder is moved from being last to being first. {quote} I will check. {quote} pom.xml has been rearranged and dependency is using hardcoded version instead of what is in the bom. if version specific in pom.xml for junit-container that is now removed. surefire-plugin is added. {quote} I have created the https://github.com/jbosstools/jbosstools-arquillian/blob/master/plugins/o... based on the Arquillian tutorial. The file is used to add arquillian artifacts. The version.arquillian_core property is replaced with the arquillianVersion Eclipse preference. Could you please specify how this file would look like? {quote} profiles are added. {quote} This is defined using the Window>Preferences>JBoss Tools>Arquillian preferences page. Do you mean, we don't need to add profiles when adding the Arquillian nature. There is a separate action to add profiles (Configure>Add Arquillian profiles...). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira