TreeTable: wrong column sizes when scrollable="true" and dynamic columns

Describe the defect When we have scrollable=“true” with dynamic component generating columns in tree table, the column sizes are different from header to the body. Maybe is related to #7070

Also, don’t know why but this only works with <c:forEach/> component, when using the equivalent <ui: repeat/> nothing is displayed, which I think is another bug. Is it right?

Environment: PF Version: 10.0.0-RC2 (Was working in PF8) JSF + version: JSF 2.2.19 Affected browsers: Chrome, Safari

To Reproduce Steps to reproduce the behavior:

1. Insert scrollable=“true” in p:treeTable
2. Incude some dynamic columns and set their width’s
3. See error

Expected behavior Columns in the second table ( scrollable=“true”) should match the fist one:

Example XHTML

 <p:treeTable value="#{relatorioBean.root}"     var="item" id="tabelaItens" 
                          scrollable="true"      	  >  

           <p:column      style="width:150px;"    >  
			            <f:facet name="header">  <h:outputText value="col1"  />       </f:facet>  
			            <h:outputText value="col1"  />  
	     </p:column>  


  <c:forEach var="i" begin="0"       end="#{fn:length(relatorioBean.listaPeriodicidade) -1}" step="1"  >
	 <!--   equivalent  ui:repeat doesn't work here -->	
                       
                                            <p:column      field="#{item.listaPeriodoValor[i]}"
			                                       style="width: 100px;" width="100" > 
	                                              <!--   Apparently the width="100" param has no effect here -->		 
                                                      <f:facet name="header" >   
						               <h:outputText     value="title #{i}"  />
						       </f:facet> 
						     <h:outputText  value="#{i} value "  />
					   </p:column>
				        </c:forEach>  		      

[melloware]

TreeTable will have a first class Exporter in PF11 so you can get rid of that lib hopefully.

[edudoda]

Found it, it was due to that lib com.lapis.jsfexporter I mentioned above =x, which was requesting for PF5.1 version, and because when using -SNAPSHOT approach maven resolves to the nearest version, not newest one. Inserting <exclusion> <groupId>org.primefaces</groupId> ... in that lib solves the problem, but nice to see that it still working after so many years and versions.