Actually I think the key step is the next one where "clean deploy" is being done, but it doesn't hurt to have them all configured to have Releases be the top priority.
Also this should really be done for all Maven jobs including merge and verify, not just release-version. The right long term solution is to remove the need to build against Staging at all, which will be addressed by the Independent Versioning process, but it probably will take some time for the whole of ONAP to transition to that process. Thanks, Gary -----Original Message----- From: Jessica Wagantall via RT [mailto:[email protected]] Sent: Wednesday, September 06, 2017 1:52 PM To: Gary Wu <[email protected]> Cc: [email protected] Subject: [ONAP Helpdesk #45447] [integration] Maven repo precedence issue Sure Gary, It seems that this should be a property of this step: versions:set versions:update-child-modules versions:commit -B Let me investigate how to do that in this case and get back to you Thanks! Jess _______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
