Using of Maven plugin for stream?!
Hello, I set up a builder of project on the server using the Jazz Build Engine (Maven), using the scm plugin, but faced with the need to specify the exact workspace, although I need to download the latest version of project of the full Stream.
When you try to specify in pom.xml: <scm> Build is stopped because of an error: "Der Selektor 'MOLS Stream' hat mit keinem Arbeitsbereich bereingestimmt. " Or if translate: "The selector 'MOLS Stream' has agreed to any work area." How to solve this problem? |
2 answers
Hello, I set up a builder of project on the server using the Jazz Build Engine (Maven), using the scm plugin, but faced with the need to specify the exact workspace, although I need to download the latest version of project of the full Stream. It might be easier to add the "Jazz Source Control" pre-build configuration element (tab) to the Maven build definition. This reduces the need to perform a lot of individual maven goals using the Maven SCM plugin (which currently has many limitations). Using this "Jazz Source Control" tab you first set your build workspace. This will be the repository workspace that you want to build from. The idea is that this repository workspace flows with a particular stream, so to answer your question about "needing to download the latest version of the project of the full Stream", you can check-off the checkbox called "Accept latest changes before loading". The next thing you need to do is specify the "load directory". (you can also customize the other options on this page to fit your needs). Doing this also has other benefit such as automatically creating a snapshot for you (so you can always keep track of exactly what went into each build). Now you will then have on disk the contents of a repository workspace (that has the latest from a particular stream), and you can then go to the "Maven" tab and do what ever maven goals you want from there... |
In this particular case though, the "SCM URL" used for our Maven Jazz SCM Plugin cannot use a Stream... it has to reference a repository workspace. In the Jazz world people load repository workspaces and check in / deliver / accept from them (not from streams however). As mentioned above there are limitations to how we can adapt to the Maven SCM Plugin. We are constrained in that we have to use their API... and many of the concepts that we have in Jazz SCM do not exist in the Maven SCM Plugin (or other SCMs). Please see this forum topic if you would like to discuss proposals: http://jazz.net/forums/viewtopic.php?p=39169#39169 |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.