The way I do mine is via web.xml:
ui.struts2.util.config.EnvironmentListener
public class EnvironmentListener implements ServletContextListener {
private static Log log = LogFactory.getLog(EnvironmentListener.class);
/**
* @see
javax.servlet.ServletContextListener#conte
And small changes to my proposal
2014-02-06 9:33 GMT+01:00 Lukasz Lenart :
> - hotfix is obvious (I think) - security vulnerabilities
> - feature - something big, like Struts2 for example :-)
When you work on something largest than just one commit, create feature branch
> - support - daily work
Hi,
First flow based on "git-flow" is done ;-) Basically it looks ok, the
only problem is with many comments - you can see it here [1]. In that
case each commit was referencing the JIRA issue. It could be omitted
and only finishing (git flow feature finish) commit message can
contain reference to
Hi,
Do you know how does it work? I need some usage example.
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
-
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: dev-h...@st
Hi,
Just to keep everything consistent please use the following schema of
commit message:
"WW- \n
"
where WW- is a JIRA key if change is related to JIRA issue.
Putting this on beginning simplifies matching between different
systems (Git, JIRA, Fisheye, etc).
Thanks in advance!
--
Łuka
