2 Replies Latest reply: Apr 11, 2012 4:15 PM by Clebert Suconic RSS

Now we have 3 active branches

Yong Hao Gao Master

Which means one bug fix will have to go to as many as three places. An issue may be found and fixed first in master and then pushed to the other two branches. It could also be initiated from one of the other branchs and then pushed back to master. I don't think it is a good practice and it will gets harder to maintenance.


I think the best solution is keep only one active branch (one copy of common source code, no duplicated code) and use different maven tasks to produce build kits for different purposes. For example we can define the build target in a property file like hornetq.properties:


build.target = AS7 | EAP5 | EAP6


and all relevant build tasks will observe this flag for their proper actions.