I have a simple setup of two projects A and B using subversion. Both use subversion polling as build trigger.
Is the following use case possible (using the parameterized-trigger plug-in)? - When there is a change in A (SVN rev-x), then a successful build of A triggers a build of B with SVN rev-x (parameterized trigger). - When there is a change in B (SVN rev-x) and no change in A, then build B is triggered using rev-x (but no build of A) - When there is a change in A (SVN rev-x), and during this build a new revision rev-y is committed to project A and B, then I would like to have as next build project B with revision rev-x, then again project A with rev-y and then project B with rev-y. From the comments in the wiki it seems that after A rev-x a build of B rev-y is triggered. In that case I might get compile errors if the files in rev-y refer to classes in project A that are introduced in subversion rev-y. Ulli
