[
https://issues.jboss.org/browse/JBIDE-14018?page=com.atlassian.jira.plugi...
]
Eric Barber commented on JBIDE-14018:
-------------------------------------
I accept that Team->Show History will allow developers to see the contents of a commit.
That said, when 8-12 developers are pushing constantly to multiple branches with cherry
picking going on, generic commit messages really complicate the process.
Developers are currently falling back to your second suggested approach. More accurately,
they're just using Git's command line interface. That works, but it takes them
away from the Eclipse plugins that you've developed and that I think simplify
interaction w/ OpenShift.
In short, we're working around this issue, but developing patterns which are leading
away from Eclipse and any productivity boosters these plugins can provide. I can only
advocate that this issue receive higher priority going forward. Thanks.
OpenShift commit message references JBoss Tools
-----------------------------------------------
Key: JBIDE-14018
URL:
https://issues.jboss.org/browse/JBIDE-14018
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.1.0.Alpha2
Reporter: Michelle Murray
Assignee: Andre Dietisheim
Priority: Minor
Fix For: 4.2.x
Attachments: commit_from_JBT.png, Customized Git Commit on Publish.png
In Servers tab, when you right-click on an OpenShift server adapter and click Publish, an
automatic commit message is generated: "Commit from JBoss Tools".
This message references JBoss Tools - for JBDS it should mention JBDS. I realise it is
difficult to have a different message for JBT and JBDS so I guess the message needs to be
changed to not reference either.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira