[ https://issues.jboss.org/browse/JBIDE-12974?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-12974 at 1/23/13 2:08 AM: ------------------------------------------------------------- Sorry, Nick, I was on vacation last week. Great job, thanks! I have a couple of comments. 1. Where is org.jboss.tools.ui.bot.ext and org.jboss.tools.ui.bot.ext.test? The former was the number one reason we wanted this site :) 2. Yes, we're aware of the failures. I don't think we can have simple maven builds work everywhere in the near future. But perhaps we could at least change the tests so by default only a 100%-working subset will be run. I'll comment on the other JIRA. 3. Why deprecate coretests? That is not the same thing as integrationtests, right? coretests contain unit tests for all the components and I thought that's something we want to continue doing. Also, coretests update site is still set up in the parent pom by default, right? -3.- 4. Could we have a mechanism in the parent pom to enable the integrationtests update site? Or maybe we could just add it to our root pom? Having it in parent pom seems cleaner. (But not on by default.) Tomorrow I will try to use it using repo definition in my setting.xml locally. was (Author: mmalina): Sorry, Nick, I was on vacation last week. Great job, thanks! I have a couple of comments. 1. Where is org.jboss.tools.ui.bot.ext and org.jboss.tools.ui.bot.ext.test? The former was the number one reason we wanted this site :) 2. Yes, we're aware of the failures. I don't think we can have simple maven builds work everywhere in the near future. But perhaps we could at least change the tests so by default only a 100%-working subset will be run. I'll comment on the other JIRA. 3. Why deprecate coretests? That is not the same thing as integrationtests, right? coretests contain unit tests for all the components and I thought that's something we want to continue doing. Also, coretests update site is still set up in the parent pom by default, right? 3. Could we have a mechanism in the parent pom to enable the integrationtests update site? Or maybe we could just add it to our root pom? Having it in parent pom seems cleaner. (But not on by default.) Tomorrow I will try to use it using repo definition in my setting.xml locally. -- 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