Description of problem: Not having org.richfaces:richfaces-bom:4.2.2.Final in maven local repository causes error during Administration section generation. Version-Release number of selected component (if applicable): WFK 2.2.0.CR1 Ticket Monster 2.0.7.Final-redhat-1 Forge 1.1.2.Final (and 1.2.2.Final too, but you have to modify admin_layer.fsh script before to accept this version) How reproducible: Always. Steps to Reproduce: 1. remove (if exists) org.richfaces:richfaces-bom:4.2.2.Final from your maven local repository 2. unzip distributed Ticket Monster example and navigate to `demo` directory 3. run Forge 4. run admin_layer.fsh Actual results: Using Forge at /home/trepel/forge-distribution-1.1.2.Final _____ | ___|__ _ __ __ _ ___ | |_ / _ \| `__/ _` |/ _ \ \\ | _| (_) | | | (_| | __/ // |_| \___/|_| \__, |\___| |___/ [ticket-monster] demo $ run admin_layer.fsh ***INFO*** Using currently installed scaffold [faces] Wrote /home/trepel/Desktop/TiMos/timo/demo/src/main/webapp/favicon.ico Wrote /home/trepel/Desktop/TiMos/timo/demo/src/main/webapp/resources/scaffold/paginator.xhtml Wrote /home/trepel/Desktop/TiMos/timo/demo/src/main/webapp/resources/scaffold/pageTemplate.xhtml Wrote /home/trepel/Desktop/TiMos/timo/demo/src/main/webapp/index.html Wrote /home/trepel/Desktop/TiMos/timo/demo/src/main/webapp/index.xhtml Wrote /home/trepel/Desktop/TiMos/timo/demo/src/main/webapp/error.xhtml Wrote /home/trepel/Desktop/TiMos/timo/demo/src/main/webapp/resources/add.png Wrote /home/trepel/Desktop/TiMos/timo/demo/src/main/webapp/resources/bootstrap.css Wrote /home/trepel/Desktop/TiMos/timo/demo/src/main/webapp/resources/false.png Wrote /home/trepel/Desktop/TiMos/timo/demo/src/main/webapp/resources/favicon.ico Wrote /home/trepel/Desktop/TiMos/timo/demo/src/main/webapp/resources/forge-logo.png Wrote /home/trepel/Desktop/TiMos/timo/demo/src/main/webapp/resources/forge-style.css Wrote /home/trepel/Desktop/TiMos/timo/demo/src/main/webapp/resources/remove.png Wrote /home/trepel/Desktop/TiMos/timo/demo/src/main/webapp/resources/search.png Wrote /home/trepel/Desktop/TiMos/timo/demo/src/main/webapp/resources/true.png Wrote /home/trepel/Desktop/TiMos/timo/demo/src/main/webapp/resources/jboss-community.png Wrote /home/trepel/Desktop/TiMos/timo/demo/src/main/webapp/WEB-INF/web.xml Wrote /home/trepel/Desktop/TiMos/timo/demo/pom.xml ***ERROR*** Exception encountered: 1 problem was encountered while building the effective model for org.jboss.jdf.examples:ticket-monster:2.0.7.Final-redhat-1 [ERROR] Non-resolvable import POM: Could not find artifact org.richfaces:richfaces-bom:pom:4.2.2.Final in obsolete-enterprise-repository (file:///home/trepel/sources/wfk-qa/build/configuration/../../../obsolete-repository) @ line 51, column 19 (type "set VERBOSE true" to enable stack traces) Expected results: It passes. Additional info: If you build the example via maven before, the richfaces-bom dependency will be downloaded to your maven local repository and the subsequent try will succeed.
We need to alter TiMo to use proper RF version, instead of community.
Pete Muir <pmuir.uk> made a comment on jira JDF-254 In general, please file one issue per issue and don't compound issues, it makes it hard to track them, as not all may be fixable at the same time. 1) This is clearly documented in the tutorial, and is also a dupe of JDF-6 2) This is a bug in Forge 1.1.x, it's not reproducible in 1.2.x 3) This is a covered in https://issues.jboss.org/browse/JDF-257 which I've spun out of this issue (because it's covering too much).
This issue is not reproducible on Forge 1.2.2.
(In reply to comment #5) > Pete Muir <pmuir.uk> made a comment on jira JDF-254 > > In general, please file one issue per issue and don't compound issues, it > makes it hard to track them, as not all may be fixable at the same time. > This is my fault, I should have filed a new issue for comment #2. I'll split problems into separate issues.
Tomas, can you please verify that 2) cannot be reproduced with 1.2.x? It seems that Pete and you are experiencing different behavior.
For 1), I've filled https://bugzilla.redhat.com/show_bug.cgi?id=950332
For 3), I've filled https://bugzilla.redhat.com/show_bug.cgi?id=950334
(In reply to comment #8) > Tomas, can you please verify that 2) cannot be reproduced with 1.2.x? It > seems that Pete and you are experiencing different behavior. I have tried using: Ticekt Monster 2.0.7.Final-redhat-1 (the one from WFK 2.2.0.CR1 jboss-wfk-2.2.0-ticketmonster-demo.zip) Forge 1.2.2.Final The richfaces-bom can't be found for me.
Do you guys use different settings.xml by any chance?
Ok, I can reproduce, if I add an the wfk repo as an active profile. Please report this in the FORGE JIRA. This needs release noting: If you are using the WFK maven repository zip, then you may encounter an error downloading the RichFaces BOM e.g. ERROR] Non-resolvable import POM: Could not find artifact org.richfaces:richfaces-bom:pom:4.2.2.Final If this happens, please run the mvn verify goal. from the forge console in order to fetch the artifact locally
Related Forge JIRA: https://issues.jboss.org/browse/FORGE-858
Edited release note and inserted it into the 2.2.0 RN book. Docs stage URL: https://documentation-devel.engineering.redhat.com/docs/en-US/JBoss_Web_Framework_Kit/2.2/html-single/2.2.0_Release_Notes/index.html Build: JBoss_Web_Framework_Kit-2.2.0_Release_Notes-2.2-en-US-0-23
Forge JIRA: https://issues.jboss.org/browse/FORGE-858 is fixed in Forge 1.3.0
Verified in WFK 2.3.0.ER1
Edited doc text for wfk 2.3 release notes.
Vineet Reynolds <vineet.reynolds> updated the status of jira JDF-254 to Resolved