i'll keep spamming
this might be a dumb question but i'm new to jbpm area, i'm no maven expert (i use it mainly for simple dependency management) and i hate wasting time on reinventing the wheel - thus the post.
I found a github repository named 'droolsjbpm-build-distributions' (child of droolsjbpm repo) containing some maven assembly descriptors and it seems that these might be the entrypoint i'm looking for - am i right ?
I'm reading sonatype's maven reference guide to figure it out by myself (cannot expect that somebody else will do my job ) but any hints / words of wisdom would be very much appreciated.
1 of 1 people found this helpful
what you could do is that once you get all repositories on you side (using git-clone-others.sh) as you already did and that will give you complete repositories with the branches. Once you have that you could use git-checkout-all.sh script that allows to specify what branch it should use for what project - so you should be able to specify 5.5 for drools and 5.4 for jbpm.
thanks for your reply - it was very helpful.
I haven't used git before and the idea of a 'distributed vcs' is relatively new to me (we use good-old cvs to keep track of source changes in our small development team).
Seems that i'm gonna need a git primer before i dive into the details of 'jbpm ecosystem'
i was a bit hasty with my reply - this isn't exactly what i was looking for.
The script you mentioned (git-checkout-all.sh) seems to produce the same output i've achieved in a slightly different manner (by cloning specific branches using '-b' switch of git clone command).
It just seems to mark these branches 'active' within local copies of entire repositories.
And i'm trying to set 'active' flags for specific revisions / releases within these branches.
For example the code base of jbpm 5.4.x branch is still being developed with the latest maven version '5.4.1-SNAPSHOT' and what i'm trying to achieve is to move back to version '5.4.0' - the version that has been used to produce the full installer package.
But thanks anyway - i figure i just need this git primer really badly
I think that you could use git-checkout-all.sh and provide tag names instead of branch names and that should give you exact copy of sources from releases.
thank you, that solved my noobish problem