[
https://issues.jboss.org/browse/JBIDE-23092?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-23092:
------------------------------------
I've added the above list to the job config, so next time around we can branch all the
other projects too:
Meanwhile, I've branched the above projects by hand, eg.,
https://github.com/jbdevstudio/jbdevstudio-website/tree/jbosstools-4.4.1.x
{code}
for d in jbosstools-maven-plugins/
jbosstools-download.jboss.org/ jbosstools-devdoc/
jbosstools-versionwatch/; do pushd $d; git checkout master;git pull origin master;git
checkout -b jbosstools-4.4.1.x;git push origin jbosstools-4.4.1.x; popd; done
for d in jbdevstudio-artwork/ jbdevstudio-website/ jbdevstudio-ci/; do pushd $d; git
checkout master;git pull origin master;git checkout -b jbosstools-4.4.1.x;git push origin
jbosstools-4.4.1.x; popd; done
{code}
I can't branch jbdevstudio-qa since I don't have permission.
add more projects to the list of projects to branch and/or update
root pom
--------------------------------------------------------------------------
Key: JBIDE-23092
URL:
https://issues.jboss.org/browse/JBIDE-23092
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: build
Reporter: Nick Boldt
Fix For: 4.4.1.Final
MIssing projects we could have included in the automated branching:
* jbosstools-integration-tests [root pom in ./]
Need to also branch these, but there's no root pom to adjust, so the script should
just fail silently:
* jbosstools-devdoc [no root pom]
*
jbosstools-download.jboss.org [no root pom]
* jbosstools-maven-plugins no root pom]
* jbosstools-versionwatch [no root pom]
* jbdevstudio-ci [no root pom]
* jbdevstudio-qa [no root pom]
* jbdevstudio-website [no root pom]
* jbdevstudio-artwork [no root pom]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)