[
https://issues.jboss.org/browse/JBIDE-22728?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-22728:
------------------------------------
Projects to include here are:
* jbosstools-aerogear
* jbosstools-base
* jbosstools-forge
* jbosstools-server
* jbosstools-webservices
* jbosstools-hibernate
* jbosstools-vpe
* jbosstools-browsersim
* jbosstools-jst
* jbosstools-javaee
* jbosstools-central
* jbosstools-arquillian
* jbosstools-livereload
* jbosstools-openshift
* jbosstools-freemarker
and
* jbosstools-build-sites [needs a new PR builder job?]
* jbosstools-integration-tests [needs a new PR builder job?]
Projects which are more complicated to move via script:
* jbosstools-discovery
* jbosstools-build
* jbosstools-build-ci, maven-plugins, versionwatch
* jbosstools-target-platforms
Script the process for jbosstools projects to move up to the latest
parent pom in their root pom & all-tests pom; verify that changes are valid & push
to origin
----------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-22728
URL:
https://issues.jboss.org/browse/JBIDE-22728
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build
Affects Versions: 4.4.1.AM1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 4.4.1.AM2
Current process for moving all the JBT projects to the latest parent pom involves
generating 15+ JIRAs assigned to the various project leads, so they can all adopt the
latest parent pom, verify their build works, and push the change.
With the advent of PR build jobs, we can now streamline this a little:
instead of creating Task JIRAs, create PRs & let them run automatically.
if they pass, push them in automatically (via script that Alexey or Denis would run)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)