Good. I'm scratching my head about some of my pull requests. JMS is a bit overly complicated.
On Mon, Sep 19, 2011 at 6:24 PM, Jason Porter <[email protected]>wrote: > No, we didn't assign it to anyone. > > Sent from my iPhone > > On Sep 19, 2011, at 16:19, Shane Bryzak <[email protected]> wrote: > > > Was it decided who would take care of the testsuite restructure? I must > > admit I wasn't paying much attention during this discussion ;) > > > > On 19/09/11 23:39, Jozef Hartinger wrote: > >> INTEGRATION TESTS > >> > >> Structure: > >> > >> - api > >> - impl > >> - testsuite / src / test / java > >> > >> Container-specific issues > >> - there will be a BaseDeploymentFactory that creates base deployment > >> based on a system property (arquillian container name) > >> - there will be no common package scheme for now > >> > >> Default profile > >> - weld embedded > >> - skipped tests if weld embedded does not make sense in the context of > >> the module > >> > >> > >> FUNCTIONAL TESTS > >> - m4 will be used to generate pom files from our templates (stored in > >> Seam QA github) > >> > > > > _______________________________________________ > > seam-dev mailing list > > [email protected] > > https://lists.jboss.org/mailman/listinfo/seam-dev > _______________________________________________ > seam-dev mailing list > [email protected] > https://lists.jboss.org/mailman/listinfo/seam-dev >
_______________________________________________ seam-dev mailing list [email protected] https://lists.jboss.org/mailman/listinfo/seam-dev
