]
Brian Leathem edited comment on RF-11861 at 1/21/12 12:22 AM:
--------------------------------------------------------------
RichFaces artifacts are now in maven central.
See:
was (Author: bleathem):
RichFaces artifacts are now in maven central.
See:
richfaces 4.1.Final showcase: Non-resolvable parent POM: Could not
find artifact org.richfaces:richfaces-root-parent:pom:4.1.0.Final
------------------------------------------------------------------------------------------------------------------------------------
Key: RF-11861
URL:
https://issues.jboss.org/browse/RF-11861
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: Peter B
Assignee: Brian Leathem
Labels: richfaces
Fix For: 4.2.0.CR1
richfaces showcase for Richfaces 4.1 Final doesn't build.
Problem is that:
{code}
<groupId>org.richfaces</groupId>
<artifactId>richfaces-root-parent</artifactId>
<version>4.1.0.Final</version>
{code}
is not in central maven repository.
Console output:
{code}
[INFO] Scanning for projects...
Downloading:
http://repo1.maven.org/maven2/org/richfaces/richfaces-root-parent/4.1.0.F...
inal.pom
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project org.richfaces.examples:richfaces-showcase:4.1.0.Final
(D:\tmp\richfaces-showcase-77c6701\pom.xml)
has 1 error
[ERROR] Non-resolvable parent POM: Could not find artifact
org.richfaces:richfaces-root-parent:pom:4.1.0.Final in ce
ntral (
http://repo1.maven.org/maven2) and 'parent.relativePath' points at wrong
local POM @ line 8, column 13 -> [Help 2
]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the
following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2]
http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: