Hello,
with my latest commits on trinidad trunk pass-through Attributes should
work.
But there are some open questions.
Inside some Renderer there are several calls to responseWriter.startElement
with a component instance.
For example inputText will result following Html rendering:
Hi
I think it is safe to only pass the component in
responseWriter.startElement when it is really wanted, and pass null in
other cases. Trinidad overrides the default (and updated)
HtmlResponseWriter, so it is necessary to update the ResponseWriter there
with the new JSF 2.2 logic. There is no
[
https://issues.apache.org/jira/browse/MYFACES-4109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15976055#comment-15976055
]
Leonardo Uribe commented on MYFACES-4109:
-
I have been trying to fix this one, but it has been
Until now, nobody could explain me the real technical improvement of
GitFlow.
We are talking about using git and not GitFlow. Git does not require
GitFlow
At Apache we are only using process as much as needed and not as possible!
And my personal advice is:
Start with a model as simple as
Hello Bernd,
I like GitFlow for coordinating with multiple developers. However, if
everyone is sending pull requests anyway, it's not quite as useful. It
makes sense when you have multiple developers that are committing to a
"develop" branch and provides guidelines for working with master for new
+1
Wha's wrong with GitFlow?
___
Kito D. Mann | @kito99 | Author, JSF in Action
Web Components, Polymer, JSF, PrimeFaces, Java EE training and consulting
Virtua, Inc. | virtua.tech
JSFCentral.com | @jsfcentral | knowesis.io - fresh Web Components info
+1 203-998-0403
* See me speak at the
Hello
I think the changes will be not so complicated. The deltaspike pom looks
nice :-)
If someone talks about git-flow process i'm out.
Regards
Bernd
On Wed, Apr 19, 2017 at 12:28 AM, Leonardo Uribe wrote:
> +1
>
> Change the release process is a pain, but I agree there