[
https://issues.jboss.org/browse/RF-13057?page=com.atlassian.jira.plugin.s...
]
RH Bugzilla Integration commented on RF-13057:
----------------------------------------------
Pavol Pitonak <ppitonak(a)redhat.com> made a comment on [bug
974084|https://bugzilla.redhat.com/show_bug.cgi?id=974084]
First, issues should have ON_QA status when you want us to verify fix.
Brian, archetype itself seems to be OK.
Marek, I need to use both EAP 6.0.1 and 6.1.0 Maven repositories for building generated
project because of missing slf4j dependency:
[ERROR] Failed to execute goal on project richfaces-kitchensink: Could not resolve
dependencies for project
org.richfaces.tests.archetypes:richfaces-kitchensink:war:4.3.2.Final: Could not find
artifact org.slf4j:jcl-over-slf4j:jar:1.6.1-redhat-2 in wfk-latest-enterprise-repository
(file:///mnt/hudson_workspace/workspace/richfaces-wfk-2.3-archetype-kitchensink-ftest/wfk-tools/maven-bootstrap/jboss-wfk-2.3.0-maven-repository)
-> [Help 1]
This is part of mvn dependency:tree:
org.richfaces.tests.archetypes:richfaces-kitchensink:war:4.3.2.Final
+- org.richfaces.core:richfaces-core-impl:jar:4.3.2.Final-redhat-1:compile
| +- org.richfaces.core:richfaces-core-api:jar:4.3.2.Final-redhat-1:compile
| +- net.sourceforge.cssparser:cssparser:jar:0.9.5:compile
| | \- org.w3c.css:sac:jar:1.3:compile
| +- com.google.guava:guava:jar:13.0.1-redhat-1:compile
| \- org.apache.james:apache-mime4j:jar:0.6-redhat-2:compile
| \- org.slf4j:jcl-over-slf4j:jar:1.6.1-redhat-2:compile
| \- org.slf4j:slf4j-api:jar:1.6.1-redhat-2:compile
Kitchensink Archetype: update enterprise version of JBoss BOM
-------------------------------------------------------------
Key: RF-13057
URL:
https://issues.jboss.org/browse/RF-13057
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: archetype
Affects Versions: 4.3.2
Reporter: Jan Papousek
Fix For: 4.3.3
from "1.0.4.Final-redhat-wfk-1" to "1.0.4.Final-redhat-wfk-2"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira