Hide Forgot
Date of First Response: 2009-02-11 06:11:31 project_key: SOA It is hard for project teams to test against the SOA platform, as the SOA platform build process is hard for project members to use. Solutions: 1. Give project members access to the SOA private repository 2. Change the way EAP is provided (e.g. by using ivy instead of SVN) to decrease the download size 3. Use anonsvn for project checkouts (* make this configurable) 4. Provide instructions for building the platform and for updating project versions
Thomas Benninger has informed us that the SOA platform SVN server will move, and that anonsvn will be available at some point on this new server. This will solve point 1., above.
If I can build the SOA platform - I can create integration tests - one of the integration tests can then cover JBPM-1395
Link: Added: This issue is a dependency of JBPM-1395
Link: Added: This issue depends JBQA-2139
We now use anonymous SVN for the project checkouts. MVEL is no longer required for SVN. Revision 3145 of: build-common.xml build.xml builders/drools/build.xml builders/esb/build.xml builders/jbpm/build.xml builders/soa/opensso/build.xml builders/soa/p-consoles/build.xml builders/soa/p-consoles/jbpm/build.xml dependencies.properties Commit message: Add new top-level build-common.xml to hold common routines. Move SVN handling into build-common.xml. Stop using mvel fragments to determine if we need to checkout or update. Use anonsvn for project checkouts.