[ https://issues.jboss.org/browse/SHRINKRES-61?page=com.atlassian.jira.plug... ] Karel Piwko updated SHRINKRES-61: --------------------------------- Component/s: api-maven (was: impl-maven) -- 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

[ https://issues.jboss.org/browse/SHRINKRES-61?page=com.atlassian.jira.plug... ] Karel Piwko edited comment on SHRINKRES-61 at 9/6/12 6:49 AM: -------------------------------------------------------------- Note, API discussion held place in SHRINKWRAP-325. was (Author: kpiwko): Note, API discussion held place in SHRINKRES-325. -- 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

[ https://issues.jboss.org/browse/SHRINKRES-61?page=com.atlassian.jira.plug... ] Geoffrey De Smet commented on SHRINKRES-61: ------------------------------------------- Some more motivation behind why I believe this issue is important: Contributors now take our source code, build it with maven, make some changes, run our testcases in IntelliJ or Eclipse (just right click on the class and select run) and see the test are still green. But that's because the test's war file hasn't been rebuild and their changes actually fail the tests. Educating them that they have to run maven after every change or that they have to configure IntelliJ/Eclipse/NetBeans's test run configs specifically, is a pita. -- 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