[ http://jira.jboss.com/jira/browse/JBMICROCONT-198?page=all ] Adrian Brock closed JBMICROCONT-198. ------------------------------------ Resolution: Won't Fix See the forum thread. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBMICROCONT-198?page=all ] Adrian Brock updated JBMICROCONT-198: ------------------------------------- Component/s: General Fix Version/s: JBossMC-2.0.0.CR1 Description: jboss-test (and its dependencies) and junit are pulled into projects that depend on "jboss-kernel" and "jboss-aop-mc-int" because the project contains child classes of TestCase within src/main/java ... Probably the best way to deal with this is to create a separate jboss-kernel-test and mc-int-test artifacts. These dependencies pull in: junit\junit\4.1\junit-4.1.jar jboss\profiler\jvmti\jboss-profiler-jvmti\1.0.0.CR5\jboss-profiler-jvmti-1.0.0.CR5.jar jboss\jboss-test\1.0.4-SNAPSHOT\jboss-test-1.0.4-SNAPSHOT.jar which aren't relevant to people's runtime. was: jboss-test (and its dependencies) and junit are pulled into projects that depend on "jboss-kernel" and "jboss-aop-mc-int" because the project contains child classes of TestCase within src/main/java ... Probably the best way to deal with this is to create a separate jboss-kernel-test and mc-int-test artifacts. These dependencies pull in: junit\junit\4.1\junit-4.1.jar jboss\profiler\jvmti\jboss-profiler-jvmti\1.0.0.CR5\jboss-profiler-jvmti-1.0.0.CR5.jar jboss\jboss-test\1.0.4-SNAPSHOT\jboss-test-1.0.4-SNAPSHOT.jar which aren't relevant to people's runtime. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira