Description of problem:
The 4.3.2.Final Kitchensink archetypes defines version of JBoss BOM 1.0.4.Final-redhat-wfk-1, but WFK 2.3.0.ER1 contains only 1.0.4.Final-redhat-wfk-2.
Brian Leathem <firstname.lastname@example.org> updated the status of jira RF-13057 to Resolved
Brian Leathem <email@example.com> made a comment on jira RF-13057
Resolved with this commit:
[~manaRH] can you cherry pick this into the WFK branch? Or would you rather I do a new 4.3.2.Final-2 archetype release?
Brian, archetype modifications are asynchronous process, so no WFK cherry picking is needed, do the release and QE verifies your release with proper cli arguments. Have a nice day!
Released and staged here:
@Pavol, can you please verify?
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.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
Pavol, try to ecxlude org.apache.james:apache-mime4j:jar:0.6-redhat-2 or directly org.slf4j:jcl-over-slf4j. That EAP artifact is unfortunately in EAP 6.1.0 repository inconsistent.
Excluding jcl-over-slf4j helps. Do we need to release new versions of our both archetypes with excluded jcl-over-slf4 or is there any other way of doing it?
Brian, this hasn't been resolved yet. Are you going to release a new version of archetype or will it be resolved in WFK 2.4?
Pavol, your comment on 2013-07-02 08:18:23 EDT (Comment 5) indicates this was resolved. Can you clarify what you mean when you say it is hasn't been resolved yet?
See the released archetype in maven central:
The archetype itself works fine with both EAP 6.0.1 and 6.1.0 Maven repositories. However, it should work with only 6.1.0 repository but it's not possible because of a bug in EAP Maven repo. However, customers can workaround it so we don't have to release new version of archetype. We should fix it in WFK 2.4.