Hi Ed,
OK that explains a lot. I think I do want to give Maven
a chance with respect to running the tests.
About the SVN branch, that would be most helpful. It
would allow me to test it easier for sure!
Regards,
Manfred
> -------- Original Message --------
> Subject: RE: JSF mavenizing
> From: Ed Burns <edward.burns_at_oracle.com>
> Date: Fri, April 22, 2011 2:25 pm
> To: "'Mojarra dev list'" <dev_at_javaserverfaces.java.net>
>
>
> >>>>> On Thu, 21 Apr 2011 19:33:19 -0600, "Manfred Riem" <mriem_at_manorrock.org> said:
>
> MR> Hi Ed,
> MR> I want to use the master-child way of working within Maven.
> MR> This would allow you to push properties / plugins / dependencies
> MR> down to child projects while maintaining them globally.
>
> You mean using a pom that other modules declare as their <parent />?
>
> MR> Hope that explains what I am trying to do :)
>
> Yes, it does.
>
> Ok. Take a look at this blog entry describing the layout of our
> automated tests. [1]. I dread using surefire for tests. We have VERY
> VERY advanced and specific requirements for the runtime configuration
> that must exist for the various tests. These configurations depend
> heavily on what container is being used. For example, consider these
> statements.
>
> * For GlassFish 3.1, we support cluster and non-cluster scenarios.
>
> * In the GlassFish 3.1 non-cluster scenario only, some of tests use
> virtual servers.
>
> * We currently support tomcat7, but only for the systests.
>
> * The set of tests that actually run is highly dependent on which server
> config.
>
> * All of these need to able to dynamically stop and start the container
> at will from within the build logic of the test.
>
> Unless the state of the art for automated tests in maven has
> significantly advanced since I last looked at it, I'd like to stick with
> maven for the automated tests. Therefore, I can see the following maven
> module layout.
>
> maven module directory in maven tree
> master-pom
> jsf-api jsf-api/src/main (and other stuff)
> jsf-api-test/unit jsf-api/src/test
> jsf-ri jsf-ri/src/main (and other stuff)
> jsf-ri-test/unit jsf-ri/test
> jsf-ri-test/system jsf-ri/systest
> jsf-ri-test/integration jsf-ri/systest-per-webapp
> jsf-ri-test/regression jsf-ri/jsf-test
> jsf-tools jsf-tools
> jsf-demo jsf-demo
>
> Manfred, can I create an svn branch for your to play around with?
>
> Ed
>
> [1] http://www.java.net/blog/edburns/archive/2011/03/15/summary-mojarra-hudson-jobs-and-automated-tests-they-run
>
>
> --
> | edward.burns_at_oracle.com | office: +1 407 458 0017
> | homepage: | http://ridingthecrest.com/
> | 3 Business Days til JSF 2.2 planning complete
> | 40 Business Days til JSF 2.2 Early Draft Review
> | 76 Business Days til JSF 2.2 Public Review
> | 164 Business Days til JSF 2.2 Proposed Final Draft