Bug 825802 - RichFaces Showcase cannot be built with EAP 6 ER8 repository
Summary: RichFaces Showcase cannot be built with EAP 6 ER8 repository
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise WFK Platform 2
Classification: Retired
Component: RichFaces
Version: 2.0.0.ER6
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 2.0.0.ER7
Assignee: Marek Novotny
QA Contact: Pavol Pitonak
URL:
Whiteboard: showcase
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-28 13:54 UTC by Pavol Pitonak
Modified: 2012-06-22 07:32 UTC (History)
1 user (show)

Fixed In Version:
Clone Of: 820950
: 802066 (view as bug list)
Environment:
Last Closed: 2012-06-22 07:32:36 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBPAPP-9168 0 None Closed Missing artifacts in ER8 Maven repository 2012-07-04 17:29:37 UTC

Description Pavol Pitonak 2012-05-28 13:54:56 UTC 
Description of problem:
RichFaces Showcase cannot be built with EAP 6.0.0.ER8 Maven repository because of missing artifact org.hornetq:hornetq-logging:jar:2.2.16.Final-redhat-1

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. extract jboss-wfk-2.0.0.ER6-richfaces-demo.zip
2. mvn clean package
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Marek Novotny 2012-05-30 06:50:07 UTC 
Meanwhile I will include missing artifact
Comment 2 Marek Novotny 2012-05-30 14:48:15 UTC 
it is there starting https://hudson.qa.jboss.com/hudson/view/WFK/view/WFK-2.0-CI/job/JBoss-WFK-2.0.x-Maven-Repository/117/
Comment 3 Pavol Pitonak 2012-06-01 14:45:38 UTC 
I was able to build Showcase 2.0.0.ER7.
Comment 4 JBoss JIRA Server 2012-06-06 11:43:09 UTC 
Karel Piwko <kpiwko> updated the status of jira JBPAPP-9168 to Closed
Comment 5 JBoss JIRA Server 2012-06-06 11:43:09 UTC 
Karel Piwko <kpiwko> made a comment on jira JBPAPP-9168

Verified in EAP 6.0.0.CR1.
Note You need to log in before you can comment on or make changes to this bug.