[richfaces-issues] [JBoss JIRA] (RF-11836) Replace ${project.version} definitions in the poms with actual version
Lukáš Fryč (JIRA)
jira-events at lists.jboss.org
Mon May 21 08:28:19 EDT 2012
[ https://issues.jboss.org/browse/RF-11836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12694305#comment-12694305 ]
Lukáš Fryč commented on RF-11836:
---------------------------------
In richfaces-root-parent, we manage versions of submodules and plugins (like CDK)
to ${project.version}.
But imagine some subproject (like Sandbox components), which consumes richfaces-root-parent as its parent.
Then when you re-define <version> of the project, all dependencies are automatically managed to that version (and such versions don't need to exist at the moment).
Hard-coding version is the best solution, since we can't also use the property like ${version.richfaces} - I don't remember why, but we have that discussion with Marek [1].
Does anything prevent us to do so?
Prototyped here:
https://github.com/richfaces/build/commit/e9172f2fbb6d057c11009faff6c21e0a59e6c93d
> Replace ${project.version} definitions in the poms with actual version
> ----------------------------------------------------------------------
>
> Key: RF-11836
> URL: https://issues.jboss.org/browse/RF-11836
> Project: RichFaces
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: build/distribution
> Affects Versions: 4.1.0.Final
> Reporter: Lukáš Fryč
> Assignee: Brian Leathem
>
> This is requirement for uploading to 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
More information about the richfaces-issues
mailing list