On 10 July 2013 14:27, Jesse Glick <[email protected]> wrote: > On Wed, 10 Jul 2013 11:31:25 +0200 (CEST) "Christoph Kutzinski" < > [email protected]> wrote: > > no one has ever added a non-JUnit implementation, so all plugins will > probably only work with the JUnit implementations. > > To up-level the discussion a bit: does this functionality really need to > live in core at all? What if we deprecate the hudson.tasks.{junit,test} > packages, delete the @Extensions from visible descriptors in these > packages, and bundle e.g. the xUnit plugin [1] instead (using XStream > aliases for settings compatibility), presumably meaning plugins like > email-ext currently using the core interfaces would be switched to depend > on that? This would have numerous benefits such as allowing for a decoupled > release cycle and avoiding core bloat. > > (Some core refactoring would need to be done due to > Run.determineDetailedUnstableSummary, > AbstractBuild.{getTestResultAction,getAggregatedTestResultAction}, > AbstractProject/main.jelly, and some stuff in maven-plugin. The presence of > these things in core clearly points to the lack of appropriate extension > points.) >
Ha! Synergy... I was looking at those bits of poor factoring myself... it would be great if we could abstract those out... should be somewhat doable... > > > [1] https://wiki.jenkins-ci.org/display/JENKINS/xUnit+Plugin > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
