[
https://issues.jboss.org/browse/JBIDE-23623?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-23623:
------------------------------------
Please define WHICH flag was reported missing. Can you attach your console log? I need tea
leaves if you want me to read your future. My crystal ball's in the shop being
repaired. :D
JIRAs are automatically closed if your github commit email matches your JIRA email, and
you use Smart Commits:
https://confluence.atlassian.com/fisheye/using-smart-commits-298976812.html
Thus pushing a commit to github with a comment like "JBIDE-23623 #close" will
cause this JIRA to be closed. But only if the above condition is met (github email == JIRA
email).
problems running getProjectRootPomParents and createTaskJIRAs
-------------------------------------------------------------
Key: JBIDE-23623
URL:
https://issues.jboss.org/browse/JBIDE-23623
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build
Affects Versions: 4.4.3.AM1
Reporter: Nick Boldt
Assignee: Jeff MAURY
Fix For: 4.4.3.AM2
Attachments: jira.txt, prepare-am1.txt, run.log
When Jeff ran the latest emailed instructions [0] for the 4.4.3.AM1 initialization [1],
this happened:
{quote}
Remarks:
the right command is git checkout jbosstools-4.4.x and not co jbosstools-4.4.x
When I run the getProjectRootPomParents.sh script, the JIRAs are not created as
createTaskJIRAs.py emits an error message (see run.log). What I do is to get the output
using tee, filter the output (keeping only python commands) and then run this script (see
jira.txt). Don't know why it does not fail this time.
Would be safe to run `pwd`/util/getProjectRootPomParents.sh instead of
./util/getProjectRootPomParents.sh
Jeff{quote}
[0]
https://issues.jboss.org/secure/attachment/12413688/prepare-am1.txt
[1]
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/jbos...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)