[jbosstools-issues] [JBoss JIRA] (JBIDE-23761) ensure that as, runtime test-framework plugins/features are added to the coretests site

[ https://issues.jboss.org/browse/JBIDE-23761?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-23761: ------------------------------------- Since whatever changes you made affected hte jbt-server ball color, I'm going to make some notes here: Following guide at https://wiki.eclipse.org/Minerva#Source ------------------------ 1) sourceTemplateFeature and gitkeep a) Ran on all folders of as, jmx, wtp, archives. All are already present 2) feature's pom.xml a) None of my feature's pom.xmls have this xml, but neither do any of the poms in base features... Assumed to be in parent pom somehow? 3) build.properties of every plugin - Cleaned up to make sure all build.properties have a src.includes = * and src.excludes = src - This step doesn't really make sense to me. What's the point of excluding the source folder in the source build?? - See part 6 for some strange stuff about build.properties 4) features added to site.xml? - All were already added 5) Additions to parent pom? - Assume done in parent pom already 6) Oddities / plugins that do not conform - jmx.jvmmonitor.core and jmx.jvmmonitor.ui have a very weird structure. - They look as follows: source.jvmmonitor-core.jar = src/ output.jvmmonitor-core.jar = bin/ bin.includes = [etc etc etc] - No idea how to remedy this stuff... they seem to actually include the generated jar in the build somehow? Not sure wtf is going on here. I made no changes here but these are the only two plugins that are 'weird'... Running build locally now and will commit if it doesn't seem like it broke anything, then will get jenkins results after -- This message was sent by Atlassian JIRA (v7.2.3#72005)