[
https://issues.jboss.org/browse/RF-13608?page=com.atlassian.jira.plugin.s...
]
Brian Leathem commented on RF-13608:
------------------------------------
After discussing this with [~lfryc] we have come up with the following artifact/naming
convention:
* The rich set of components will be called:
** {{org.richfaces}}:{{richfaces}}
* The a4j set of components will be called:
** {{org.richfaces}}:{{richfaces-a4j}}
* The richfaces core will be called:
** {{org.richfaces}}:{{richfaces-core}}
This naming convention was chosen so that we can setup the following transitive
dependencies
* {{richfaces}} depends upon
** {{richfaces-a4j}}
** {{richfaces-core}}
* {{richfaces-a4j}} depends upon
** {{richfaces-core}}
With these transitive dependencies in place, an application developer needs only include
the single dependency in there application:
{code}
<dependency>
<groupId>org.richfaces</groupId>
<artifactId>richfaces</artifactId>
</dependency>
{code}
Additionally the choice of artifact names will give meaningful names for those who consume
the artifacts directly (without using maven).
Apply appropriate package and artifact names to the component poms
------------------------------------------------------------------
Key: RF-13608
URL:
https://issues.jboss.org/browse/RF-13608
Project: RichFaces
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Brian Leathem
Assignee: Brian Leathem
Fix For: 4.5.0.Alpha3
Original Estimate: 30 minutes
Remaining Estimate: 30 minutes
The current package {{org.richfaces.compat}} is inappropriate for the RichFaces 4.5
release.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)