[
https://issues.jboss.org/browse/RF-11666?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč updated RF-11666:
----------------------------
Comment: was deleted
(was: 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/e9172f2fbb6d057c11009faff6c21e0...
)
Manage dependencies across whole framework
------------------------------------------
Key: RF-11666
URL:
https://issues.jboss.org/browse/RF-11666
Project: RichFaces
Issue Type: Task
Security Level: Public(Everyone can see)
Components: build/distribution
Affects Versions: 4.1.0.CR1
Reporter: Lukáš Fryč
Assignee: Lukáš Fryč
Priority: Critical
Fix For: 4.2.0.CR1
(Issue originally requested by Marek Novotny)
There are lot of dependencies with versions managed on low-level POMs, e.g.:
Search across project has found following (approximately, includes false positives):
{code}
./checkstyle/pom.xml
./shade-transformers/pom.xml
./core/impl/pom.xml
./core/api/pom.xml
./build/dist/pom.xml
./dev-examples/dnd-demo/pom.xml
./dev-examples/input-demo/pom.xml
./dev-examples/iteration-demo/pom.xml
./dev-examples/output-demo/pom.xml
./dev-examples/parent/pom.xml
./dev-examples/irc-client/pom.xml
./dev-examples/push-demo/pom.xml
./components/output/ui/pom.xml
./components/dnd/ui/pom.xml
./components/dnd/api/pom.xml
./components/validator/ui/pom.xml
./components/dist/static-resources/pom.xml
./components/dist/richfaces-components-ui/pom.xml
./components/input/ui/pom.xml
./components/parent/pom.xml
./components/pom.xml
./showcase/pom.xml
./archetype-simpleapp/src/main/resources/archetype-resources/pom.xml
./archetype-simpleapp/pom.xml
./cdk/maven-javascript-plugin/pom.xml
./cdk/maven-cdk-plugin/pom.xml
./cdk/generator/pom.xml
{code}
For {{jsf-test}}:
{code}
./jsf-test/jsf-mockito/pom.xml
./jsf-test/stage/pom.xml
./jsf-test/mock/pom.xml
./jsf-test/maven-mockgenerator-plugin/pom.xml
./jsf-test/jsf-test-htmlunit/pom.xml
./jsf-test/scriptunit/pom.xml
./jsf-test/jetty/pom.xml
{code}
It would be beneficial having one place managing these dependencies.
--
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