[ https://issues.jboss.org/browse/RF-11836?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč reassigned RF-11836: ------------------------------- Assignee: Lukáš Fryč -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11836?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-11836: --------------------------------- we would need to investigate more what variables exactly should not be used. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11836?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-11836: --------------------------------- It needs to be determined if we are able to sync only 4.1.x artifacts with Maven Central. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11836?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-11836: --------------------------------- I assume this was only misinterpretation of mail we have got from Joel: {quote} * Several sub-groups in org.richfaces contained POMs with variables in the <version> element. This caused our POM validity scripts to fail. These sub-groups appeared to be documentation or example related: {quote} Although some changes were done on feature branch {{productization-changes}}, there were rather focused on clean up. I suggest to reject this issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11836?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč resolved RF-11836. ----------------------------- Resolution: Rejected -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11836?page=com.atlassian.jira.plugin.s... ] Bernard Labno reopened RF-11836: -------------------------------- The problem is when I want to have custom release version of sandbox component (i.e. 4.2.3.ITC.Alpha1) then I set version of richfaces-root-parent to i.e. 4.2.2.Final but it uses ${project.version} in dependency management section and maven resolves it to 4.2.3.ITC.Alpha1 instead of 4.2.2.Final. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11836?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-11836: --------------------------------- Another option we have discussed with Marek and Karel: * define pom {{richfaces-build}} ** build-dependency version management (build BOM) ** import that from {{richfaces-root-parent}} * define property {{version.richfaces.cdk}} in {{richfaces-root-parent}} ** use it to manage versions of {{richfaces-build}} and {{richfaces-cdk-plugin}} and {{richfaces-resources-plugin}} * move as much as plugin management records to {{richfaces-parent}} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11836?page=com.atlassian.jira.plugin.s... ] Brian Leathem reassigned RF-11836: ---------------------------------- Assignee: (was: Brian Leathem) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11836?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč edited comment on RF-11836 at 5/24/12 3:20 AM: ---------------------------------------------------------- Brian, I agree, just several notes: (1) That we are not able to manage plugin versions of {{maven-cdk-plugin}} and {{maven-resources-plugin}} this way (they can't be managed in {{richfaces-parent}}, since they have own release cycle. We can certainly manage them in {{components}} module, which is all right (it is the only place which should use them. ---- (2) Additionally, {{richfaces-root-parent}} carries JSF profiles, we would need to move them all to the all sub-modules ({{core}}, {{components}}, {{dev-examples}}, {{showcase}}, {{cdk}}) specifically. We would need to synchronize them across all the modules. ---- (3) Additionally, we would have cyclic dependency on {{richfaces-parent <-> richfaces-checkstyle}} and the same with {{shade-transformers}}. We can then use the {{jboss-parent}} as parent there. --- These all modifications are okay with me, only (2) doesn't look maintainable enough. was (Author: lfryc): Brian, I agree, just several notes: (1) That we are not able to manage plugin versions of {{maven-cdk-plugin}} and {{maven-resources-plugin}} this way (they can't be managed in {{richfaces-parent}}, since they have own release cycle. We can certainly manage them in {{components}} module, which is all right (it is the only place which should use them. ---- (2) Additionally, {{richfaces-root-parent}} carries JSF profiles, we would need to move them all to the all sub-modules ({{core}}, {{components}}, {{dev-examples}}, {{showcase}}, {{cdk}}) specifically? ---- (3) Additionally, we would have cyclic dependency on {{richfaces-parent <-> richfaces-checkstyle}} and the same with {{shade-transformers}}. We can then use the {{jboss-parent}} as parent there. --- These all modifications are okay with me, only (3) doesn't look simple. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11836?page=com.atlassian.jira.plugin.s... ] Jan Papousek closed RF-11836. ----------------------------- -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira