[ https://issues.jboss.org/browse/TEIID-5521?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5521: --------------------------------------- There are some other issues with the dependency analysis. Something that we need transitively for embedded like jboss-vfs, basepom does not like that it is explicitly declared as a dependency. If we remove the explicit dependency on xerces we see the issue mentioned in TEIID-5225. So I committed what I could of the initial cleanup to master. We should probably at least pull back the kitting change to remove unneeded stuff from dataquality. With the jboss-parent we also just inherit the warnings: [WARNING] Rule 0: org.apache.maven.plugins.enforcer.RequirePluginVersions warned with message: Some plugins are missing valid versions:(LATEST RELEASE SNAPSHOT are not allowed ) org.apache.maven.plugins:maven-clean-plugin. The version currently in use is 3.1.0 org.codehaus.mojo:buildnumber-maven-plugin. The version currently in use is 1.4 org.apache.maven.plugins:maven-install-plugin. The version currently in use is 2.5.2 org.apache.maven.plugins:maven-source-plugin. The version currently in use is 3.0.1 org.apache.maven.plugins:maven-site-plugin. The version currently in use is 3.7.1 org.apache.maven.plugins:maven-deploy-plugin. The version currently in use is 2.8.2 org.apache.maven.plugins:maven-enforcer-plugin. The version currently in use is 3.0.0-M2 Which seems odd at first glance as those plugin version are defined in the parent... [~van.halbert] or [~rareddy] do either of you want to pursue this further in 12.0, or are you good with picking this back up later? -- This message was sent by Atlassian Jira (v7.12.1#712002)