[jbosstools-issues] [JBoss JIRA] (JBIDE-17123) Arquillian support added even if it is not valid maven project

[Snjezana Peco (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-17123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Snjezana Peco resolved JBIDE-17123.
-----------------------------------

    Resolution: Rejected


I have disabled refactoring pom.xml in the Add Arquillian Support dialog because of the issues described in JBIDE-16417.
We can disable adding Arquillian profiles when a Maven project isn't valid, but I don't see any advantages of that.
If you, though, want to disable the action, please, reopen the jira.

> Arquillian support added even if it is not valid maven project
> --------------------------------------------------------------
>
>                 Key: JBIDE-17123
>                 URL: https://issues.jboss.org/browse/JBIDE-17123
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: testing-tools
>    Affects Versions: 4.2.0.Beta1
>            Reporter: Lucia Jelinkova
>            Assignee: Snjezana Peco
>             Fix For: 4.2.0.Beta2
>
>
> When I try to add Arquillian support to maven project with corrupted pom file, the dialog says that it is not valid maven project, however, the arquillian nature is added to the project. No arquillian stuff is added to the pom.xml file. 
> When I then try to add arquillian profile to the corrupted pom file, the profile is generated. 
> This is confusing - we should either prevent adding arquillian nature in case of corrupt pom file or generate arquillian stuff in both cases - adding support and adding profiles. 



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)