[
https://issues.jboss.org/browse/RF-13759?page=com.atlassian.jira.plugin.s...
]
Brian Leathem commented on RF-13759:
------------------------------------
RichFaces-cdk is not a runtime library. It is merely used to build the RichFaces project.
As such a release for the sole purpose of updating the parent seems superfluous.
Also, is downgrading RichFaces 4.5 to use 11 instead of 12 necessary? Are we sure we
won't see a EAP micro release with an updated parent before WFK 2.7 ships?
Unify jboss-parent between richfaces and cdk projects & allign
with EAP-6.3.0
-----------------------------------------------------------------------------
Key: RF-13759
URL:
https://issues.jboss.org/browse/RF-13759
Project: RichFaces
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: cdk, component, core
Affects Versions: 4.5.0.Alpha3
Reporter: Pavel Slegr
Fix For: 4.5.0.Beta1
Original Estimate: 1 hour
Remaining Estimate: 1 hour
both cdk and richfaces projects use different jboss-parent versions (9,12)
EAP-6.3.0 which will be underlying base for RF\-4.5.0 uses as latest supported
jboss-parent version 11.
Please unify into jboss-parent 11
NOTE: updating cdk version into jboss-parent 11, will need a maintenance (update for
deprecated code) in cdk/maven-plugin/src/main/java/org/richfaces/builder/mojo
These classes use deprecated api such as
{code}
@parameter expression="${executedProject}""
{code}
which doesn't work with maven-plugin-plugin 3.1 and leads into
{code}
[WARNING] The syntax
[WARNING] @parameter expression="${property}"
[WARNING] is deprecated, please use
[WARNING] @parameter property="property"
[WARNING] instead.
{code}
Some other additional changes may be also needed.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)