Re: [jboss-as7-dev] sisu and spymemcached

This are transitive dependencies of maven aether. It is used during test phase to load legacy versions of subsystems artifacts and test against them. so this is only test dependency not runtime one. if that helps you in any way.

-- tomaz On Fri, Mar 1, 2013 at 11:15 PM, Fernando Nasser < fnasser(a)redhat.com > wrote: Hi guys, I found these in our todo tag (for building the EAP AS in Brew) these artifats: org.sonatype.forge-forge-parent-9-1 jb-eap-6-rhel-6-todo jsanda org.sonatype.oss-oss-parent-5-1 jb-eap-6-rhel-6-todo dfediuck org.sonatype.sisu-sisu-inject-2.2.3-1 jb-eap-6-rhel-6-todo jsanda org.sonatype.sisu-sisu-inject-bean-2.2.3-1 jb-eap-6-rhel-6-todo jsanda org.sonatype.sisu-sisu-inject-plexus-2.2.3-1 jb-eap-6-rhel-6-todo jsanda org.sonatype.sisu-sisu-parent-2.2.3-1 jb-eap-6-rhel-6-todo jsanda org.sonatype.sisu.inject-containers-2.2.3-1 jb-eap-6-rhel-6-todo jsanda org.sonatype.sisu.inject-guice-bean-2.2.3-1 jb-eap-6-rhel-6-todo jsanda org.sonatype.sisu.inject-guice-plexus-2.2.3-1 jb-eap-6-rhel-6-todo jsanda spy-spymemcached-2.8.0-1 jb-eap-6-rhel-6-todo mikeb They do not have todo versions and are not included in the AS we ship, it is not in our POM, so they must be some build-time indirect dependencies. I see our BOM has: <version.org.sonatype.sisu>3.0.3</version.org.sonatype.sisu> but it is just the property, no <dependency> entry for this at all in the DM. Note the version is considerably different. Similar for spy-spymemcached Do we really need those to build the AS? Can we exclude these perhaps? Thanks for any help. Cheers, Fernando _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev