[richfaces-issues] [JBoss JIRA] (RF-13759) Unify jboss-parent between richfaces and cdk projects & allign with EAP-6.3.0

[Marek Novotny (JIRA)]

    [ https://issues.jboss.org/browse/RF-13759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991457#comment-12991457 ] 

Marek Novotny commented on RF-13759:
------------------------------------

[~bleathem] RichFaces-cdk is not a runtime library that is true, but we are here speaking about better maintability which is the main target for doing 4.5.x instead of 4.3.x, right?

With regarding to jboss-parent we are pretty sure as EAP 6.3.0.GA was released this week with version 11 of jboss-parent and EAP team will do only bug fixing in patch releases. We are bound now with 6.3.x for WFK 2.7.0. Exceptions happen but that is now really very low probability. Please evaluate it and let us know what features are required from org.jboss:jboss-parent:12 ? Otherwise we will differ between project/product release - less maintainability after deprecation.

> 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)