[ https://issues.jboss.org/browse/JBIDE-11570?page=com.atlassian.jira.plugi... ] Rastislav Wagner updated JBIDE-11570: ------------------------------------- Attachment: dw_error.zip Exception stack trace isn't available. Project attached. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11570?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-11570: ------------------------------------- I'd need to see the project before you add the seam dependency. So far, here's what I can say : - if no jboss repo is defined in your settings.xml, seam can not be resolved - for some reason, that leads to the project being configured with phony facet versions (jsf 1.2) - after you add the repository and seam is resolvable, the configurator can try again to configure the proper facets - when installing the seam 2.3 facet, it fails because it requires jsf 2.0, but jsf 1.2 has already been installed. Since we have can not update the jsf facet automatically, this is doomed to fail with a constraint violation. Again, if the jboss repo is in my settings.xml, I can't reproduce the problem. What we could do is -properly- better intercept the constraint violation and display it as an error marker. It'll be the user's responsibility to manually change the jsf facet. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11570?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-11570: ------------------------------------- Can you attach the project including all the config files? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11570?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-11570: ------------------------------------- Still can't reproduce. Do you have the same problem on different OS / JDK? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11570?page=com.atlassian.jira.plugi... ] Rastislav Wagner updated JBIDE-11570: ------------------------------------- Attachment: out-2.ogv screencast attached -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11570?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-11570. --------------------------------- Resolution: Done fixed in trunk -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira